Export (0) Print
Expand All

Troubleshoot Protection Agent installation issues

Updated: November 1, 2013

Applies To: System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - 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

 

Issue Possible Cause Resolution

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.

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 DPMAgentInstaller <DPMServerName>.

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 additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft