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