Troubleshooting Windows SharePoint Services Protection Issues

Applies To: System Center Data Protection Manager 2007

The following table provides troubleshooting guidance on protection issues for computers running Windows SharePoint Services.

Windows SharePoint Services 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 using cliconfg.exe.

You must reconfigure the SQL Server alias using the SQL Server Configuration Manager.

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.

Protection of a Windows SharePoint Services farm fails.

If you protect a Windows SharePoint Services database as a SQL Server data source, protection of the Windows SharePoint Services farm will fail.

You must include the databases in a Windows SharePoint Services farm as part of the Windows SharePoint Services protection. You cannot directly protect the databases as a SQL Server data source.

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