Troubleshooting Windows SharePoint Services Recovery Issues

  • Article

Applies To: System Center Data Protection Manager 2007

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

Windows SharePoint Services Recovery Issues

Issue Possible Cause Resolution

Recovery points are not displayed for sites or documents in DPM Administrator Console in the Recovery task area. (If you double-click the Content databases, the sites do not appear.)

If the Windows SharePoint Services farm administrator account is not a local administrator on the front-end Web server, after the farm backup DPM fails to perform the catalog operation. If the catalog operation fails, DPM only performs farm and database recovery.

Make the Windows SharePoint Services farm administrator a local administrator on the front-end Web server on which the protection agent is installed.

After recovering a Windows SharePoint Services farm, you cannot attach a content database.

If you recover a Windows SharePoint Services farm that had a detached database prior to recovery, you cannot attach the database after the recovery if the front-end Web server was different than the database DPM used for the recovery.

To resolve this issue, do the following:

  • Delete the config cache on the front-end Web server that was not used for the recovery.

    The cache is a set of XML files located in the following folder: <drive letter>:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\<config database ID>.

    Warning

    Do not delete the folder. Delete only the XML files in the folder.

  • The cache will automatically rebuild, enabling you to attach the database.

Recovery of the Windows SharePoint Services farm fails.

If a Quick Fix Engineering (QFE) is installed after the Windows SharePoint Services farm is protected, the recovery will fail.

To resolve this issue, do the following:

  1. Recover the Windows SharePoint Services farm using the Recovery Wizard.

  2. On the front-end Web server, from the command prompt, type psconfig -cmd upgrade -wait -force -inplace b2b.

Consistency check fails with "Data source not found".

If you perform a recovery after the content database is deleted from SQL Management Studio, and not through the Sharepoint Console, the consistency check will fail.

You must stop protection, and then use the New Protection Group Wizard to reprotect the Windows SharePoint Services farm.