none
Install protection agent failed. Error 324 RRS feed

  • Question

  • Hi

    So this is my problem.

    I have 2 Windows 2012R2 servers, where DPM2012R2 are installed on server2.

    They are both on the same domain and network. I have talked to the network team and there should not be anything that stops the DPMserver from talking to the agent on server 1.

    The errors i get are:

    Install protection agent on BRG-WI-HV01C01.felles.firma.no failed:

    Error 324: The agent operation failed because the DPM Agent Coordinator service on BRG-WI-HV01C01.felles.firma.no did not respond.

    Error details: Internal error code: 0x8099090E

    Recommended action: Do the following to troubleshoot this issue:

    1) Verify that BRG-WI-HV01C01.felles.firma.no is remotely accessible from the DPM server.

    2) If a firewall is enabled on BRG-WI-HV01C01.felles.firma.no, 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

    AND

    Agent operation failed. (ID: 370)

    The agent operation failed because the DPM Agent Coordinator service on BRG-WI-HV01C01.felles.firma.no did not respond. (ID: 324)

    I have done every test, firewall is of, the server is accessible, i have tried installing the agent manually and attaching it. Same errors.

    I have even tried removeing SCDPM and installing it again.

    Anyone have any idea what this could be?

    I tried installing the dpm agent from another server I have, and that worked fine. This DPM server is not on the same location or network, but they are in the same domain.

    Monday, January 20, 2014 1:19 PM

All replies

  • Hi,

    Please use the following blog to help troubleshoot - it's very comprehensive.

    http://blogs.technet.com/b/dpm/archive/2012/02/06/data-protection-manager-agent-network-troubleshooting.aspx


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, January 20, 2014 11:44 PM
    Moderator
  • Thank you

    I have been through this blog, and the one thing that I can’t get to work are.

    The netstat –ano command

    The result I get is: TCP    0.0.0.0:5718           0.0.0.0:0              LISTENING       1040

    I don’t know if this is right? This is when I have started the DPMRA service on the DPM server. Otherwise this would not show up.

    I also tried to start the DPMRA service on the protected server and I get this error:

    Windows could not start the DPMRA on local computer.

    I tried to start a protection job on another server and when this is going on I see the Port 5718 is ESTABLISHED

    Tuesday, January 21, 2014 9:23 AM
  • Hi,

    <snip>
    I also tried to start the DPMRA service on the protected server and I get this error:

    Windows could not start the DPMRA on local computer.
    >snip<

    This problem needs to be fixed - the dpmra needs to be able to run either by manually starting it or by normal "on demand" request when a DPM job is initiated.


    If you look in the C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\dpmracurr.errlog and see if there are any clues why it cannot start.

    Manually delete any files or folders under the MTATempStore$ share on the DPM server. This is typically the c:\Program Files\Microsoft DPM\DPM\temp\MTA folder.

    DO NOTE DELETE the MTA folder itself.



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Tuesday, January 21, 2014 4:16 PM
    Moderator