Troubleshoot the DPM Protection Agent
Updated: October 30, 2017
Applies To: System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - Data Protection Manager, System Center 2016 - Data Protection Manager
The following table provides troubleshooting guidance that supplements the specific error messages that you may encounter during protection agent installation.
Before starting the troubleshooting process, we recommend that you first try to install the protection agents manually. For detailed instructions for installing the protection agents manually, see Installing Protection Agents Manually (http://go.microsoft.com/fwlink/?LinkID=179676).
Protection Agent Installation Issues
|Agent installation (or setdpmserver) fails with fatal error 0x80004005.||Check if Windows Management Instrumentation (WMI) is listed as a predefined exception in Windows Firewall.||Configure the Security Configuration Wizard (SCW) to enable Remote WMI. In SCW wizard, on the "Select administration and other options", enable Remote WMI. Apply the security policy and then start DPM agent installation again.|
|DPM protection agent will not install on a computer||Go through the check list||- Is the computer connected to the network and can it be remotely accessed from the DPM server?
Both the DPM server and the computer to be protected must be connected to the network during installation of a protection agent.
- Does the protected computer have a supported Windows operating system installed?
Verify the operating system on the computer to be protected.
- Is a firewall enabled on the computer to be protected that could be blocking requests from the DPM server?
If a firewall is enabled, you need to configure the firewall to allow communication between the DPM server and the computer to be protected. For information about configuring the firewall, see Configure firewall exceptions for the agent
- Is a firewall enabled on the DPM server?
If a firewall is enabled, you need to configure the firewall to allow installation of a protection agent on the computer.
- Has a previous version of the protection agent already been installed on the protected computer?
You cannot install two versions of the protected agent on the same protected computer.
- Is the Remote Registry service running on the computer to be protected?
The Remote Registry service must be running on both the DPM server and the computer before you can install a protection agent. In Administrative Tools, start the Remote Registry service and then install the protection agent.
- Is Remote Procedure Call (RPC) unavailable?
RPC must be available. See Microsoft Knowledge Base article 555839, Troubleshooting RPC Server is Unavailable in Windows.
- Is the boot volume on the computer formatted as file allocation table (FAT)?
Convert the boot volume to NTFS file system if you have sufficient space.
|DPM protection agent will not uninstall from a computer||Go through the check list||- Is the protected computer disconnected from the network?
To uninstall a protection agent, the protected computer must be connected to the network.
- Was the protected computer renamed or moved to another Active Directory domain after the protection agent was installed?
To uninstall a protection agent, the protected computer must have the same name and be in the same domain as it was when the protection agent was installed.
Uninstall the agent locally, and then remove the entry from DPM Administrator Console.
|DPM protection agent is incompatible with DPM or other software||Go through the check list||- Did you upgrade the DPM software without updating the protection agent?
To determine whether an agent update is available, check the Agents tab in the Management view.
- Did you upgrade a protection agent by using Microsoft Update before DPM received the corresponding server update?
Because Microsoft Update can occur automatically, ensure that the protection agent and DPM are compatible.
|An error occurred when the agent operation attempted to communicate with the DPM Agent Coordinator service on the specified computer||COM communications error||Verify COM permissions on the protected computer.|
|SetDPMServer fails with error code 0x80070534 and error message “No mapping between account names and security IDs was done.”||A DPM 2010 agent was installed on this computer earlier, but a SetDPMServer action was not performed.||1. Install the new protection agent.
2. Perform SetDPMServer on the old agent.
3. Uninstall the old protection agent.
4. Do an agent upgrade.
|Protection agent upgrade fails.||- If there is an entry for DPM Protection Agent in the installed programs list, try upgrading the agent by using DPMAgentInstaller.exe.
- If the previous step fails, uninstall the agent from Programs and Features and install it again by running
|System Error 1130:
Not enough server storage is available to process this command.
- OR -
Event ID 2011: Not enough memory to complete the transaction. Close some applications and retry.
|The configuration parameter "IRPStackSize" of the server is too small for the server to use a local device.||We recommend that you increase the value of this parameter. See KB 177078, Antivirus software may cause Event ID 2011 (http://go.microsoft.com/fwlink/?LinkId=73102).|
|The RPC server is unavailable.||A firewall is enabled on the remote computer.||If a firewall is enabled on the remote computer on which you are installing the protection agents, before installation you must run the DPMAgentInstaller.exe executable file. For more information, see Installing Protection Agents on Computers Behind a Firewall.|
|The Windows SharePoint Services farm back-end server does not appear as protected in DPM Administrator Console.||After you install a protection agent on a back-end server to protect a Windows SharePoint Services farm, the server does not appear as protected in the Management task area on the Agents tab.||No action is required. DPM protects the back-end servers internally if the Windows SharePoint Services farm has data on the server.|
|The protection agent installation fails if you are installing it on a non-primary domain controller running Windows Server 2003.||If the Primary Domain Controller (PDC) is running Windows Server 2000, the required Distributed COM Users group will be missing.||To resolve this issue, upgrade the forest root PDC emulator operations master role holder to Windows Server 2003, and then perform the protection agent installation again.
For more information, see KB 827016, "Local service and other well-known security principals do not appear on your Windows Server 2003 domain controller" (http://go.microsoft.com/fwlink/?LinkId=101729).
|The application has failed to start because the application configuration is incorrect.||The software requirements must be met on the protected computer.||Install the .NET Framework 3.5 with Service Pack 1 (SP1), and then try the protection agent installation again.
For DPM 2016, if you are protecting a server released prior to Windows Server 2012, you must install the appropriate version of WMF before installing the DPM agent:
- WMF 3.0 for Windows Server 2008 SP2
- WMF 4.0 for Windows 7, Windows Embedded Standard 7 and Windows Server 2008 R2
|Backup of data sources fail with agent upgrade error.||The protection agent on some members of the cluster has not been upgraded.||Upgrade the protection agent on all members of the cluster.|
|Error ID: 31008 appears because DPM only refreshes protection agents every 30 minutes.||If a protected domain controller or secondary server becomes unavailable, the protection agents are not automatically refreshed in DPM Administration Console.||For disaster recovery scenarios, in DPM Administrator Console you must wait for the scheduled installation list refresh, which is a maximum of 30 minutes.
To manually refresh the protection agents, in the Management task area, click the Agents tab, select the computer, and then in the Actions pane, click Refresh information.
|DPM Agent install fails with Error 347: An error occurred when the agent operation attempted to create the DPM Agent Coordinator service||This issue typically occurs because a prerequisite is not installed. Most frequently, Windows Management Framework (WMF) needs to be updated.||See KB 4018028|