System Center Data Protection Manager SharePoint Catalog Task fails with Unknown error (0x8013151a)

Symptoms

 Symptom 1: While attempting to protect a SharePoint 2010 farm with System Center Data Protection Manager 2010 (DPM) you get the following error:

Backup Metadata enumeration failed

Symptom 2: After successfully protecting SharePoint 2010 with System Center Data Protection Manager 2010, after a period of time the SharePoint catalog task fails with the following error and alerts:

Type:     SharePoint Catalog Task
Status:   Failed
Description:        DPM Agent on the SharePoint front-end Web server sp10.corp.local is not configured appropriately. DPM was unable to invoke WssCmdletWrapper DCOM component successfully. (ID 32019 Details: Unknown error (0x8013151a) (0x8013151A))
               More information
End time:            
Start time:          
Time elapsed:     00:00:02
Data transferred:              0 MB (0 bytes)
Source details:   name.corp.local
Target details:    name.corp.local
Cluster node       -

Where ErrorCode: 0x8013151A (-2146233062): COR_E_MEMBERACCESS: Access to this member is denied.

Affected area:    Sharepoint Farm\SP10\SharePoint_Config
Occurred since: 
Description:        DPM could not obtain backup metadata information for SharePoint Farm Sharepoint Farm\SP10\SharePoint_Config on name.corp.local. If the data source is a SharePoint farm then a valid recovery point has been created. However, content databases from this recovery point can be recovered using the alternate location option only. (ID 3134)
               More information
Recommended action:   
               If the data source is a SharePoint farm, then
1) Ensure that "ConfigureSharePoint.exe -EnabledSharePointProtection" has been run on the front-end web server with the current SharePoint farm administrator credentials.
2)Ensure that the SharePoint VSS writer is running on the front-end web server.
Resolution:         DPM automatically changes this alert's status to inactive 10 days after it is issued.To dismiss the alert, click below
               Inactivate alert


Affected area:    Sharepoint Farm\SP10\SharePoint_Config
Occurred since: 
Description:        DPM failed to gather item level catalog for 3 database(s) of the SharePoint Farm Sharepoint Farm\SP10\SharePoint_Config on name.corp.local. Some of the recovery points for these databases in the farm would be associated with an earlier successful catalog. (ID 3133)
               More information
Recommended action:   
               To re-run the catalog job manually for the farm, run Start-CreateCatalog command in PowerShell.
Resolution:         DPM automatically changes this alert's status to inactive 10 days after it is issued.To dismiss the alert, click below
               Inactivate alert

If you look in the C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\WSSCMDLETSWRAPPERCURR.ERRLOG on the SharePoint web front end server, the only details after each sharepoint catalog task failure are these three lines.

1278  0C14  05/21  15:53:40.611  31  wsscmdletswrapperfactory.cpp(235)                           ACTIVITY             Principal name HOST/SP10.corp.local@corp.local
1278  0774   05/21 15:53:41.994  31  wsscmdletswrapper.cpp(143)   [00000000001DFA50]  WARNING           CoCreateInstance failed for CLSID_CWSS3Cmdlets : {40B0FC9C-A853-3F52-B677-A81B2D0F17AE}
1278  0774   05/21 15:53:41.995  31  wsscmdletswrapper.cpp(144)   [00000000001DFA50]  WARNING           Failed: Hr: = [0x8013151a] : F: lVal : hr

If you attempt to re-run the ConfigureSharePoint.exe -EnabledSharePointProtection on the Web front end server, it also fails with the below error:

C:\Program Files\Microsoft Data Protection Manager\DPM\bin>configuresharepoint -enablesharepointprotection
Enter the user name for 'WSSCmdletsWrapper': domain\usernamer
Enter the password for WSSCmdletsWrapper:

Unhandled Exception: System.MissingMethodException: Method not found: 'Void Microsoft.Sharepoint.SPRequestManager.Dispose()' .
   at Microsoft.SharePoint.StsAdmin.SPStsAdmin.Main(String[] args)
An error occured while trying to start the sharepoint vss writer

Cause

 The Sharepoint 2010 front end server has the following registry key present:

 HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0

DPM interprets the presence of that key as indicating that SharePoint 3.0 is installed on the server, therefore it uses different logic to call into the SharePoint DCOM components by trying to use different or non-existent .dll files.

Resolution

This issue is fixed in the following DPM 2010 rollup fix.

2615782 - A hotfix that enables interoperability with Microsoft System Center Data Protection Manager 2012 RC is available for System Center Data Protection Manager 2010 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;2615782). 

More Information

 

INFORMATIONAL ONLY - PRIOR TO THE ABOVE FIX THIS WAS THE WORKAROUND.

1) Check to see if the customer has Foxit Software PDF Ifilter product installed.  http://www.foxitsoftware.com/pdf/ifilter/  That product adds the offending HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0 registry key.  Un-install the product* to allow DPM to protect the farm and create catalogs.

*NOTE: Working with a customer who reported that backing up and removing the 12.0 reg key allowed DPM to function and FoxIt continued to work as well.  This has not been verified beyond the customer's limited testing, but should be considered the first option if customer is using FoxIt as it allows continued use of the product.

2) It is possible some other product installed on the system has added that key, If the HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0 is present - export that key then delete it.

NOTE:  There is a MS feature in Windows 2008 R2 which creates the very same key HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
             The feature is called "Windows TIFF IFilter"

NOTE: On an SBS 2010 server - It appears that Exchange 2010 creates the offending key. The key contains a subkey named IRMProtectors.  I assume that this key is created to assist with rights management but I am not sure. Don't delete the key without know how it will effect exchange.

 

 

Properties

Article ID: 2182903 - Last Review: Apr 17, 2012 - Revision: 1

Feedback