Answered by:
The agent operation failed because the DPM Agent Coordinator service on machine.contoso.com did not respond. (ID 324 Details: Internal error code: 0x8099090E)

Question
-
DPM 2016 with the latest rollup Protected servers (PS) with Windows 2016 PS is located on a different network but a part of the domain When trying to install the DPM agent I get the below error. The machine is accessible from the DPM server Firewall is enabled but exceptions are set - WMI is running and have exceptions set Manual installation of the agent fails with that its not finding the DPM server Error in DPM: Affected area: machine.contoso.com Occurred since: 2019-03-27 09:51:34 Description: Agent operation failed. (ID 370) The agent operation failed because the DPM Agent Coordinator service on machine.contoso.com did not respond. (ID 324 Details: Internal error code: 0x8099090E) More information Recommended action: Do the following to troubleshoot this issue: 1) Verify that machine.contoso.com is remotely accessible from the DPM server. 2) If a firewall is enabled on machine.contoso.com, make sure that it is not blocking requests from the DPM server and has an exception for Windows Management Instrumentation(WMI). 3) Try installing the agent manually by selecting "Attach Agents" in the agent installation wizard. To troubleshoot this problem, refer to http://go.microsoft.com/fwlink/?LinkId=157614 To install an agent manually, run DpmAgentInstaller.exe <DPMServerName> on target server. For more information, see http://go.microsoft.com/fwlink/?LinkID=185786 Resolution: DPM automatically changes this alert's status to inactive 3 days after it is issued.To dismiss the alert, click below Inactivate
Error on PS
A DPM agent failed to communicate with the DPM service on DPMServer.contoso.com because the host is unreachable. Make sure that DPMserver.contoso.com is online and remotely accessible from the computer running the DPM agent. If a firewall is enabled on DPMServer.contoso.com , make sure that it is not blocking requests from the computer running the DPM agent (Error code: 0xa58ad070, full name: DPMServer.contoso.com).
- Edited by Micke68 Wednesday, March 27, 2019 10:01 AM
Wednesday, March 27, 2019 9:57 AM
Answers
-
Hi,
This issue can occur if your DCOM channel is not working properly or your firewall exceptions are not added correctly at the protected server side.
Check the following:1. Can you ping the DPM Server from the protected server?
2. Did you try installing the DPM agent manually? If yes, then configure firewall in your protected server.
For firewall configuration requirements, see Deploy the DPM protection agent:
https://docs.microsoft.com/en-us/system-center/dpm/deploy-dpm-protection-agent?view=sc-dpm-2016Best regards,
LeonBlog:
https://thesystemcenterblog.com LinkedIn:
- Marked as answer by Micke68 Friday, March 29, 2019 6:21 AM
Wednesday, March 27, 2019 10:08 AM
All replies
-
Hi,
This issue can occur if your DCOM channel is not working properly or your firewall exceptions are not added correctly at the protected server side.
Check the following:1. Can you ping the DPM Server from the protected server?
2. Did you try installing the DPM agent manually? If yes, then configure firewall in your protected server.
For firewall configuration requirements, see Deploy the DPM protection agent:
https://docs.microsoft.com/en-us/system-center/dpm/deploy-dpm-protection-agent?view=sc-dpm-2016Best regards,
LeonBlog:
https://thesystemcenterblog.com LinkedIn:
- Marked as answer by Micke68 Friday, March 29, 2019 6:21 AM
Wednesday, March 27, 2019 10:08 AM -
Thank you Leon.
Found out that RPC was blocked one way (from PS to DPM) in our application firewall.//Micke
Friday, March 29, 2019 6:21 AM