DCOM error 10010 – finding the culprit

While cleaning up logs reports in check_mk – I came across a dcom error and thought it would be useful to document how to track down which supplier / app might be the cause of it. Specifically the message I was tracking down was

DCOM The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.

The Component Object Model (COM) infrastructure tried to start the named server; however, the server did not reply within the required timeout period. There might be a deadlock, or the program might not have responded to the server initialization code within the timeout period of two minutes.

To determine the program vendor:

Using Regedit, navigate to the following registry value HKCRClsidclsid valuelocalserver32 The clsid value is the information displayed in the message. In the right pane, double-click Default. The Edit String dialog box is displayed. Leave this dialog box open. Click Start, and then click My Computer. Using the information displayed in the Value data box of the Edit String dialog box, navigate to the program. Right-click the program name, and then click Properties. The Properties dialog box for the program is displayed. To determine who the vendor is for this program, refer to the Version tab.


Note the quickest way to get to the right key is to do a search and paste in the value of the key for example


is what you want to search for. And in my case its the BITS service.