Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 10006 Source: DCOM

DCOM got error "<error description>" from the computer <computer name> when attempting to activate the server: <server component>
Error "General access denied" - If running Citrix, see CTX118698.
This is now a common error with Microsoft Data Protection Manager.

- On the server giving the error, go into the Component Services Manager, Computers, My Computer
- Right-click on My Computer and select properties
- Select the COM Security tab
- "Edit Default" for Access Permissions
- Select "Add", select "Object Types" and select Computers
- Now add the computer name where Data Protection Manager is installed
- Restart the MSDTC service on your computer.

If this doesn''t work, review the COM rollup packages for Windows Server to be installed on the server generating the errors.
Error 2147746132, server ECABB0C4-7F19-11D2-978E-0000F8757E2A. As per ME971153, you receive the following error message when you try to use Dcomcnfg.exe connect to a computer that is running Windows 2000 Server from a computer that is running Windows Vista or that is running Windows Server 2008. To resolve this issue, Use the Microsoft Application Compatibility toolkit to let Windows Vista or Windows Server 2008 accept these packets. See the article for details.
- Error: "Class not registered" Server: "5A5AA0AA-1DEB-4683-96B0-B43301E83971" - In my case, this problem was caused by the HP Toolbox utility. It was not going through our ISA server firewall and registering this error every 30 seconds. Removing the toolbox eliminated the error.
As per Microsoft: "This problem occurs because Windows 2000 SP4 contains security updates that are included from Microsoft Windows Server 2003 that are not supported by the Application Center Event Provider in Application Center 2000 SP1. Therefore, Windows 2000 SP4 is not compatible with and is not supported with Application Center 2000 SP1". See ME827803 to solve this problem.

See ME911359 for additional information about this event.

This event appears when a program on this computer could not access a program on a remote computer. See MSW2KDB for more information.

- Error: "General access denied error" - See the link to "Configuring and Troubleshooting Windows 2000 and Windows Server 2003 Certificate Services Web Enrollment" for details on this problem.

If the computer is running Citrix software, then read "Citrix Support Document ID: CTX104003", "Citrix Support Document ID: CTX105019", and "Citrix Support Document ID: CTX108107" for details on fixing this problem.

See EV100105 - "Troubleshooting Microsoft Operations Manager" for more details on this event. Search for "DCOM 10006" on the page.

From a newsgroup post: "As I know, this event indicates that a program on this computer could not access a program on a remote computer. If the event log indicates an access-denied error, please change the DCOM permissions. For detailed information, please refer to the link “Microsoft event 10006 from source DCOM”. If the problem persists, please check if DCOM is disabled on the remote computer. If so, please enable it.
1. Run Dcomcnfg.exe.
2. Click the "Component Services" node under "Console Root".
3. Open the "Computers" folder.
4. For the local computer, right-click "My Computer", and then click "Properties".
5. For a remote computer, right-click "Computers" folder, point to "New", and then click "Computer".
6. Type the computer name.
7. Right-click the computer name, and then click "Properties".
8. Click the "Default Properties" tab.
9. Click to select the "Enable Distributed COM on this Computer" check box.
Note: If the option is already enabled, please make sure that under the Default Properties tab, “Default Authentication Level” is set to Connect. Also, check that the “Default Impersonation Level” is set to Identify.
10. Click "OK" to apply the changes and quit Dcomcnfg.exe.
11. Restart the operating system for the changes to take effect.
Please test the issue again. If the problem still happens, please run Dcomcnfg.exe again, and change “Default Impersonation Level” to Impersonate. Test again.
You may also try to disable all non-Microsoft services and startup items to see if the event still appears. To accomplish this do the following:
1. Run "msconfig".
2. In the Services tab, click "Hide All Microsoft Services" and click "Disable All".
3. In the Startup tab, click "Disable All". Click OK. (This will temporarily prevent third-party programs from running automatically during start-up).
4. Restart the computer and keep monitoring it to see if the problem still exists".

