Windows Installer XP SP2 DCOM Problems and Solutions

Windows Installer XP SP2 DCOM Problems and Solutions
 
A strange problem occurred over the past few days. The symptoms are as follows:
1. When sysmantec Norton Antivirus is old, an error is reported, prompting that the instant message (MSN) cannot be monitored, while LiveUpdate and options cannot be started and configured properly. At that time, Norton thought there was a problem.
2. If the program cannot be properly installed or uninstalled, the system prompts "RPC service unavailable" or "Windows Installer is running in a secure environment or the installation is incorrect" during installation. It was thought to be related to RPC.
3. When Word Excel is started, it prompts "this document cannot be registered". At that time, it was suspected that it was related to DCOM.

Solution:
1. Search for "RPC service unavailable installation" on the Internet, and find some articles to solve the problem of Windows Installer damage.
There are roughly the following types:
A: (1) Stop the Windows Installer Service with msiexec/unregserver.
(2) download instmsiw.exe and decompress it with WinRAR. Enter the directory.
(3) Right-click MSI. inf, click Install, right-click mspatcha. inf, and click Install.
(4)re-use msiexec.exe/regserver to enable the Service
B: (1) Stop the Windows Installer Service with msiexec/unregserver.
(2)re-use msiexec.exe/regserver to enable the Service
C: Use the instmsiw.exe file of the office to reinstall it.
The problem has not been solved yet, because my installer is xp2's self-contained 3.0. There is no problem in running misexec.exe in the kernel. It does not appear that the installer has a problem.
2. I was reminded of the problems that occurred when I ran the word, and Google again. It turned out that the "DCOM initiator" was not started. Start-> solve the word problem and run other installation programs. OK, great

Cause:
Com is the specification for communication between Windows applications. For example, if sysmantec norton wants to reference some Windows Services, it needs to call the service interface through COM ,*. the MSI installer calls the interface function of the Windows Installer Service through DCOM. other programs call the word function through COM. Now I have stopped the com initiator, which causes these problems.
Summary:
It turned out to be a fault caused by DCOM. XP SP2 added this service and it seems to be the DCOM manager. Since I didn't see this service, I just stopped it.