HTTP Error 500.19-internal Server error resolution _win servers

A webservice test has just been deployed on this machine, and the "HTTP error 500.19-internal Server error" error occurred while browsing, as shown in the following figure:

After the inspection found that because of the first installation of IIS after the vs2008, simply re-register the ASPNET can be, the following steps

1 open to run, enter cmd into the command Prompt window.

2 into the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 directory.

3 input aspnet_regiis.exe–i execution can be

Note: If the system is a 64-bit second step path to C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727

IIS7 error occurred on The server when processing the URL ...
Win7 running the ASP program is always an error, the original site configuration problem ...

Problem One: The MS jet engine changed the location of the temp directory, but did not have access to the temporary directory, causing the database to fail (because of SQL problems, then use the Access database test).
Workaround:
To add a user of "Authenticated users" to the "system disk: \windows\serviceprofiles\networkservice\appdata\local\temp" directory, Where the AppData directory is hidden, you can enter the path directly in the address bar when entering, or display hidden files in Folder options.

To set permissions step: Right-click the Temp folder, select Properties Select the Security tab Click Edit to come out the Temp Permissions dialog box, click Add, and then enter authenticated in the "Enter object name to select" button below. Users (You can also click the "Advanced ..." button, click the "Find" button, select authenticated Users in the search results), OK "return to" Temp permission ", and authenticated the full control of the Users ' permissions to the check, OK Are you sure.

Question two: is IIS7 the client that does not send verbose error by default, so just give us a script error message (This information can be modified): An error occurred on the server when processing the URL. Please contact the system administrator. In this way, what is wrong is unknown.
Workaround:
Change the "Send errors to Browser" Inside the ASP module in IIS7 to True.
is critical, or you don't know where the error is.