I'm attempting to backup a MOSS 2007 farm with DPM 2007 SP1.  More often than 
not it works great, but more often than I'd like it "succeeds" with the 
following errors which leaves me unable to do item-level restores.

Affected area:	Sharepoint Farm\simcspdb\SharePoint_Config
Occurred since:	3/4/2010 11:11:41 PM
Description:	DPM failed to obtain catalog information as part of the backup 
for SharePoint Farm Sharepoint Farm\simcspdb\SharePoint_Config on 
simcspwf.sawdustmgmt.local. Your recovery point is valid, but you will be 
unable to perform item-level recoveries using this recovery point. (ID 3103)
Recommended action:	1) If you do not expect to be performing item-level 
restores using this recovery point, then dismiss this alert; otherwise, take 
the recommended actions in the subsequent steps.
2) If the operation failed for a short-term backup to disk, in the 
Protection task area, select the data source and click Create recovery point 
to restart the backup. 
3) If the operation failed for a short-term backup to tape, in the 
Protection task area, select all the failed data sources that belong to the 
same protection group, and click Create recovery point – tape. This will 
ensure that the tape backups are located on the same tape. 
4) Dismiss this alert immediately after starting your backup.
Resolution:	DPM automatically changes this alert's status to inactive 10 
days after it is issued.To dismiss the alert, click below


I've checked the WssCmdletsWrapperCurr.errlog and it give me the following 
three lines each time this occurs (the specific identifiers change, of course)

0B90	1528	03/04	05:10:08.623	38	WSSCatalogGeneratorIncremental.cs(798)			Couldn't 
process change 
1;0;dd6a327e-cb15-435e-a802-791727099f3a;634032281955770000;3032149
0B90	1528	03/04	05:10:20.201	38	WSSCatalogGeneratorIncremental.cs(798)			Couldn't 
process change 
1;0;dd6a327e-cb15-435e-a802-791727099f3a;634032456674770000;3033134
0B90	1528	03/04	05:10:20.248	38	WSSCatalogGeneratorIncremental.cs(798)			Couldn't 
process change 
1;0;dd6a327e-cb15-435e-a802-791727099f3a;634032460189400000;3033138

How can I troubleshoot these errors?

I looked in the DPMRACurr.errlog and I'm seeing the following error message 
(same GUID) repeat itself going back several months.  Can I safely delete the 
specified directory to get rid of this message?  Is this issue related to my 
initial post?

2274	1588	03/08	12:00:09.684	37	mta.cpp(203)CMTA::Initialize => Could not 
delete file = [C:\Program Files\Microsoft Data Protection 
Manager\DPM\temp\MTA\{034D40CB-459D-4E95-8D35-FACC799684A8}]
2274	1588	03/08	12:00:09.684	37	mta.cpp(204)Failed: F: lVal : 0: 0000000000

"pk" wrote:

