How to solve internal errors in IIS running ASP file 500

1. IIS Server Error 500

2 error cause: 500 error is generally caused by an error in the source program.

3. Solution: 1. First, set the IE browser tool> Internet option.

2. If you refresh or re-open the 500 error page, the error program will appear.

3. Solve the problem according to the error message.

4 Possible solutions to ADODB. Connection creation failure:

1. reinstall MDAC2.8.

MDAC 2.8:

Http://www.microsoft.com/downloads/details.aspx? Displaylang = zh-cn & FamilyID = 6c 050fe3-c795-4b7d-b037-185d 0506rjc

2. Enter regsvr32 "C: \ Program Files \ Common Files \ System \ ado \ msado15.dll" in the start operation ". If you cannot enter regsvr32 scrrun. dll, refresh the page. You cannot enter regsvr32 msxml3.dll.

3. reinstall MDAC_TYP.EXE. I have also performed this operation, so I recorded it.

Http://download.microsoft.com/download/8/ B /6/8b 6198c 0-fe96-4811-9d81-d 5c 76dd5fea8/MDAC_TYP.EXE

The steps 1, 2, and 3 in no particular order above can solve the problem after the operation.

PS: Generally, use the second step to register these DLL. If the test is OK, no other steps are required.

1. symptom description:
(1) run the asp file locally. The IE prompt is:
Server Application Error
The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for maintenance.
Or prompt: 500 internal server error.
Or the error message "com +" is displayed.
View log files:
System logs are described as follows:
DCOM error no 10010 nt authority \ SYSTEM Myserver server {3D14228D-FBE1-11D0-995D-00C04FD919C1} was not registered with DCOM within a limited period of time.
W3SVC warn that no 36 N/A Myserver server fails to be transferred to the application '/LM/W3SVC/1/root '. The error is 'server running failed '.
For more information about this message, visit the Microsoft online support site: [url] http://www.microsoft.com/contentredirect.asp#/url].
Application logs are described as follows:
COM + error management 4205 N/A Myserver the COM + service cannot be initialized due to API errors in the following systems. It is usually caused by system resource storage problems on the local computer.
CryptAcquireContext
Process name: dllhost.exe
The severity of the error has led to Process Termination.
Error code = 0x80090017: The provider type is not defined.
COM + internal service information:
File:. \ security. cpp, row: 617
Ii. Cause Analysis
SA has been deleted. The SAM file is a database file that saves the user password. After deletion, all user information will be lost, and the corresponding group information will be lost, although you have logged on to the system again, the system has re-established the SAM file, IIS has been re-installed, and the IWAM account has been re-established, but the special information in the original user group has not been restored.
Or you can run it before, but you cannot run it because of unknown reasons. You can use this method.
Check Start> Settings> Control Panel> Administrative Tools> component services, "console root directory"-> "component service"-> "computer"-> "my computer"-> "COM + application, there is an IIS Out-Of-Process Pooled application. The application ID is {3D14228D-FBE1-11D0-995D-00C04FD919C1}. Many systems cannot find the application {3D14228D-FBE1-11D0-995D-00
An error such as C04FD919C1} occurs because the application fails to be started. Open the properties of the application and check that the identity is IWAM user. Right-click to start the application and report an error. After you change it to an administrator, it can be started normally. You can also add IWAM to the local administrator group. It is determined that the IWAM user is not authorized to access the application.
Iii. Solution
1. Modify the password of the IWAM_Myserver account. Choose Start> set> Control Panel> Administrative Tools> Computer Management, "System Tools"-> "local users and groups"-> "users", a IWAM_Myserver (Myserver is the name of the Local Computer) account, right-click to change the password, change to a custom password, which is assumed to be "1234 ";
2. Modify the password of the IIS IWAM_Myserver account. In the c: \ inetpub \ adminscripts \ directory (the default directory for IIS installation), enter c: \ inetpub \ adminscripts> adsutil. vbs set w3svc/wamuserpass "1234 ". after the modification is successful, the system prompts wamuserpass: (string )"******"
3. Choose Start> Settings> Control Panel> Administrative Tools> Computer Management, in "System Tools"-> "local users and groups"-> "users", check that IWAM_My server users are only in the GUEST group, in "local user and group"-> "group", right-click Users group attributes and add them to two user Members: nt authority \ Authenticated Users and nt authority \ Interactive. OK.
4. Enter c: \ inetpub \ adminscripts> synciwam. vbs-v in the default IIS installation directory.
The system prompts that the vb script cannot be run. Download a vbscript to install it online. Restart the computer (to restart)
Enter c: \ inetpub \ adminscripts> synciwam. vbs-v in the default IIS installation directory.
You can run it. However
Appears in the last line
Error 80110414
Check com + running status
Start -- run -- enter dcomcnfg-server component -- my computer -- COM + application cannot be opened, and an error occurs when com + cannot communicate with the Distributed Transaction Coordination Program.
Check net stop msdtc and find that it is not running
Net start msdtc cannot be started
Change the name of msdtc in the windows system32 folder on drive C. Change it as needed
Reinstall msdtc
Msdtc-install
Msdtc is automatically started.
If it cannot be started, repeat the complete steps.
A. Run msdtc-uninstall on the command line to delete the msdtc (Distributed Transaction Coordinator) service.
B. Delete the NetBIOS protocol in the "local connection" attribute.
C. After the machine is restarted, run msdtc-install on the command line to install the msdtc Service.
D. on the database server, open "component service" and "computer" in "component service" mmc, right-click "my computer", and select "properties ". Select "Security Configuration" on the "msdtc" tab, confirm "Network DTC Access", and select "do not require verification ".
And com + can be opened normally.
Then enter c: \ inetpub \ adminscripts> synciwam. vbs-v in the default IIS installation directory.
The result is all right. No error is reported.
Run the ASP program again. Everything works.
As a result, IIS cannot run ASP files. It is possible that MSDTC is damaged and cannot be started.