Windows Server - Event ID 10010 DCOM error on SBS 2008

Asked By mrceolla

02-Nov-09 12:22 PM

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:
B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

02-Nov-09 12:32 PM

Any help here? Usually my first port of call:

http://www.eventid.net/display.asp?eventid=10010&eventno=508&source=DCOM&phase=1

02-Nov-09 01:20 PM

Unfortunately, no.  I came across that page earlier in my searches.
My GUID is

0B5A2C52-3EB9-470A-96E2-6C6D4570E40F

...which does not appear on that page.

Since the fixes for this event id seem to depend on the reported GUID
I do not believe any of those solutions will help.

Any other ideas?  Anyone from MS available to help me with this?

Thanks,
Mike

02-Nov-09 12:59 PM

Have you searched the registry for the CLISID string
,"0B5A2C52-3EB9-470A-96E2-6C6D4570E40F" to see what service or application
it is associated to?

Have you looked in Component services for that CLSID String?


--
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.

02-Nov-09 06:04 PM

Ace,

Yes, in HKEY_CLASSES_ROOT\CLSID\ the value is "VssSnapshotMgmt Class"
and the AppID is "{56BE716B-2F76-4dfa-8702-67AE10044F0B}" which
appears to be Volume Shadow Copy Service.

I do not know how to search Component Services for the CLSID.

Thank you for your continued help.

Mike

02-Nov-09 05:38 PM

Here is a thread with instructions from a MS support rep
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/fb4cbe98f89ce266/d7a041d29c8d7459?hl=en&ie=UTF-8&oe=UTF-8&q=%7B0B5A2C52-3EB9-470A-96E2-6C6D4570E40F%7D

02-Nov-09 06:04 PM

le.com/group/microsoft.public.windows.server.sbs/br...

Thanks Dave, but I already went through that thread.  The original
author's problem was not 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

02-Nov-09 06:10 PM

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?



Thanks Dave, but I already went through that thread.  The original
author's problem was not 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

03-Nov-09 01:38 AM

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

doing):"
http://blogs.msdn.com/adioltean/archive/2004/12/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.

03-Nov-09 09:18 PM

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 do not 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 have 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

04-Nov-09 11:55 AM

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

05-Nov-09 10:49 AM

Hello all,

Thank you once again for your posts.

Larry, I had already looked at that eventid.net page as explained
above.  It did not offer any related help.

I did not get the error at all yesterday.  This is the first day I have
gone without one, usually two of these errors.  Before I do anything
else I am going to give it one more day and see if it occurs again.
Nothing has changed software wise on the server.  Though I did add
some more RAM earlier this week.  But since the error happened once
right after I installed the RAM I do not think the RAM fixed anything.
Who knows.  We'll see.  I will report back.

Mike

10-Nov-09 11:05 AM

Hello again,

Well, that error has not 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 have been something else I did but I had not 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 is gone.

Thanks again for all of your help/advise.

Have a great day!

Mike

10-Nov-09 11:58 AM

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.

01-Feb-10 05:42 PM

Hi mrceolla,

if it work with instructions above? :-) ?