Hi,

I am trying to setup item level recovery through Microsoft Data Protection Manager 2010 for our new Sharepoint 2010 website.  
I have Sharepoint 2010 installed on a virtual vmware server (called sharepoint 2010) and the databases are stored on a separate virtual vmware  server (called SQL2008) which is running SQL 2008 R2.

I have installed the DPM agent on both servers & rebooted them.  Next I tried to run the ConfigureSharepoint.exe command on sharepoint2010 but received the following error:

C:\Program Files\Microsoft Data Protection Manager\DPM\bin>configuresharepoint.exe -enablesharepointprotection
Enter the user name for 'WSSCmdletsWrapper': Domain\username
Enter the password for WSSCmdletsWrapper: *******
 
Object reference not set to an instance of an object.
 
An error occurred while trying to start the Sharepoint Vss Writer.

I have checked the VSS service - it was set to manual so I tried starting it and re-running the command, but I am still getting the same error.

Does anyone have any ideas?  Is it because the databases are stored on a separate server?  They were on the same box before.

Many thanks

This is a failure trying to start the SharePoint Vss Writer. We depend on sharepoint tools for this action.

Can you try the following.

1. Disable the SharePoint Vss Writer service and stop it completely.

2. Run stsadm -o unregisterwsswriter. stsadm.exe is a SharePoint tool which you'll find under%Program Files%\Common Files\Microsoft Shared\web server extensions\14\bin.

Now try running ConfiguresharePoint.exe -enableSharePointProtectionand see if it succeeds.

If you still run into the issue, you may check out if stsadm -o registerwsswriteris working or not. If that fails, probably there is some issue with your farm configuration. Please get in touch with sharepoint forums or contact microsoft support.

I have a SharePoint 2010 server and when I run the ConfigureSharePoint.exe I get a syntax error, can someone help me out?  I am running the comman prompt as Administrator

C:\Program Files\Microsoft Data Protection Manager\DPM\bin>ConfigureSharepoint.e
xe -EnableSharePointProtection

Syntax:
        ConfigureSharePoint.exe [-EnableSharePointProtection] | [-EnableSPSearch
Protection] | [-ResolveAllSqlAliases] | [-SetTempPath <Path>]

Requirement:
        This command should be run as a local administrator. For Windows 2008 on
wards, ensure that this command is run from an elevated command prompt.

Parameters:
        -EnableSharePointProtection
                Enables the protection of SharePoint farm. It registers the WSSC
mdletsWrapper DCOM object and enables the WSS VSS writer. When prompted to enter
 user name and password, enter the credentials of the SharePoint farm administra
tor.

        -EnableSPSearchProtection
                Enables the protection of WSS 3.0 Search and MOSS 2007 SSP. It r
egisters the WSSCmdletsWrapper DCOM object. When prompted to enter user name and
 password, enter the credentials of the SharePoint farm administrator.

        -ResolveAllSqlAliases
                This option can be run only after running -EnableSharePointProte
ction or -EnableSPSearchProtection on the server. It provides information about
all the SQL aliases reported by the WSS VSS writer and resolves them to the corr
esponding SQL Server instance names. If a SharePoint database is mirrored and co
nfigured with SQL alias then the corresponding mirror's SQL Server instance name
 is displayed as well. This option also reports all the SQL aliases that cannot
be resolved to any SQL Server.

        -SetTempPath <Path>
                Sets the environment variable TEMP and TMP to the specified path
.

• Proposed as answer by George Ene Monday, March 10, 2014 11:56 PM
• Unproposed as answer by George Ene Monday, March 10, 2014 11:56 PM

Hi.

The answer is MUCH more simple.....

Log into your Sharepoint server with your Farm Administrator account, then run the command.

Hope this helps

• Proposed as answer by krokebob Wednesday, June 06, 2012 6:59 AM

Hi.

The answer is MUCH more simple.....

Log into your Sharepoint server with your Farm Administrator account, then run the command.

Hope this helps

This worked perfectly - thanks

Thanks it works.!

It is not enough to run Command Promt as Farm Administrator if you are logged in with your server administrator account.  You must login to the server RDP with a Farm Administrator account.

• Edited by uzit 23 hours 6 minutes ago

Thanks it works.!

It is not enough to run Command Promt as Farm Administrator if you are logged in with your server administrator account.  You must login to the server RDP with a Farm Administrator account.

• Edited by uzit Tuesday, September 08, 2015 8:31 AM