Unable to Install Agent on Direct Access Machines. RRS feed

  • Question

  • New DPM 2019 install.  Got all agents and protection groups setup with the exception of my Direct Access (DA) clients.  The DPM machine can ping and even browse to those machines (explorer).  However when I attempt to install the agent I get this error:

    The system detected an invalid pointer address in attempting to use a pointer argument in a call (0x8007271E)

    My DA system uses the isatap Tunnel adapter so I assume this is some sort of mismatch confusion about seeing both IPv6 and IPv4?

    Any ideas on how to get around this issue?

    Friday, April 5, 2019 9:45 PM

All replies

  • Hi,

    Are you installing the DPM agent from the DPM console?

    DPM can back up client computers that are physically or wirelessly connected to the local area network (LAN) or back up over VPN. 

    Note that for VPN backup the ICMP should be enabled on the client computer.

    I would suggest you install the DPM agent manually, you can follow the procedure below:

    1. Copy the DPMAgentInstaller_x64 from the DPM server 
    (Default location: C:\Program Files\Microsoft System Center\DPM\DPM\ProtectionAgents\RA\\amd64)

    2. Open a Command Prompt (Admin) on the server/client where you want to install the DPM agent.

    3. Change directory to the location where you copied the DPMAgentInstaller_x64.

    4. Run the following command to install the DPM agent:

    DpmAgentInstaller_x64.exe <DPMServerName>
    (where <DPMServerName> is the fully qualified domain name (FQDN) of the DPM server)

    5. Once the agent has been installed, run the following command:

    SetDpmServer.exe -dpmServerName <DPMServerName>
    (where <DPMServerName> is the fully qualified domain name (FQDN) of the DPM server)

    Best regards,

    Blog: LinkedIn:

    Saturday, April 6, 2019 10:44 AM
  • Yes, from the console.  Manually installing it on over 30 machines doesn't sound like much fun.  Was hoping there was a way to fix DPM.  I guess the sooner I get started the sooner it'll get done.
    Monday, April 8, 2019 3:53 PM
  • It could be a firewall issue, can you verify that the clients can ping the DPM (FQDN) via the IPv4 address? And that both Forward DNS & Reverse DNS are resolving?

    With PowerShell remoting you could install the agents pretty quickly even manually.

    Blog: LinkedIn:

    Monday, April 8, 2019 4:12 PM
  • Yes, they can ping the DPM machine just fine.  The exact error message I'm getting isn't specific to DPM.  It's the same error you'll get with any network stack attempting to connect to an end point via IPv6 then ultimately getting an IPv4 address.  It's simply DPM not handing Direct Access via the tunnel properly.  If my DA was full blown IPv6 then this wouldn't be happening.

    WSUS had the exact same problem until MS fixed it.

    Monday, April 8, 2019 4:16 PM
  • I believe DPM will work in a pure IPv6 environment; however, if DPM has both IPv4 and IPv6 we expect the Protected Server to have IPv4 enabled, as the IPv4 channel is preferred.

    In this case the manual method might be the only working way for now.

    Blog: LinkedIn:

    • Edited by Leon Laude Monday, April 8, 2019 4:33 PM
    Monday, April 8, 2019 4:31 PM
  • Hello,

    Just wanted to check if you have any update on your issue?

    Blog: LinkedIn:

    Friday, April 12, 2019 2:32 PM
  • No update to give.  No fix for DPM has been presented.  Looks like manual install for DA clients on a tunnel.  But that's not a fix.  DPM is borked in this regard.
    Friday, April 12, 2019 3:38 PM
  • You could create a PowerShell script and run it on multiple servers/clients, this way it would be a bit more painless to install many agents.

    Blog: LinkedIn:

    Friday, April 12, 2019 3:45 PM
  • It's on the ToDo list.  Thanks.

    Problem with that though is all these clients are never on at the same time.  So that's very frustrating.  Also, updates from the console don't work either (naturally).  So again, big mess that will always take a long time to get sorted out even if scripted.

    Friday, April 12, 2019 4:04 PM
  • I understand, there's no easy way to go here I'm afraid.

    Are you using DPM mainly to backup clients (non-servers)?

    Because DPM is more designed for server backup, hence the limitations.

    Blog: LinkedIn:

    Friday, April 12, 2019 4:08 PM
  • Clients, Servers, VMs....lots of things.  DPM specifically functions with "Disconnected Clients" so MS needs to fix it.
    Friday, April 12, 2019 5:03 PM