Windows SharePoint Protection Issues
Applies To: System Center Data Protection Manager 2010
The following table provides troubleshooting guidance on protection issues for computers running Windows SharePoint Services.
Windows SharePoint Protection Issues
| Issue | Possible Cause | Resolution |
|---|---|---|
The SQL Server alias did not resolve on the SQL Server Agent and protection for the Windows SharePoint Services farm fails. |
The Windows SharePoint Services farm is unable to use a SQL Server alias that was created by using cliconfg.exe. |
You must reconfigure the SQL Server alias by using the SQL Server Configuration Manager. |
Not all the SQL Server aliases are configured on the front-end Web server. |
Check the list of servers on the Central Admin page of the SharePoint farm. Identify the SQL Server aliases from the list of SQL Server computers. Verify if all the SQL Server aliases have been configured on the SharePoint front-end Web server (the one that communicates with the DPM server). |
|
The SQL Server alias is not of type TCP/IP. |
DPM supports only TCP/IP SQL Server aliases. Reconfigure the aliases to type TCP/IP. |
|
SQL Server client connectivity components are not installed on the front-end Web server. |
Install the SQL Server client connectivity components on the front-end Web server. |
|
For Windows SharePoint Services 3.0/MOSS 2007 farms, SQL Server 2005 client connectivity components are not installed on the front-end Web server. |
Irrespective of the version of SQL Server on the back-end servers, for MOSS 2007 and Windows SharePoint Services 3.0, you should install the SQL Server 2005 client connectivity components on the front-end Web server. Also, ensure that all the aliases are configured using this version of the client connectivity components. |
|
Windows SharePoint Services database log files are not truncated. |
If the path to any Windows SharePoint Services database log file exceeds 150 characters, DPM cannot truncate the log file. |
We recommend running periodic scripts to truncate your Windows SharePoint Services database log files. |
The Copy-Only registry value has been set for the specific SharePoint farm on the DPM server. |
This registry entry needs to be deleted. It can be found under the following path on the DPM Server: “HKLM\Software\Microsoft\Microsoft Data Protection Manager\CopyBackups” with the name equivalent to the name of the Config database of the farm. |
|
The “Do not truncate logs” setting has been enabled for the SQL Server computer on which the SharePoint databases reside. |
This can be reset by using the following Windows PowerShell command: |
|
The server process could not be started because the configured identity is incorrect. Check the username and password (0x8000401A). |
If the password is reset for the Windows SharePoint Services farm, protection will fail. |
From the command prompt, run ConfigureSharePoint.exe to reset the password. For more information about how to manage password changes, see How to change service accounts and service account passwords in SharePoint Server 2007 and in Windows SharePoint Services 3.0 (https://go.microsoft.com/fwlink/?LinkId=126982). |
Replica Inconsistent alerts for one or more SQL Server databases that were earlier a part of the SharePoint farm appear in the Monitoring pane. |
DPM retains the existing recovery points of the databases that have been removed from the SharePoint farm. This can happen if the removed database is recovered by using DPM or if DPM has been upgraded. |
Resolve the alert by clicking Inactivate the alert. |
Some of the SharePoint farm’s consistency check jobs appear to have stopped (no data transfer has occurred for a long time). |
The consistency check was triggered while recovery of one of the farm’s components was in progress. |
Cancel the consistency check job and restart the consistency check for the farm from the Protection pane. |
The SharePoint catalog task fails with HR 0x80004003 (Invalid Pointer) |
There is a network connectivity issue between the SharePoint front-end Web server and the back-end server. |
Rerun the catalog job by using Windows PowerShell. |