Support Tip: DPM System State Protection Fails with error ID: 30229

~ Dwayne Jackson | Senior Support Escalation Engineer

FIXHi Everyone, Dwayne Jackson here with a quick tip in case you ever run into an issue where System State Protection fails for System Center 2012 Data Protection Manager. Please ensure your symptoms align with the items noted below. 

Symptoms

The first symptom you’ll see from DPM server system state protection fails with below error:

clip_image002

<DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code:  0x12F6790). (ID 30229 Details: Internal error code: 0x80990ED0)>

Also, if you examine it from the protected server side, the Event ID 517 below is logged in Application log.

clip_image004

<The backup operation that started at '‎2015‎-‎04‎-‎22T11:46:14.594589400Z' has failed with following error code '0x80780102' (The system writer is not found in the backup.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.>

Additionally, from protected server, Windows Server backup displays than error similar to this:

clip_image006

clip_image008

You will also notice that if you go to the protected server and run the command vssadmin list writers from and administrative command prompt, you’ll see that System Writer is not displayed in the output.

Cause

If you encounter these symptoms, a possible cause is that Cryptographic Services on the problem server is not running.

Resolution

To remedy this, carry out the steps outlined below.

1) From the problem server, identify whether the Cryptographic Services service is running.

2) Assuming it is not running, attempt to start the service. If the service starts successfully then move on to step 3. If the service fails to start, review the Application Event Log for help identifying why the service failed to start.

clip_image010

3) From problem server, open an administrative command prompt (Run as Administrator) run the following command:

Vssadmin List Writer

The writer named System Writer should now be displayed.

image

4) From the DPM server, attempt to run the System State backup that previously failed. It should now succeed.

For additional information explaining DPM System State Protection, please see the following:

DPM and System State Backup Explained

Dwayne Jackson | Senior Support Escalation Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: http://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: http://blogs.technet.com/momteam/ 
Service Manager Team blog: http://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/

The Forefront Endpoint Protection 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/

DPM 2012 R2