Archive

Posts Tagged ‘nugget’

Volume Shadow Copy Service Error

March 1, 2012 Leave a comment

Or the perils of setting up search with SharePoint…

This is only a Nugget, which is far less than a snack.

When you see stuff like this:

image

It’s kinda important to resolve. Oh wait, I’m contributing to the “Downfall of the English Language”<<again – big announcer voice>> with kinda instead of “kind of”… my transgression… sorry.

First the error

Volume Shadow Copy Service error: The process that hosts the writer with name OSearch14 VSS Writer and ID {0ff1ce14-0201-0000-0000-000000000000} does not run under a user with sufficient access rights. Consider running this process under a local account which is either Local System, Administrator, Network Service, or Local Service.

Operation:
   Initializing Writer

Context:
   Writer Class Id: {0ff1ce14-0201-0000-0000-000000000000}
   Writer Name: OSearch14 VSS Writer

After some searching points to the following technet article.

http://technet.microsoft.com/de-de/library/cc734219(en-us,WS.10).aspx

I’ve applied this and we’ll see if the error falls away.

Then there’s this:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{000C101C-0000-0000-C000-000000000046}
and APPID
{000C101C-0000-0000-C000-000000000046}
to the user <domain>\<accountname>SID (S-1-5-21-40860068-1898212740-1415713722-7245) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

So, I quickly go to the usual suspect (thinking I’m cool and I know this rodeo) and check out:

image

Hmmmmm… this account is already set up there.  What the heck?  So, it’s time to open RegEdit and see what 000C101C-0000-0000-C000-000000000046 points to.

It says MSI Server… well, this is not an app that is easily coerced so maybe it’s something else.  I recall from my earlier exploits that ForeFront has to run and the particular account in this instance has to play nice with that.  So I checked The ForeFront Set of permissions…

image

The last entry had not been set up so the account had activation permissions.  Well, that’s been changed and I’ll see if that reduces or eliminates the error.

Categories: SharePoint Tags: