Summary of common problems and errors

1. No desktop found
CTRL + ALT + DEL new run input Explorer;
Complete Solution
CMD/K copy c: \ windows \ system32 \ dllcache \ assumer.exe C: \ WINDOWS

HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Run restart key: the path where the value of assumer.exe is Explorer

Manager. aspx, password 51 aspx
2. IIS cannot be started, error code 1086, Solution

It may be because other system components dependent on this service are disabled.

Click dependency to check whether two system components must be started before IIS can be started.

One of them is Remote Procedure Call (RPC)

Another is Security Accounts manger.

Start these two system components and then start IIS.

3. COM + Error
This problem started to cause a headache for me. Finally, I finally found the correct solution. Well, some people do not understand what it means.

MSDTC)
The password of the IWAM account in ActiveDirectory, IIS metabase database, and COM + application cannot be synchronized. The solution is also simple. There are three steps:

1. Reset the iis iwam account password. [In User Management in Computer Management]
2. Synchronize the password of iwam_myserver in IIS metabase, in cmd: C: \ Inetpub \ adminscripts> adsutil set w3svc/wamuserpass "yourpassword"
3. Synchronize the IWAM_MYSERVER password used by the COM + application, in CMD: c: \ inetpub \ adminscripts> cscript synciwam. vbs-v, but the error is always reported during step 3.

The key is to keep looking at it in the system and find that the MSDTC Service is abnormal. So let's start from here. The specific solution is as follows:
1. First, go to the component service and check the component service/computer/my computer/COM + application. The error "COM + cannot talk to Microsoft Distributed Transaction Coordination Program" is returned ", you cannot view the objects in it.
2. Go to the Event Viewer and find that the msdtc Service is not started properly.
3. Delete the keys in the registry:
? HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ MSDTC
? HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSDTC
? HKEY_CLASSES_ROOT \ CID
4. stop MSDTC Service: net stop msdtc start net start msdtc
5. uninstall the MSDTC Service: msdtc-uninstall
6. reinstall the MSDTC Service: msdtc-install
7. confirm that the msdtc Service has been started properly in the Event Viewer. [This step is critical. If not, restart the computer and check the password again (that is, the start step)

In fact, "COM + cannot talk to Microsoft Distributed Transaction Coordinator" does not cause this error after the message queue in the Windows component is installed, at the same time, the "message queue" component is dependent on the "Distributed Transaction Coordinator" (msdtc Service) in the service. This service must be enabled before the Message Queue component can be installed! After the message queue is installed, the COM + application menu in can be opened, indicating that it is working properly! The most convenient * (after msdtc is normal) If you reinstall IIS or uninstall and reinstall IIS at this time, you do not need the above manual password synchronization problem! That is to say, it is normal to install IIS by following this step! Actually, manually synchronize the password

4. Add the following configuration information to the WEB. Config configuration file. Otherwise, the program reports the "Sys undefined" error:

<HttpHandlers>
<Add verb = "GET, HEAD" path = "ScriptResource. axd "type =" System. web. handlers. scriptResourceHandler, System. web. extensions, Version = 1.0.61025.0, Culture = neutral, PublicKeyToken = 31bf3856ad364e35 "validate =" false "/>
</HttpHandlers>

5. Register ActiveX Controls
Regsvr32 yourocx_file_path (to install)
Regsvr32/u yourocx_file_path (to uninstall)