DPM 2022 error id 60

Question

We are running up to date DPM2022 to backup laptops, we are having issues with several systems in which the consistency check fails with error code: The protection agent on server name* was temporarily unable to respond because it was in an unexpected state. (ID 60 Details: Internal error code: 0x809909B0).

When I look up the code it suggest there is a locked file but when I check the systems there are no open files.

Answer 1

Hello,

This error has been documented by Microsoft and an official Resolution article has been published.

Please try the next steps:

1.Check recent records from the DPM protection agent (DPMRA) source in the Application event log on <ServerName> to discover why the agent failed to respond.

2.Examine the DPMRA log file for any details about the cause of the crash. The DPMRA log file will be in the format of DPMRA*.errlog (for example, DPMRACURR.ERRLOG) and by default is located in \Program Files\Microsoft Data Protection Manager\DPM\Temp.

3.Make sure that the DPM server is remotely accessible from <ServerName>. If a firewall is enabled on the DPM server, make sure that it's not blocking requests from <ServerName>. For complete details about the necessary ports and recommended firewall configuration, see Configure firewall settings for DPM

4.Restart the DPMRA on <ServerName>. If the service doesn't start, reinstall the protection agent.

Reference: https://learn.microsoft.com/en-us/troubleshoot/system-center/dpm/protection-agent-crashes

--If the reply is helpful, please Upvote and Accept as answer--

Answer 2

Firewalls are turned off this is effecting several machines but not all. I am having issues with reading the error logs. The application event log is error and warning free. The job starts off transfering data but then at a random point it errors out.

Answer 3

Same issue. Had the issue with DPM 2019 and I thought upgrading to 2022 will fix the issue, but no luck. Random file servers, especially remote servers. Everything was fine and all of the sudden this happened.

Answer 4

I wish I can contribute with an actual answer instead of just piling on, but I do think Microsoft needs to be made aware of this. For me it started happening around UR4 with DPM 2019 (and I'm thinking this may be reproducible on all versions of DPM 2022). While that update did fix a lot of things--particularly in the way it mounts replicas--it seems to throw a lot of the aforementioned error in John VanHoose's question.

I've seen cases where that error gets thrown every 15 minutes (or in many cases, at :15, :30, :45, and :00 on the dot no matter when the server/services were started), and in the Event Viewer, DPMRA.exe crashes at those intervals.

It seems to be correlated with backing up client computers (Windows 10, 11) with long file paths, but I can't verify this for sure.

I've removed and re-added client computers to our DPM servers and to different protection groups with various results.

For now we've given up backing up client computers since they're now using OneDrive and Known-Folder Move (KFM), but we do still run into occasions with the "unexpected state" error when backing up servers (regardless of whether it's at the guest file level, guest application level, guest Bare Metal (yes, Windows Server Backup is enabled on those protected servers), or host VHD), and we have to restart the DPM server exhibiting this behavior.

Answer 5

I hope MS support is reading these posts. The issue is getting worse, and I tried all suggestions, even from MS support but no luck. I hope they resolve the issue soon or we are abandoning DPM for good :-(