> I'm attempting to backup a MOSS 2007 farm with DPM 2007 SP1.  More often than 
> not it works great, but more often than I'd like it "succeeds" with the 
> following errors which leaves me unable to do item-level restores.
> 
> Affected area:	Sharepoint Farm\simcspdb\SharePoint_Config
> Occurred since:	3/4/2010 11:11:41 PM
> Description:	DPM failed to obtain catalog information as part of the backup 
> for SharePoint Farm Sharepoint Farm\simcspdb\SharePoint_Config on 
> simcspwf.sawdustmgmt.local. Your recovery point is valid, but you will be 
> unable to perform item-level recoveries using this recovery point. (ID 3103)
> Recommended action:	1) If you do not expect to be performing item-level 
> restores using this recovery point, then dismiss this alert; otherwise, take 
> the recommended actions in the subsequent steps.
> 2) If the operation failed for a short-term backup to disk, in the 
> Protection task area, select the data source and click Create recovery point 
> to restart the backup. 
> 3) If the operation failed for a short-term backup to tape, in the 
> Protection task area, select all the failed data sources that belong to the 
> same protection group, and click Create recovery point – tape. This will 
> ensure that the tape backups are located on the same tape. 
> 4) Dismiss this alert immediately after starting your backup.
> Resolution:	DPM automatically changes this alert's status to inactive 10 
> days after it is issued.To dismiss the alert, click below
> 
> 
> I've checked the WssCmdletsWrapperCurr.errlog and it give me the following 
> three lines each time this occurs (the specific identifiers change, of course)
> 
> 0B90	1528	03/04	05:10:08.623	38	WSSCatalogGeneratorIncremental.cs(798)			Couldn't 
> process change 
> 1;0;dd6a327e-cb15-435e-a802-791727099f3a;634032281955770000;3032149
> 0B90	1528	03/04	05:10:20.201	38	WSSCatalogGeneratorIncremental.cs(798)			Couldn't 
> process change 
> 1;0;dd6a327e-cb15-435e-a802-791727099f3a;634032456674770000;3033134
> 0B90	1528	03/04	05:10:20.248	38	WSSCatalogGeneratorIncremental.cs(798)			Couldn't 
> process change 
> 1;0;dd6a327e-cb15-435e-a802-791727099f3a;634032460189400000;3033138
> 
> How can I troubleshoot these errors?

