Re: Event ID 10010 DCOM error on SBS 2008

Here's a thread with instructions from a MS support rep
http://groups.google.com/group/micro...C6D4570E40F%7D


"mrceolla" <> wrote in message
news:70c22a58-57e6-4708-b337-...
> Hello,
>
> I have searched all over and can not find a solution to this error.
> It happens usually twice, sometimes only once, per day. It appears it
> has something to do with VSS. Any help would be greatly appreciated.
>
> Have a great day,
> Mike
>
> Log Name: System
> Source: Microsoft-Windows-DistributedCOM
> Date: 11/1/2009 1:50:34 PM
> Event ID: 10010
> Task Category: None
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: SERVER.domain.local
> Description:
> The server {0B5A2C52-3EB9-470A-96E2-6C6D4570E40F} 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="2009-11-01T19:50:34.000Z" />
> <EventRecordID>57601</EventRecordID>
> <Correlation />
> <Execution ProcessID="0" ThreadID="0" />
> <Channel>System</Channel>
> <Computer>SERVER.domain.local</Computer>
> <Security />
> </System>
> <EventData>
> <Data Name="param1">{0B5A2C52-3EB9-470A-96E2-6C6D4570E40F}</Data>
> </EventData>
> </Event>

Did you go through all the steps the MS rep suggested? It seems like the OP
on that thread either abandoned troubleshooting or went in some other
direction (like calling MS support, which is something you could consider
given the seeming lack of other good options).

You're not running any 3rd party backup software, right? Any symptoms other
than the logged error?


"mrceolla" <> wrote in message
news:9a43e724-3962-4f96-8e79-...
On Nov 2, 4:38 pm, "Dave Nickason [SBS MVP]"
<gwdib...@NOSPAM.frontiernet.net> wrote:
> Here's a thread with instructions from a MS support
> rephttp://groups.google.com/group/microsoft.public.windows.server.sbs/br...
>

Thanks Dave, but I already went through that thread. The original
author's problem wasn't solved after these steps. I went through and
performed some of the same checks anyway just to be sure. But again,
this guy had the same problem I do and this MS support rep did not
find a solution for him...at least from what I can tell in this
thread. The original author, Scott, just stops replying.

More help, please.

Mike

> On Nov 2, 4:38*pm, "Dave Nickason [SBS MVP]"
> <gwdib...@NOSPAM.frontiernet.net> wrote:
>> Here's a thread with instructions from a MS support
>> rephttp://groups.google.com/group/microsoft.public.windows.server.sbs/br...
>>
>
> Thanks Dave, but I already went through that thread. The original
> author's problem wasn't solved after these steps. I went through and
> performed some of the same checks anyway just to be sure. But again,
> this guy had the same problem I do and this MS support rep did not
> find a solution for him...at least from what I can tell in this
> thread. The original author, Scott, just stops replying.
>
> More help, please.
>
> Mike

Have you disabled any services on SBS? Please read the following to see
what I mean.

"Don't disable system services! (unless you REALLY know what you are
doing):"
http://blogs.msdn.com/adioltean/arch...26/332540.aspx

What third party or other Microsoft products have you installed on the
server?

Ace

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

I don't have an SBS 08 nearby to compare permissions. I don't think you're
likely to have any issues with adding Local System, especially if you've
seen that documented. Whenever I do anything with COM settings or anything
related, I keep written notes in case I have to undo something.


"mrceolla" <> wrote in message
news:d4c5910d-d59c-484c-a0a4-...
> Thank you all for your replies.
>
> Dave, no, I did not perform every single step. Some of them seem to
> not apply and others I am not comfortable with (ie. "msdtc -
> uninstall", deleting registry hives).
>
> One of the steps, outlined below, mentions "Local System" permissions
> in Component Services MMC but I don't have Local System listed in
> either Access Permissions or Launch and Activation Permissions:
>
> Please make sure that proper permissions are set to Access, Lunch and
> Activation in COM security. To check that:
>
>
> 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.
>
> Should I add "Local System" to the list? I was hesitant to do so
> because I figured it would've been at least in the list already.
> Maybe with incorrect permissions but at least in the list. Could one
> of you check your install for Local System in those permission lists?
>
> I am not using 3rd party backup software and there are no other
> suspect apps on the server. This is a very fresh, fully patched
> install. There are currently no other apps to speak of other than
> some HP management utilities (ACU) that only run when launched...no
> service type stuff or anything.
>
> Larry, I believe the friendly name is "VssSnapshotMgmt Class." But
> what KB article are you referring to?
>
> Ace, I have not disabled any SBS services. Any our backups run every
> night without reporting any errors.
>
> Thank you all again for your help. Any further suggestions?
>
> Mike

Interesting. I wonder if the extra performance from the added RAM made the
difference, especially since the original error message referenced a
timeout. Anyway, glad you got it sorted out, and thanks for the update.


"mrceolla" <> wrote in message
news:cdb88610-c9ee-4be0-819b-...
> Hello again,
>
> Well, that error hasn't happened in a few days. My wild guess is that
> adding RAM to the machine (went from 4 to 12) must have changed
> something. And the only reason I attribute it to the RAM is because
> the day after I added the RAM is when the errors stopped. Of course
> it could've been something else I did but I hadn't performed any
> additional troubleshooting steps between the last time I got the error
> and when I put the RAM in. Oh well. At least it's gone.
>
> Thanks again for all of your help/advise.
>
> Have a great day!
>
> Mike
>

Hi mrceolla,

if it work with instructions above? :-) ?

"Dave Nickason [SBS MVP]" wrote:

> Here's a thread with instructions from a MS support rep
> http://groups.google.com/group/micro...C6D4570E40F%7D
>
>
> "mrceolla" <> wrote in message
> news:70c22a58-57e6-4708-b337-...
> > Hello,
> >
> > I have searched all over and can not find a solution to this error.
> > It happens usually twice, sometimes only once, per day. It appears it
> > has something to do with VSS. Any help would be greatly appreciated.
> >
> > Have a great day,
> > Mike
> >
> > Log Name: System
> > Source: Microsoft-Windows-DistributedCOM
> > Date: 11/1/2009 1:50:34 PM
> > Event ID: 10010
> > Task Category: None
> > Level: Error
> > Keywords: Classic
> > User: N/A
> > Computer: SERVER.domain.local
> > Description:
> > The server {0B5A2C52-3EB9-470A-96E2-6C6D4570E40F} 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="2009-11-01T19:50:34.000Z" />
> > <EventRecordID>57601</EventRecordID>
> > <Correlation />
> > <Execution ProcessID="0" ThreadID="0" />
> > <Channel>System</Channel>
> > <Computer>SERVER.domain.local</Computer>
> > <Security />
> > </System>
> > <EventData>
> > <Data Name="param1">{0B5A2C52-3EB9-470A-96E2-6C6D4570E40F}</Data>
> > </EventData>
> > </Event>
>
> .
>