The server did not register with DCOM within the required timeout

 

Sometimes after upgrading your Windows OS, the System Logs under Event Viewer may display the following error message: Event ID 10010 error – The server did not register with DCOM within the required timeout. What does this DCOM error message signify and how can you fix this error? These are some of the questions we’ll have answered in today’s post.

The server did not register with DCOM within the required timeout

Before proceeding further, first, let us know what DCOM is. DCOM or Distributed Component Object Model is a proprietary Microsoft technology that allows Component Object Model (COM) software to communicate across a network. You can consider it as an extension of COM, equipped with the capability of solving a few inherent problems associated with the COM model to better use over a network.

Component Services needs the DCOM wire protocol to communicate with the Component Object Model (COM) components on other computers. In a Windows-based system, by default, network computers are initially configured to enable DCOM.

What’s COM? It’s a tool used for advanced configuration and troubleshooting in Windows 10. The developers often use it to configure routine component and application behavior, such as participation in transactions and object pooling, etc. Also, some components in Windows might require registering themselves with DCOM. If they fail to do so, you’ll get this message.

To fix this issue, go thorugh the post first and then try the suggestions:

1] Use Component Services

Open the ‘Run’ dialog box, type ‘dcomcnfg’ in the empty box and hit ‘Enter’ to open ‘Component Services’.

In the right-pane double-click ‘Computers’ folder then, right-click ‘My Computer’ and select ‘Properties’ option.

component-services-4469772

Under ‘My Computer Properties’, switch to ‘COM Security’ tab and move to the ‘Access Permissions’ section. There, hit the ‘Edit Default’ tab.

access-permissions-2515441

Now, in the new window that opens up, apply the correct permission to objects under Group or user names section.

remote-access-2397423

When done, click OK and exit.

This should resolve your problem.

2] Ensure that Function Discovery Resource Publication Properties Services is running

Type ‘Services’ in the Windows 10 Search box and press ‘Enter’.

Scroll down to locate ‘Function Discovery Resource Publication’ entry.

function-discovery-resource-publication-4984619

Double-click on it and switch to ‘General’ tab.

Ensure that the ‘Startup’ type is set to ‘Manual (Triggered)’.

Click ‘Apply’ to allow the changes to take effect.

Also, ensure that the Service is running. If not, click on the Start button to start the service.

3] Reset default DCOM permissions

the-server-did-not-register-with-dcom-8203472

Click Start and select Run, type dcomcnfg, and press Enter to open ‘Component Services’.

Expand Component Services > Computers, right-click My Computer and select Properties.

In the Default Distributed COM Communication Properties section of Default Properties tab, make sure that:

  • Default Authentication Level is set to Connect
  • Default Impersonation Level is set to Identify.

This should help!

Original Article