Description Event ID:10010 Shows up in event viewer every month sometimes twice a month.
What is causing this and how do I fix it?
OS: Server 2008 R2 SP1
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 1/19/2011 3:37:15 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WB-DC01-------
Description:
The server {752073A1-23F2-4396-85F0-8FDB879ED0ED} did not register with DCOM within 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="2011-01-19T21:37:15.000000000Z" />
<EventRecordID>8223</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>wb-dc01--------</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">{752073A1-23F2-4396-85F0-8FDB879ED0ED}</Data>
</EventData>
</Event>
January 13th, 2012 1:25pm
General info on this error is here
http://technet.microsoft.com/en-us/library/cc774175(WS.10).aspx
Regards
Milos
Free Windows Admin Tool Kit Click here and download it now
January 13th, 2012 3:13pm
Two ways to fix this:
1. Launch Notepad.
2. Paste the following content in Notepad.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{752073A1-23F2-4396-85F0-8FDB879ED0ED}]
@="Component Based Servicing Session"
"AppID"="{752073A2-23F2-4396-85F0-8FDB879ED0ED}"
3. Save to Desktop, with the name CID.reg.
4. On Desktop, launch the file CID.reg.
It may prompt that this task would modify the Registry. Please allow it to change.
The second way:
1. In the registry we must set the Registry Size Limit to "unlimited":
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
Key: RegistrySizeLimit
Type: REG_DWORD
Value: 0xffffff (4294967295)
2. Reboot
3. As a Administrator open a Command Prompt and run "SFC /SCANNOW". The command should complete successfully and if any errors were found, they should be corrected.
January 18th, 2012 12:36pm