This happened again last night.  :(  I can't deal with this much longer.

I looked in the MSDPM.errlog and found the following entries at the exact 
time the error messages showed up.

Does anyone have any ideas?

27A0	1A80	03/11	05:08:10.830	32	RecoverableObjectsList.cs(1097)			Didn't 
find a RO with UniqueId [fed72ba3-5a29-492b-8a36-476b2baad94e]
27A0	1A80	03/11	05:08:12.455	32	RecoverableObjectsList.cs(1097)			Didn't 
find a RO with UniqueId [2daba070-74f2-4c25-89b8-6611f5cd5a97]
27A0	1A80	03/11	05:08:12.471	32	RecoverableObjectsList.cs(1097)			Didn't 
find a RO with UniqueId [84e07e6a-4035-479f-a7a4-15d9cc0f20e8]
27A0	1A80	03/11	05:08:12.502	32	RecoverableObjectsList.cs(1097)			Didn't 
find a RO with UniqueId [da91cefd-0bbe-4c45-8180-981ccb30e252]
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			ApplicationException during SharePoint Catalog Load operation
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			Message 
= Unknown database error: Error trying to query ComponentName in 
tbl_RM_SharePointRecoverableObject 
SP='dbo.prc_PRM_GetSharePointRecoverableObjectbyId' Error=50003
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			StackTrace 
=    at 
Microsoft.Internal.EnterpriseStorage.Dls.DB.SqlRetryCommand.ValidateReturnValue(String errorTitle)
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			   
at 
Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.SharePointRecoverableObject.GetRecoverableObjectFromUniqueId(SqlContext 
sqlContext, Int32 datasourceSequenceNumber, String caption, String& 
componentName)
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			   
at 
Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.SharePointRecoverableObject.DeleteSharePointRecoverableObjectsIncremental(SqlContext 
sqlContext, Int32 datasetSequenceNumber, Int32 datasourceSequenceNumber, 
String caption)
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			   
at 
Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.DeleteSharePointRecoverableObjectIncremental(Int32 
datasourceSequenceNumber, Int32 datasetSequenceNumber, String caption)
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			   
at 
Microsoft.Internal.EnterpriseStorage.Dls.Prm.SPContentDatabaseCatalogParser.OnIncrementalRecoverableObjectFoundHandler(Object 
sender, IncrementalCatalogObject catalogObject)
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			   
at 
Microsoft.Internal.EnterpriseStorage.Dls.Prm.WssRecoverableObjectsParser.ParseIncrementalCatalogData()
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			   
at 
Microsoft.Internal.EnterpriseStorage.Dls.Prm.SPContentDatabaseCatalogParser.ParseIncrementalCatalogData()
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			   
at 
Microsoft.Internal.EnterpriseStorage.Dls.Prm.SPContentDatabaseCatalogParser.ParseCatalogData()
27A0	1A80	03/11	05:08:12.596	32	RecoverableObjectCatalogLoader.cs(400)			   
at 
Microsoft.Internal.EnterpriseStorage.Dls.Prm.SharePointCatalogDataLoader.CatalogLoadPendingAsync(Object msgContext)
27A0	1A80	03/11	05:08:12.861	32	FsmBlock.cs(118)		|TaskID=41E1354F-8B7E-44F6-A613-A7381978FEF0	Backup.OnSuccess.ROCatalogLoad 
: <-- Exited FSM block with FAILURE (errorCode = PrmROCatalogMissing)

"pk" wrote:

> I looked in the DPMRACurr.errlog and I'm seeing the following error message 
> (same GUID) repeat itself going back several months.  Can I safely delete the 
> specified directory to get rid of this message?  Is this issue related to my 
> initial post?
> 
> 2274	1588	03/08	12:00:09.684	37	mta.cpp(203)CMTA::Initialize => Could not 
> delete file = [C:\Program Files\Microsoft Data Protection 
> Manager\DPM\temp\MTA\{034D40CB-459D-4E95-8D35-FACC799684A8}]
> 2274	1588	03/08	12:00:09.684	37	mta.cpp(204)Failed: F: lVal : 0: 0000000000
> 
> "pk" wrote:
> 
> > I'm attempting to backup a MOSS 2007 farm with DPM 2007 SP1.  More often than 
> > not it works great, but more often than I'd like it "succeeds" with the 
> > following errors which leaves me unable to do item-level restores.
> > 
> > Affected area:	Sharepoint Farm\simcspdb\SharePoint_Config
> > Occurred since:	3/4/2010 11:11:41 PM
> > Description:	DPM failed to obtain catalog information as part of the backup 
> > for SharePoint Farm Sharepoint Farm\simcspdb\SharePoint_Config on 
> > simcspwf.sawdustmgmt.local. Your recovery point is valid, but you will be 
> > unable to perform item-level recoveries using this recovery point. (ID 3103)
> > Recommended action:	1) If you do not expect to be performing item-level 
> > restores using this recovery point, then dismiss this alert; otherwise, take 
> > the recommended actions in the subsequent steps.
> > 2) If the operation failed for a short-term backup to disk, in the 
> > Protection task area, select the data source and click Create recovery point 
> > to restart the backup. 
> > 3) If the operation failed for a short-term backup to tape, in the 
> > Protection task area, select all the failed data sources that belong to the 
> > same protection group, and click Create recovery point – tape. This will 
> > ensure that the tape backups are located on the same tape. 
> > 4) Dismiss this alert immediately after starting your backup.
> > Resolution:	DPM automatically changes this alert's status to inactive 10 
> > days after it is issued.To dismiss the alert, click below
> > 
> > 
> > I've checked the WssCmdletsWrapperCurr.errlog and it give me the following 
> > three lines each time this occurs (the specific identifiers change, of course)
> > 
> > 0B90	1528	03/04	05:10:08.623	38	WSSCatalogGeneratorIncremental.cs(798)			Couldn't 
> > process change 
> > 1;0;dd6a327e-cb15-435e-a802-791727099f3a;634032281955770000;3032149
> > 0B90	1528	03/04	05:10:20.201	38	WSSCatalogGeneratorIncremental.cs(798)			Couldn't 
> > process change 
> > 1;0;dd6a327e-cb15-435e-a802-791727099f3a;634032456674770000;3033134
> > 0B90	1528	03/04	05:10:20.248	38	WSSCatalogGeneratorIncremental.cs(798)			Couldn't 
> > process change 
> > 1;0;dd6a327e-cb15-435e-a802-791727099f3a;634032460189400000;3033138
> > 
> > How can I troubleshoot these errors?