See ME325752 for additional information on this event.
In my case, this problem occurred between two Windows 2000 Professional SP4 workstations and an HP Print Server Appliance 4200, which is joined to a Windows 2000 AD Domain. HP LaserJet 1320 Toolbox miss-registered itself during standard install, caused two DCOM errors every 35 seconds.
To fix the problem, at a command window from the directory \windows\system32 run the command:
hpbpro.exe –RegServer
If the problem persists then run the following command:
hpbpro.exe –Service.
See the link to “HP LaserJet and LaserJet AiO Printers - DCOM Error Message” for additional information on this problem.
I got this problem on a Server running Microsoft Operations Manager (MOM) 2005. The event was caused by DCOM because MOM uses WMI to query information from the clients. One of the clients was an NT4 server, which normally does not run WMI. This caused the events on the MOM server. Installing WMI on the NT4 agent or configuring the agent to be monitored "agent-less" helped solving these entries.
In one case this happed on a Windows XP SP2 computer after it was added to a Windows 2003 domain and the computer was restarted twice (once as part of the procedure for adding the computer to the domain and an extra one).

The relevant part of the Default Domain Policy that caused this is shown in condensed form below:

Console Root
  {Group Policy}
    Computer Configuration
      Software Settings
        Windows Settings
          Scripts (Startup/Shutdown)
          Security Settings
            Account Policies
            Local Policies
              Audit Policy
                User Rights Assignment
                  Impersonate a client after authentication <MyGroup>.

Resolution: Change the above policy setting for Impersonate a client after authentication to: Administrators, <MyGroup>, SERVICE.

Restart the workstation twice (once to pick up the change in Group Policy and again to be affected by it at Windows startup).
- Error "Class not registered" - I had this error come up on my backup exec server in a 24-hour period. This error was linked to the account used to start the backup exec services. The solution was to stop the services, rename the C:\Program Files\VERITAS\Backup Exec\NT\Data\BEWINUI.uni to *.old. This file handles the security for backup exec. After starting the services and opening the backup exec application a new BEWINUI.uni is created and the problem is solved.
I started getting this error after applying Windows XP Service Pack 2. The error appears in the event log of the machine (Expert) that is using the "Offer Remote Assistance" option of the help center. I cleared this problem by following the steps stated in ME884910.
- Error: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it" - We found that we were getting this error on our SMS 2003 Management Point server after we had changed the management point service from another server to this one. During the change, the IIS Service was disabled on some, but not all of our SMS 2003 Distribution Point servers. There was a 10005 error on the effected Distribution Point server. Enabling and starting the IIS service on the Distribution Point server stopped the errors.
If you have an HP printer, this error is caused by a component in the I/O, "hpbpro.exe”, which is not registered properly on the system. To register the component properly, open a command prompt window by clicking Start then Run. Enter cmd.exe in the Run window. Change the directory to the System32 folder by typing "cd \winnt\system32" on Win2K and "cd \windows\system32" on later operating systems. Next, run the command “hpbpro.exe –RegServer”. If the error is still generated, run “hpbpro.exe –Service”.
- Error: "General access denied error", server: 8BC3F05E-D86B-11D0-A075-00C04FB68820 - I was setting up a load balancing environment on 2 Windows 2003 Web servers. I found that the option for "Enable distributed COM on this computer" was unchecked on one of the web servers. Enabling this on both servers resolved my problem and allowed me to manage the NLB cluster using Network Load Balancing Manager remotely.

