Error — Event ID: 10010; DistributedCOM
I am getting this error repeatedly since I updated from Windows 8 to 8.1. Can you please help me to fix it?
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 10/20/2013 3:10:42 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
Description:
The server <03e64e17-b220-4052-9b9b-155f9cb8e016>did not register with DCOM within the required timeout.
Replies (7)
· Is your computer connected to any domain network?
. Do you experience any issue in the Computer at the time of the Event ID logged in the Event viewer?
I would suggest you to follow the methods given below.
Method 1: If you are using any third party antivirus, temporarily disable it and then check if this fixes the issue.
Temporarily disable antivirus software or any security software installed on your computer temporarily.
Warning: Security software can help protect your computer against viruses and other security threats. In most cases, you shouldn’t disable your antivirus software. If you have to temporarily disable it to install other software, you should re-enable it as soon as you’re done. If you’re connected to the Internet or a network while your antivirus software is disabled, your computer is vulnerable to attacks.
Method 2: Let’s clean start the operating system and check if you get the error.
We recommend you to clean start the operating system to determine if other programs are interfering with this application. To do this, see this article on how to clean start your computer:
Note: After checking the functionality in clean boot, follow the suggestions under “How to reset the computer to start as usual after troubleshooting with clean boot”.
Hope this helps and do let us know if you need any assistance.
3 people found this reply helpful
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Hello Babu, thanks for your help.
I am not connected to a domain. Except for Intel hardware drivers, there is no third party software on the PC. I tried Method 2 and the error is still occurring.
I searched the registry for the server <03e64e17-b220-4052-9b9b-155f9cb8e016>, and it says it is «WinStore OM».
About 4 minutes after one of these errors was generated, this Critical Event occurred and was logged in the Action Center:
Windows event 10010 dcom
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
When I started my Server Manager in Win2008R2, Application Server Role had an error event logged.
This event seems to have popped up after SQL Server 2008 R2 post-installation reboot.
The server <84ac6be7-8cf2-4e67-a80e-32acd3d7c381>did not register with DCOM within the required timeout.
This GUID seems to be for symentic computer security, as I have one installed.
I checked the registry but could not find this GUID under HKEY_CLASSES_ROOT -> CLSID.
Answers
This issue can be caused by the incorrect permissions.
I would like to suggest you perform the following suggestions to troubleshoot this issue:
1. Run Regedit to launch Registry Editor.
2. Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\
3. Right click on <84ac6be7-8cf2-4e67-a80e-32acd3d7c381>and select Permissions.
4. Click Advanced button and switch to Owner tab.
5. Highlight Administrators group and click OK
6. Highlight SYSTEM and Administrators group, check the Full Control boxes under Allow and click OK.
7. Run dcomcnfg to launch Component Services.
8. Expand Computers\My Computer\DCOM Config\NAP Agent Service.
9. Right click NAP Agent Service and choose Properties.
10. Switch to Security tab, choose Customize in Launch and Activation permissions label.
11. Highlight SYSTEM, check all the boxes under Allow and click OK to test the issue.
If it does not work, please also perform the following troubleshooting suggesstions to troubleshoot the issue:
1. In the %windir%/registration folder, make sure that the Everyone group has Read permissions.
2. In the %windir%/registration folder, make sure that the SYSTEM account has Full Control permissions.
3. In the %windir%/registration folder, make sure that the Administrators group has Full Control permissions.
4. In the advanced security properties of the .clb files in the %windir%/registration folder, make sure that the Allow inheritable auditing entries from the parent to propagate to this object and all objects. Include these with entries explicitly defined here option is selected.
5. Make sure that the Everyone group has one of the following permissions:
•Traverse permissions (“List Folder Contents”) on all parent directories, including %systemdrive%, %windir%, and %windir%\registration
•The Bypass traverse checking user right
To assign the Bypass traverse checking user right to the Everyone group, follow these steps:
1. Click Start, click Run, type gpedit.msc, and then click OK.
2. Expand Computer Configuration, expand Windows Settings, expand Security Settings, expand Local Policies, and then expand User Rights Assignment.
3. Right-click Bypass traverse checking, and then click Properties.
4. Click Add User or Group.
5. Type Everyone, and then click OK.
Note: If you receive a message that an object named «Users» cannot be found, click Object Types, click to select the Groups check box, and then click OK two times.
For more troubleshooting suggestions, please also refer to the following links:
Windows event 10010 dcom
Вопрос
На серверах Windows Server 2012 и Windows Server 2008 SP2 в журнале событий возникает ошибка:
Регистрация сервера
В чем может быть причина?
Ответы
Можно проделать следующие шаги,как указанно:
1. Run Regedit to launch Registry Editor.
2. Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\
3. Right click on <84ac6be7-8cf2-4e67-a80e-32acd3d7c381>and select Permissions.
4. Click Advanced button and switch to Owner tab.
5. Highlight Administrators group and click OK
6. Highlight SYSTEM and Administrators group, check the Full Control boxes under Allow and click OK.
7. Run dcomcnfg to launch Component Services.
8. Expand Computers\My Computer\DCOM Config\NAP Agent Service.
9. Right click NAP Agent Service and choose Properties.
10. Switch to Security tab, choose Customize in Launch and Activation permissions label.
11. Highlight SYSTEM, check all the boxes under Allow and click OK to test the issue.
1. In the %windir%/registration folder, make sure that the Everyone group has Read permissions.
2. In the %windir%/registration folder, make sure that the SYSTEM account has Full Control permissions.
3. In the %windir%/registration folder, make sure that the Administrators group has Full Control permissions.
4. In the advanced security properties of the .clb files in the %windir%/registration folder, make sure that the Allow inheritable auditing entries from the parent to propagate to this object and all objects. Include these with entries explicitly defined here option is selected.
5. Make sure that the Everyone group has one of the following permissions:
•Traverse permissions (“List Folder Contents”) on all parent directories, including %systemdrive%, %windir%, and %windir%\registration
•The Bypass traverse checking user right
To assign the Bypass traverse checking user right to the Everyone group, follow these steps:
1. Click Start, click Run, type gpedit.msc, and then click OK.
2. Expand Computer Configuration, expand Windows Settings, expand Security Settings, expand Local Policies, and then expand User Rights Assignment.
3. Right-click Bypass traverse checking, and then click Properties.
4. Click Add User or Group.
5. Type Everyone, and then click OK.
Note: If you receive a message that an object named «Users» cannot be found, click Object Types, click to select the Groups check box, and then click OK two times.
For more troubleshooting suggestions, please also refer to the following links:
Если варианты в ыше не помогут Вам,то можете ознакомитья с другими вариантами »траблшутинга» по этим ссылкам:
Windows event 10010 dcom
Вопрос
When I started my Server Manager in Win2008R2, Application Server Role had an error event logged.
This event seems to have popped up after SQL Server 2008 R2 post-installation reboot.
The server <84ac6be7-8cf2-4e67-a80e-32acd3d7c381>did not register with DCOM within the required timeout.
This GUID seems to be for symentic computer security, as I have one installed.
I checked the registry but could not find this GUID under HKEY_CLASSES_ROOT -> CLSID.
Ответы
This issue can be caused by the incorrect permissions.
I would like to suggest you perform the following suggestions to troubleshoot this issue:
1. Run Regedit to launch Registry Editor.
2. Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\
3. Right click on <84ac6be7-8cf2-4e67-a80e-32acd3d7c381>and select Permissions.
4. Click Advanced button and switch to Owner tab.
5. Highlight Administrators group and click OK
6. Highlight SYSTEM and Administrators group, check the Full Control boxes under Allow and click OK.
7. Run dcomcnfg to launch Component Services.
8. Expand Computers\My Computer\DCOM Config\NAP Agent Service.
9. Right click NAP Agent Service and choose Properties.
10. Switch to Security tab, choose Customize in Launch and Activation permissions label.
11. Highlight SYSTEM, check all the boxes under Allow and click OK to test the issue.
If it does not work, please also perform the following troubleshooting suggesstions to troubleshoot the issue:
1. In the %windir%/registration folder, make sure that the Everyone group has Read permissions.
2. In the %windir%/registration folder, make sure that the SYSTEM account has Full Control permissions.
3. In the %windir%/registration folder, make sure that the Administrators group has Full Control permissions.
4. In the advanced security properties of the .clb files in the %windir%/registration folder, make sure that the Allow inheritable auditing entries from the parent to propagate to this object and all objects. Include these with entries explicitly defined here option is selected.
5. Make sure that the Everyone group has one of the following permissions:
•Traverse permissions (“List Folder Contents”) on all parent directories, including %systemdrive%, %windir%, and %windir%\registration
•The Bypass traverse checking user right
To assign the Bypass traverse checking user right to the Everyone group, follow these steps:
1. Click Start, click Run, type gpedit.msc, and then click OK.
2. Expand Computer Configuration, expand Windows Settings, expand Security Settings, expand Local Policies, and then expand User Rights Assignment.
3. Right-click Bypass traverse checking, and then click Properties.
4. Click Add User or Group.
5. Type Everyone, and then click OK.
Note: If you receive a message that an object named «Users» cannot be found, click Object Types, click to select the Groups check box, and then click OK two times.
For more troubleshooting suggestions, please also refer to the following links:
Windows event 10010 dcom
Вопрос
I am running a Server 2012 deployment at one of my clients with networked printers loaded onto the server. I recently had an issue where one of my users was unable to print from a specific printer. When I then proceeded to check on the server side through Remote Desktop I was unable to remote into the server. Unfortunately during the time I did not record the error because I was able to physically gain access to the machine with no problem. However I had to restart the server because of the services that the server provided.
Now after the reboot and during some down time I went through the event viewer and these two DCOM errors kept repeating themselves for a long time within a 24 hour period. Please see below for the DCOM errors.
Log Name: System
The server <73e709ea-5d93-4b2e-bbb0-99b7938da9e4>did not register with DCOM within the required timeout.
Log Name: System
The server
Now I checked in my registry with the SID’s in the brackets to try to narrow it down.
The 73 had the following parameters:
The A6 had the following parameters
Now I am not sure exactly what caused the issue. My theories are either a possible print driver or something that was not fixed in Server 2012. After hours I ended up updating that Server 2012 with latest windows updates thinking maybe Microsoft had release some type of fix. However I am not super confident to make this server my backbone because of this issue with the printer locking up and not being able to remote desktop into the server until after a reboot. If someone has seen this specific issue with the above mentioned DCOM errors any help is appreciated. I have looked at many technet articles and other postings, but nothing seems to point to this error.
Ответы
Based on my research, Event ID 10010 may be related to many reasons.I recommend you refer to the similar threads below, although they are related to Windows server 2008 R2, they would also be helpful.
Все ответы
Based on my research, Event ID 10010 may be related to many reasons.I recommend you refer to the similar threads below, although they are related to Windows server 2008 R2, they would also be helpful.
Have you guys found a solution for this? I have the same problem.
Fresh install of Win 2012 r2 promoted to primary DC worked well for a week or so.
installed a few features (hyper v dns dhcp file print dfs etc)..
now about ever 4-5 days or so i see this WMI DCOM error cannot refresh server roles and features and have to reboot.
this also causes a problem with file shares and VSS shadows copies. Please HELP!
I also have the same problems:
— no servermanagement in spite of dom-admin (cannot get role and feature data)
— dcom error (73E709EA-5D93-4B2E-BBB0-99B7938DA9E4)
— shadow copies didn’t run
— snaphot related backup didn’t run
— after reboot, it works fine for several days
Does anyone have a solution?
Andreas, i have the same issue.
Do you have any Konika Minolta C220 or HP 5000 Printers?
If you look in Event Viewer, expand Applications and Services Logs, Microsoft, Windows, WMI-Activity, operational
Do you see frequent error loops such as :
Id =
Id = <9830001e-0f31-4d04-8f36-d8d18d89444a>; ClientMachine = PCNAME; User = DOMAIN\USER; ClientProcessId = 8252; Component = Unknown; Operation = Start IWbemServices::ExecMethod — root\Microsoft\Windows\ServerManager : MSFT_ServerManagerDeploymentTasks::GetServerComponentsAsync; ResultCode = 0x80080005; PossibleCause = Unknown
