1 IIS Server 500 error
2 Error Reason: 500 the cause of the error is usually caused by the source program error.
3 Workaround: 1 First set IE browser à tool->internet option
2 Refresh or reopen the 500 error page will cause the wrong part of the program
3 Follow the error prompts and then resolve the problem.
4 ADODB. Connection possible workaround for creating a failure:
1, Reload MDAC2.8.
MDAC 2.8 Download Address:
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&FamilyID= 6C050FE3-C795-4B7D-B037-185D 0506396c
2, you first in the beginning of the operation of the input regsvr32 "C:\Program files\common Files\system\ado\msado15.dll." If not, enter him regsvr32 scrrun.dll Remember to refresh the page. Not to enter his regsvr32 msxml3.dll on it.
3, reinstall the Mdac_typ. Exe. This I have also operated, so also recorded.
http://download.microsoft.com/download/8/b/6/8b 6198c0-fe96-4811-9d81-d 5c76dd5fea8/mdac_typ. EXE
The above 1, 2, 3 is not in order, after the operation can generally solve the problem.
PS: Generally first use the second step, register these DLLs, if the test OK also do not use the other steps.
A description of the phenomenon:
(1) Run ASP files locally, ie prompt:
Server Application Error
The server has encountered an error while loading a application during the processing of your of request. Please refer to the event log for more detail information. Please contact the server Administrator for assistance.
OR hint: 500 Server Internal Error
or hint: COM + what's wrong
To view the log file:
The system log is described in detail as follows:
DCOM Error no 10010 NT authority\system Myserver server {3D14228D-FBE1-11D0-995D-00C04FD919C1} is not registered with DCOM for a limited time.
W3SVC warns no n/a Myserver server failed to transfer to application '/lm/w3svc/1/root '. The error is ' Server run failed '.
To get more information about this message, visit the Microsoft Online Support site: [Url]http://www.microsoft.com/contentredirect.asp[/url].
The application log is described in detail as follows:
COM + Error Management 4205 N/a Myserver the COM + service could not initialize because of the following system API errors. It is usually caused by a system resource storage problem on the local computer.
CryptAcquireContext
Process Name: Dllhost.exe
The severity of this error has caused the process to terminate.
Error code = 0x80090017: Provider type not defined.
COM + Service Internal information:
File:. \security.cpp, Line: 617
Second, the reason analysis
Once deleted the Sa,sam file is a database file that holds the user's password. After the deletion, all the user information will be lost, and the corresponding group information will be lost, although the system has been restarted, the system has been iis,iwam the Sam file, also reinstalled the account number has been established, but Special information in the original user group has not been restored.
Or it could have been run before and now there are unexplained causes that cannot be run. can use this method.
Check the start-> Settings-> Control Panel-> Administrative Tools-> Component Services, Console Root-> Component Services-> "Computer"-> "My Computer"-> "COM + applications," ". There is an IIS Out-of-process pooled applications the application ID number is {3d14228d-fbe1-11d0-995d-00c04fd919c1}, many system errors cannot find the application { 3d14228d-fbe1-11d0-995d-00
C04FD919C1} error, because the application failed to start, open the application's properties, check the identity of the IWAM user, the right button to start, error. When you change to administrator, you can start normally. The IWAM is added to the local Administrators group and can be started normally. Determined because the IWAM user is not authorized to access the application.
Iii. Solutions
1, modify Iwam_myserver account password, in the "Start"-> "Settings"-> "Control Panel"-> "Administrative Tools"-> "Computer Management", "System Tools"-> "Local Users and Groups"-> "users" inside, a IWAM_ Myserver (Myserver for local computer name) in the account, right to change the password, change to a custom password can be assumed to be "1234";
2, modify IIS internal Iwam_myserver account password, in the C:\inetpub\adminscripts\ directory (IIS install the default directory), enter: C:\inetpub\adminscripts>adsutil.vbs Set W3svc/wamuserpass "1234". After the successful modification, the system has the following prompts WAMUserPass: (string) "Hu Jintao"
3. In the "Start"-> "Settings"-> "Control Panel"-> "Administrative Tools"-> "Computer Management", "System Tools"-> "Local Users and Groups"-> "users", confirm that the Iwam_my server users are in the guest group only, In the "Local Users and Groups"-> "group", right click on the Users group properties, add to NT Authority\Authenticated users and NT authority\interactive two user members, OK.
4, in the IIS installation default directory input: C:\inetpub\adminscripts>synciwam.vbs-v
Discovery hint can't run VB Script, download a VBScript installation on the Internet. Then reboot the computer (to reboot)
And then enter in the default directory of IIS installation: C:\inetpub\adminscripts>synciwam.vbs-v
Can run. But
appear at last line
80110414 Error
Check COM + run
Start--run--Input dcomcnfg-server component--My Computer--com+ application discovery is not open, and COM + cannot talk to the Distributed Transaction Coordinator error.
Check net stop MSDTC discovery is not running
Net start MSDTC discovery could not be started
Find MSDTC renamed in the Windows System32 folder under C disk. Just change it.
Reinstall MSDTC
Msdtc-install
MSDTC will start automatically.
If it's not started then redo the complete steps
A. Run Msdtc-uninstall at the command line to remove the MSDTC (Distributed Transaction Coordinator) service
B. Removing the NetBIOS protocol in the properties of the local Area connection
C. After restarting the machine, run Msdtc-install at the command line and install the MSDTC service.
D. On the database server, in the Component Services MMC, open Component Services, turn on computer, and then right-click My Computer to select Properties. Then select Security Configuration on the MSDTC tab, confirm that network DTC access is selected, and select Do not require authentication.
COM + can also be opened normally.
Then enter the default directory for IIS installation: C:\inetpub\adminscripts>synciwam.vbs-v
The result is all well. No error.
Rerun the ASP program. Everything's fine.
Causes IIS to not run ASP files. It is possible that the MSDTC is damaged and cannot be started.
