Error 32008 When Trying To Protect WSS 3.0/SP1 with DPM 2007
Hi I'm having some problems protecting my SharePoint farm. I am running Server 2008 X64 VM using Hyper-V. With SQL 2005 64 Bit, MOSS 2007 SP1, and SharePoint Services 3.0 SP1 When I attempt to add the farm to a protection group I get the error message below. I have checked and rechecked and all these services are definitely running. I also read a post at another forum from that suggested running wssv3-kb934525-fullfile-x64-glb.exe to resolve the problem. However when I attempt to run it I get a message saying "The expected version of the product was not found on the system." --------------------------- Microsoft System Center Data Protection Manager 2007 --------------------------- This Windows SharePoint Services farm cannot be protected because DPM did not find any dependent databases and search indices to be protected. (ID: 32008)1) Verify that the appropriate SQL Server VSS Writers on the computers hosting the Windows SharePoint Services databases are enabled. 2) Verify that the Windows SharePoint Services Search VSS Writers are enabled on the computers where the search indices are. --------------------------- OK Any assistance would be appreciated. Thanks, Adam
March 3rd, 2009 8:29am
Hi Adam There are a number of computer requirements which have to be completed before you will be able to create and protect a server successfully. Protected Computer Software Prerequisiteshttp://technet.microsoft.com/en-us/library/bb808827.aspx 1. You must install KB article 941422 on all the protected servers on which Windows SharePoint SharePoint Services 3.0, Microsoft Office SharePoint Server 2007, and Microsoft Office SharePoint Server 2007 SP1 are installed. http://www.microsoft.com/downloads/details.aspx?FamilyID=78549f3c-3cd2-445e-9dc0-417ca5a4a079&DisplayLang=en 2. Start the WSS Writer service on the WSS Server and then provide the protection agent with credentials for the WSS farm. Starting and Configuring the WSS VSS Writer Service http://go.microsoft.com/fwlink/?LinkId=100247 3. Update the instance of SQL Server 2005 to SQL Server 2005 SP2. 4. Install the SQL Server Client components on the front-end web server of the Windows SharePoint Services farm that DPM is going to protect. For information about installing SQL Server components, see How to: Install SQL Server 2008 http://go.microsoft.com/fwlink/?LinkId=110346 In addition to the above information please be sure to do the following on the Windows SharePoint server: 1. Open Services MMC and set both the Windows SharePoint Search and Windows SharePoint Services VSS Writer are set to Automatic and started. 2. Open a command prompt change the directory to C:\program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN from this directory run the following command; stsadm.exe -o registerwsswriterOnce this all has been completed walk through the process of creating a Protection Group for the SharePoint server and see if the issue has been resolved. Hope this helps. Lu Zou
March 5th, 2009 10:26am
Hi Lu Zou, I follow those steps, but I still have a problem. In DPM 2007, I have a "blank" instead of the name of my SharePoint DB. When I tick the boxe, I have the 32008 error which tells me to check the Vss writers on SQL server... Environment : 1 server x64 : WSS 3.0 SP2 + Search server Express 2008 2 server x64 : SQL 2005 SP3 I try to protected a stand alone installation of sharepoint on a VM and it works. So I think that DPM 2007 is working well. I hope you can help me...
October 12th, 2009 6:47pm
I'm having the same issue. Have you resolved this? I'm using SQL 2008 versus SQL 2005.
March 20th, 2010 1:11am