CLS/App ID string, as noted by the contributor with similar issue, is the HP Port Sensing App, "HPBPRO.EXE". In my case, the printer was installed on a Win2k SP4 Server using TCPIP port mapping to the jet printer's direct port. The server was not a print server. In this instance, the error did not relate to the status of a printer on a client workstation. The DCOM error occurred every 30 seconds via port polling interval. Uninstalling the printer software suite (drivers, monitoring, toolbox, etc.) cured the error. Reinstalling the printer using simple TCP/IP mapping and drivers only, allowed the printer to be installed on the server without generation of these errors again.
Server: 5A5AA0AA-1DEB-4683-96B0-B43301E83971. In my case, I searched the registry for this value. It appeared under a HP Port locator key. A printer that was removed from the server was still installed on the workstation that was producing the error. I killed the HP monitoring and the error that was recurring every minute, then stopped. I removed the printer from the Printers folder that was no longer valid, restarted the HP Port locator software, and the error did not appear again.
Error: "Class not registered" Server: "8BC3F05E-D86B-11D0-A075-00C04FB68820" - This message indicates that Dcom cannot instantiate a remote object (i.e. it is not installed or the wrong version). A particular case is described in the ME229796 link below.

Error "Class not registered" Server: "E85CB4EA-DA54-4632-A3C1-D8D2818AC233" - As per ME330341, applicable to Microsoft Exchange 2000 Conferencing Server, this behavior may occur if the servers in your conferencing site do not all have the same version of the Exchange 2000 Conferencing Server service pack installed.

Error "Class not registered" Server: "D99E6E73-FC88-11D0-B498-00A0C90312F3" - Not really useful if using off-the-shelf applications, but a programming function, CertSrvIsServerOnlineW can be used to make a Distributed Component Object Model (DCOM) call to the server that is specified to determine the status of the certification authority (CA). If Certificate Services is not installed on the server, the DCOM call does not complete and this error is recorded. See ME312781.
Error: "Class not registered " Server: "9F53525D-62DA-11D2-84AF-00A0C9861EAB" -See ME295859. This error can show up on a box that has Microsoft Operations Manager 2000 installed as a Consolidator and Agent Manager.  As per the Q article, "Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article."
Error: "Class not registered" Server: D99E6E73-FC88-11D0-B498-00A0C90312F3. When backing up the system state on a remote system, Backup Exec uses Microsoft''s Certificate Services APIs to determine if Certificate Services is installed on the remote computer.  If the check succeeds, Backup Exec enables the special routines to back up Certificate Services. If it fails, Backup Exec will not attempt to back up Certificate Services components. In addition, the Certificate Services APIs log an error to the Windows 2000 System event log on the backup server.

This error is a normal result of the API call determining that Certificate Services is not installed. The error can be ignored. If the error cannot be ignored, or if it is desired that the error not be generated, there is a workaround that will prevent the event from being logged: install Certificate Services on the remote servers that are generating the error.  

Follow the steps bellow to install Certificate Services:
1. On the remote computer, go to Start > Settings > Control Panel and double-click Add/Remove Programs.
2. Select Add/Remove Windows Components from the left side of the Add and Remove Programs pop-up screen.
3. From the Windows Components Wizard, select Certificate Services.
4. Respond Yes to continue with the install of the Microsoft Certificate Services. After responding Yes to continue, the Certificate Services will be marked for installation.  
5. Select Next on the Windows Components Wizard to finish the installation of Certificate Services.
Note: This error is generated as a result of a call to a Microsoft function. As a result, this issue can not be fixed in Backup Exec.
Error "Class not registered" - This error can be generated when using Veritas Backup Exec to backup the system state on a remote computer. See Veritas Knowledgebase for Document 2029185 - "Selecting an ADV server in backup selections causes a DCOM error". The bottom line is that if Cert. Services aren't installed on the remote, this error will appear, but it can be ignored.
When backing up the System State on a remote system, Backup Exec uses Microsoft''s Certificate Services APIs to determine if Certificate Services is installed on the remote computer.  If the check succeeds, Backup Exec enables the special routines to back up Certificate Services.  If it fails, Backup Exec will not attempt to back up Certificate Services components. In addition, the Certificate Services APIs log an error to the Windows 2000 System event log on the backup server. See EV100104 (Symantec TECH15342).
If using MS Office XP and running BackUpExec 8.6 by Veritas, this error will occur if latest service pack has not been applied. Simply apply Office service pack to remedy.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.