Win Srv 2012 - DPM2012 + SP1 Beta, all agents upgraded and show status OK

System was formerly WinSrv 2008 + DPM 2010 and has been OK for months.

After upgrade all replicas are marked as inconsistent.  Running a consistency check fails with description

DPM failed to communicate with BackupSrv.domain.local because of a communication error with the protection agent (ID 53 Details: The service did not respond to the start or control request in a timely fashion (0x8007041D))

<BackupSrv is where the DPM server runs, does this mean DPM tries to talk to itself and fails?)

The event log has a pair of System Events.

ID 7009 - A timeout was reached (30000 milliseconds)  while waiting for the DPMRA service to connect

ID 10005 - DCOM got error "1053" attempting to start the service DPMRA with arguments "Unavailable" in order to run the server:

Any thoughts on how to get the replicas consistent?

{DA6AA17A-D61C-4E9C-8CEA-DB25DEA52A95}

I was having the same problem.

It tried to start the "C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\DPMRA.exe" manually and it said that VssRequestor.dll was missing.

I found the VssRequestor.dll file on a client with the DPM 2012 SP1 Beta agent installed ("C:\Program Files\Microsoft Data Protection Manager\DPM\bin\VssRequestor.dll") and copied it to the DPM server ("C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\VssRequestor.dll") and it worked. 

-Thomas I

• Proposed as answer by thiv80 Monday, November 05, 2012 2:47 PM
• Marked as answer by PaulLintonMicrosoft community contributor Monday, November 05, 2012 9:11 PM

Thank you.  On the server my folder was C:\Program Files\Microsoft DPM\DPM\bin", in case anyone else is looking

Should the people who put together the SP1 install kit be told about this as it seems to be an installation problem to me?  How?

You rock dude! This solution worked like a charm. Thanks Thomas. I just got my Friday night back :)

Absolutely, phenomenally, incredible that you found this!!!  I KNEW there was some type of problem that the server was not issuing the "correct" command or something since all other communication tests between servers was fine...

ping <protected server name>  <---succeed or fail
 net view \\<protected server name>  <---succeed or fail
 Sc \\<protected server name> query  <---succeed or fail
 Wmic /node:"<protected server name>" OS list brief   <---succeed or fail

I KNOW that when you start a sync or anything for that matter on the server if you go to the PS and open WSB in Server Manager you can watch the command at the DPM Server start the process on the PS and that just wasn't happening no matter my efforts........ drop firewalls, add computer/user accounts to DCOM groups, trusted computer groups, blah blah, blah ad naseum.   What ever got you heading down this road???  I am currently watching serveral servers getting their first synch since I updated to SP1 Beta all around!!!  You truly DO ROCK!! 

• Proposed as answer by thiv80 Monday, November 19, 2012 7:02 AM
• Unproposed as answer by thiv80 Monday, November 19, 2012 7:03 AM

The thing that tipped me of was a error event in the System event log.

Source: DistributedCOM Event ID: 10005

DCOM got error "1053" attempting to start the service DPMRA with arguments "Unavailable" in order to run the server:

{DA6AA17A-D61C-4E9C-8CEA-DB25DEA52A95}

After that I tried to start the DPMRA service manualy, with the same error. I had a look at the service itself, and what command it was using. Found the dpmra.exe, tried to run it, and there it said the VssRequestor.dll was missing.

Thank You thiv80

I upgraded System Center Data Protection Manager 2012 to System Center Data Protection Manager Service Pack 1 and had the same DCOM error after the upgrade, copying the VssRequestor.dll fixed the problem.

I had the same issue, no communication with the agent... and no consistent backup after upgrading to DPM 2012 SP1. Copied the VssRequestor.dll to the server, and the problem was fixed! Great !!! And thank you very much.

Andy

All,

I found that if I upgrade the DPM server (all W2012) from DPM RTM to DPM SP1 the agent upgrade push install works, but as above connot communcate with the same errors.

The fix was to manually uninstall (Control Panel, Programs and Features) each agent from each Host and VM, then uninstall in DPM, and push out the agents from DPM again.

I can only presume the VMM push "upgrade" of agents fails but new install works.

Cheers,

LM

• Edited by Lord Melch Wednesday, March 20, 2013 10:14 AM

Thank you, been bashing my head against a brick wall with this problem since we upgraded 3 days ago!

Worked for me also.  This obviously needs to be addressed by the DPM team.

Worked for me also.  This obviously needs to be addressed by the DPM team.

Let's hope so..

• Edited by Lord Melch Wednesday, May 01, 2013 9:17 PM

I had the same issue upgrading to DPM 2012 R2 on one DPM server.  Your recommendation fixed it.  Thanks!

Same problem after upgrading from 2012 SP1 to 2012 R2 on a domain controller (WS2012) with ADFS - but no other machines had issues so far.

I had to uninstall and reboot, then reinstall (using the installer DPMAgentInstaller_x64.exe). It worked after that.

Same here when upgrading to DPM 2012 R2. The recommended fix also worked for us. Thanks!