Here’s a new Knowledge Base article we published today. This one walks you through fixing a issue where a DPM 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).
=====
For the most current version of this article please see the following:
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/