Phenomenon:
Browse ASP page prompt 500 internal error
Event viewer:
[1]:
Server failed to load application '/LM /W3SVC/1/ROOT'. The error is 'no registration category'.
For more information about this message, please visit the Microsoft Online Support site at http://www.microsoft.com/contentredirect.asp.
For more information, see the Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
[2]:
Unable to start the MS DTC transaction manager.
For more information, see the Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
[3]:
The MS DTC transaction manager failed to start. LogInit returns error 0x2.
For more information, see the Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
[4]:
The MS DTC log file could not be found. After confirming that all resource managers that are coordinated by MS DTC do not have an "indeterminate" state
, run msdtc -resetlog to create a log file.
For more information, see the Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I
operating environment:
WinXP Pro SP2;
solution:
[1]:
check your DTC service (full name: Distributed whether Transaction Coordinator) starts correctly, if normal
you skip this step; if wrong, can not start properly, run the run the start menu: msdtc -resetlog
to Create a log file.
If you run this command is not wrong that you can skip these lines.
If you run this command error, please go to this part of the lower part of this article to start watching. (==== The following part is the information retrieved online (if you still can't do the above steps, please continue) ==)
Restart the machine and check if IIS can be used normally, if not continue.
[2]:
Execute the following command under CMD:
cd %windir%\\system32\\inetsrv
rundll32 wamreg.dll, CreateIISPackage
regsvr32 Asptxn.dll
Restart the machine, my problem can be solved perfectly! Encounter this depressing issue a guide system, IIS
reloading several times, BAIDU some information, and finally resolved, I hope to help you.
========= The following sections are the information retrieved online (if you still do not follow the above steps, please continue) ============= =================
1. Click Run in the system start menu:
regsvr32 jscript.dll (Note: This command fixes the dynamic link library related to java script
Re-run the input:
regsvr32 vbscript.dll (Note: This command fixes the dynamic link library related to vb script)
2. Microsoft's article about the solution that MS DTC can't install :
How to reinstall Microsoft Distributed Transaction Coordinator on a computer running Windows XP
http://support.microsoft.com/default.aspx?scid=kb%3Bzh-cn%3B891801
============================================================================================= =================================================================================================== Coordinator (MS DTC).
More Information
In general, you do not have to reinstall the Microsoft Distributed Transaction Coordinator (Msdtc.exe) on a computer running Windows XP or later. If you are using an older operating system, you may have to reinstall MS DTC after installing software such as Microsoft SQL Server 6.5 because the software overwrites the MS DTC binary with the version it contains. Reinstall the correct version of Msdtc.exe to restore the binary. In Windows XP and later, the Windows File Protection (WFP) feature ensures that current system binaries are not replaced.
However, if you must reinstall MS DTC on a computer running Windows XP, use the following procedure.
Warning: If you use the following steps, all outstanding transactions will be lost. Make sure there are no active transactions before performing the following steps.
Warning: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you will be able to resolve problems caused by improper use of the Registry Editor. Use Registry Editor at your own risk. 1. In the Administrative Tools, open Services and stop all services.
2. In the Startup Type column, change the startup type of all other services to Manual except for the services in the following table.
Note: It is recommended that you note the changed service so that you can restore these values correctly in step 7. Alerter
? COM+ Event System
? Computer Browser
? Distributed Link Tracking Client
? DNS Client
? Event Log
? IPSEC Services
? Logical Disk Manager
? Messenger
? Net Logon
? NT LM Security Support Provider
? Network Connections
? Plug and Play
? Remote Procedure Call (RPC)
? Remote Procedure Call (RPC) Locator
? Removable Storage
? Security Accounts Manager
? Server
? System Event Notification
? Task Scheduler
? TCP/IP NetBIOS Helper
? Windows Management Instrumentation < BR>? Windows Management Instrumentation Driver Extensions
? Windows Time
? Workstation
3. close the "services", and then restart the computer.
4. At the command prompt, type the following command:
%WINDIR%\\System32\\msdtc.exe -uninstall
5. Start Registry Editor and delete the following registry key if it exists HKEY_CLASSES_ROOT\\CID
? HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\MSDTC
? HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Services\\MSDTC
? HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet002\\Services\\MSDTC
? HKEY_LOCAL_MACHINE\\ Software \\ Microsoft \\ MSDTC
6. at the command prompt, type% WINDIR% \\ System32 \\ msdtc.exe -install.
7. Wait for disk activity to stop, then restore the startup type of the changed service to its original value.
8. In the registry, create the following registry key:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MSDTC\\XADLL
9. At the command prompt, type regsvr32 mtxoci.dll.
You will receive a message stating that DllRegisterServer in Mtxoci.dll has succeeded. Click "OK" to close the message.
10. Restart your computer.
11. At the command prompt, type %WINDIR%\\System32\\msdtc.exe -resetlog.
===================================================== ====================================================================================================== Step 2 of the successful installation of re-run msdtc -resetlog and the solution is from the 51CTO.COM blog