DCOM 10010 Error on SBS 2008.

[MSFT]

Sponsored Links

We are having a SBS 2008 server since past one year. It was working fine without any problems but since past week, something went wrong which is generating the following error every night in the Event Viewer log:

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 12/16/2008 9:15:13 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DDISERVER1.ddinc.local

Description:
The server {0B5A2C52-3EB9-470A-96E2-6C6D4570E40F} did not register with DCOMwithin the required timeout.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM"
Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="49152">10010</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-12-17T02:15:13.000Z" />
<EventRecordID>56722</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>DDISERVER1.ddinc.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">{0B5A2C52-3EB9-470A-96E2-6C6D4570E40F}</Data>
</EventData>
</Event>

Somebody please help?

[HELLIAN]

Most probably the error is related to Microsoft Visual SourceSafe. As your event log points to the key {0B5A2C52-3EB9-470A-96E2-6C6D4570E40F}, unfortunately I’m not able to find the COM with that ID on my SBS 2008 hence am sure there is some application on your server which is related to this. You will need to find out the same. In order to locate that application, follow these steps:

• Open registry editor and navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\
• Here search for that Application ID. See with which application it is associated with.

[Janos™]

You are correct, even I’m sure the problem is related to VSS. He should better check if VSS related applications are registered in the AppID properly. You need to check the following VSS applications:

[HKEY_CLASSES_ROOT\AppID\{4db9c793-c48d-449c-9754-46027ee45c94}] Microsoft Volume Shadow Copy Service software provider
[HKEY_CLASSES_ROOT\AppID\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}] VssEvent
[HKEY_CLASSES_ROOT\AppID\{56BE716B-2F76-4dfa-8702-67AE10044F0B}] Volume Shadow Copy Service

If any one of these ID is missing then obviously VSSsnapshot will not start and generates Event 10010 with the error you mentioned above. In order to correct this you can copy the following strings, save it as *.reg file and then import it to the registry.

Hope it helps.

[MSFT]

Thanks for the help. All three are currently registered in the AppID properly.

I broke the report into 4 sections and sent them to you.

[Debbie Rowe]

Hello MSFT, ensure that proper permissions are set to Access, Lunch and Activation in COM security. You can check it with the following steps:

1. Click Start, click Run, type "dcomcnfg" (without the quotation marks) in the Open box, and then click OK.
2. In the Component Services MMC, right click the My Computer--->Properties--->COM security.
3. In the "Access permissions" and "Lunch and Activation Permissions", verify whether the local system, administrator, and everyone have the Local Access, Local Lunch and Local Activation permissions.

[ronald.ronmartin]

Hi,
I have done all the Possibility to resolve this event id:10010 issue.
in my SERVER but still log is generating.
is there any one here to help me.?


Error: The server {7D1933CB-86F6-4A98-8628-01BE94C9A575} did not register with DCOM within the required timeout.

- System

- Provider

[ Name] Microsoft-Windows-DistributedCOM
[ Guid] {1B562E86-B7AA-4131-BADC-B6F3A001407E}
[ EventSourceName] DCOM

- EventID 10010

[ Qualifiers] 49152

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2013-04-21T11:03:06.000000000Z

EventRecordID 133723

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel System

Computer ExchangeSVR.Gen3Com.local

Security


- EventData

param1 {7D1933CB-86F6-4A98-8628-01BE94C9A575}

[EINSTEIN_007]

Originally Posted by ronald.ronmartin

Hi,
I have done all the Possibility to resolve this event id:10010 issue.

This problem occurs because the Windows Explorer operating system shell is not running on the terminal server. When a Component Object Model (COM) object tries to register, it posts a registration message to the Windows Explorer shell. For more information visit this website - http://support.microsoft.com/kb/873375