From: mrceolla on
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
From: Larry Struckmeyer[SBS-MVP] on
Sorry, I assumed that if you have gotten as far as you had in the post to
which I replied that you must be following the instructions from some article.

I have not followed the thread, but since you ask me directly in your post
below, if you have not already seen this, you might want to look here:

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

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com


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


From: Ace Fekay [MCT] on
"Larry Struckmeyer[SBS-MVP]" <lstruckmeyer(a)mis-wizards.com> wrote in message
news:4e6835154d3f8cc2ab303a7fb2d(a)news.microsoft.com...
> Sorry, I assumed that if you have gotten as far as you had in the post to
> which I replied that you must be following the instructions from some
> article.
>
> I have not followed the thread, but since you ask me directly in your post
> below, if you have not already seen this, you might want to look here:
>
> http://www.eventid.net/display.asp?eventid=10010&eventno=508&source=DCOM&phase=1
>
> -
> Larry
> Please post the resolution to your
> issue so others may benefit


james Hurrell had posted this earlier in the thread.

A suggestion and recommendation for mrceolla: If you don't feel comfortable
following each and every step in the KB article to take care of this
problem, I would highly suggest at this time to call Microsoft PSS to assist
you in resolving it. In the US, it's around a USD $255 charge per incident,
no matter how long it takes, unless of course you have an SA agreement with
Microsoft, which is should be one of your free support calls provided with
the agreement.

You never know, if an update caused it, it will be free of charge.
Otherwise, I think at this time the small investment is well worth your
peace of mind.

And please do let us know what the resolution is if you call PSS. If you can
share it, it will be searchable and will help others.

Ace


From: Dave Nickason [SBS MVP] on
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" <mrceolla(a)gmail.com> wrote in message
news:d4c5910d-d59c-484c-a0a4-339e87fdfd9a(a)b15g2000yqd.googlegroups.com...
> 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

From: mrceolla on
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 didn't get the error at all yesterday. This is the first day I've
gone without one, usually two of these errors. Before I do anything
else I'm 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 don't think the RAM fixed anything.
Who knows. We'll see. I will report back.

Mike