Error 300: The agent operation failed because it could not communicate with the specified server.

• Incorrect firewall configuration requirements on the DPM server.
  
  
• The Remote Procedure Call (RPC) server is unavailable.
  
  

To resolve this issue, do the following:

• For firewall configuration requirements in the DPM Operations Guide, see Managing DPM Servers (http://go.microsoft.com/fwlink/?LinkId=91853).
  
  
• For an unavailable RPC server, see Microsoft Knowledge Base article 224370, "Troubleshooting RPC Server is Unavailable in Windows" (http://go.microsoft.com/fwlink/?LinkId=45817).
  
  

Error 303: Agent operation with specified server failed.

• Another installation is running on the specified server.
  
  
• The boot volume on the server is formatted as file allocation table (FAT).
  
  

• Wait for the installation to complete, and then retry the operation.
  
  
• Convert the boot volume to NTFS file system if you have sufficient space.
  
  For more information about using the Convert command for converting FAT volumes to NTFS, see Microsoft TechNet article Convert (http://go.microsoft.com/fwlink/?LinkId=50882).
  
  Review Microsoft Knowledge Base article 156560, "Free Space Required to Convert FAT to NTFS" (http://go.microsoft.com/fwlink/?LinkId=50883).
  
  
• If neither of these actions resolves the problem, restart the specified server and then retry the operation.
  
  

Error 306: Agent installation failed because the specified server already has a different version of the protection agent installed.

This issue occurs when the protection agent has already been installed on a server, but the DPM database does not have a record of the protection agent being installed.

Perform the following steps to reinstall the protection agent.

1. Locally uninstall the protection agent from the server.
   
   
2. On the DPM server, in DPM Administrator Console, in the Management task area, on the Agents tab, select the server. In the Actions section, click Refresh information.
   
   The agent status will change to Error.
   
   
3. In the Details section, click Remove the record of the server from this DPM computer.
   
   
4. Reinstall the protection agent on the server.
   
   

Error 308:

The agent operation failed because of a communication error with the DPM Protection Agent service on the specified server.

• Incorrect firewall configuration requirements on the DPM server.
  
  
• Internet Protocol Security (IPsec) configuration.
  
  
• The RPC server is unavailable.
  
  

• For firewall configuration requirements, in the DPM Operations Guide, see Managing DPM Servers (http://go.microsoft.com/fwlink/?LinkId=91853).
  
  
• IPsec may be configured to block particular IP traffic, such as on a particular port or to particular addresses. For assistance in troubleshooting IPsec, see IPsec Troubleshooting (http://go.microsoft.com/fwlink/?LinkId=50885).
  
  
• See Microsoft Knowledge Base article 224370, "Troubleshooting RPC Server is Unavailable in Windows" (http://go.microsoft.com/fwlink/?linkid=45817).
  
  

Error 316: The agent operation failed because the DPM Protection Agent service on the specified server did not respond.

Incorrect firewall configuration requirements on the DPM server.

For firewall configuration requirements, in the Deployment Guide, see Installing Protection Agents behind a Firewall (http://go.microsoft.com/fwlink/?LinkId=101313).

Error 319: The agent operation failed because of a communication error with the DPM Agent Coordinator service on the specified server.

Incorrect firewall configuration requirements on the DPM server.

For firewall configuration requirements, in the DPM Operations Guide, see Managing DPM Servers (http://go.microsoft.com/fwlink/?LinkId=91853).

Error 324: The agent operation failed because the DPM Agent Coordinator service on the specified server did not respond.

Incorrect firewall configuration requirements on the DPM server.

For firewall configuration requirements, in the DPM Operations Guide, see Managing DPM Servers (http://go.microsoft.com/fwlink/?LinkId=91853).

Error 341:

Agent operation failed because the credentials provided have insufficient privileges on the specified server.

• The account used does not have sufficient privileges on the server.
  
  
• The system times of the DPM server, the server on which you are installing the agent, and the domain controller are not synchronized, and therefore the Kerberos authentication fails.
  
  
• The DNS setting on the DPM server or the computer on which you are installing the protection agent is not correct.
  
  

• Retry the operation with an account that has administrator privileges on the specified server.
  
  
• Verify that system times on the DPM server and the server on which you are installing the agent are synchronized with the system time on the domain controller.
  
  
• Verify that the DNS settings are correct.
  
  

Error 342:

The agent operation failed because the DPM server could not communicate with the specified server.

Incorrect firewall configuration requirements on the DPM server.

For more information about firewall configuration requirements, see Managing DPM Servers (http://go.microsoft.com/fwlink/?LinkId=91853) in the DPM Operations Guide.

Error 347:

An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on <server name>.

The production server requires a restart to install the protection agent.

Restart the production server, and then manually install the protection agents. For more information about manually installing protection agents, see Installing Protection Agents Manually.

Error 348:

An error occurred when the agent operation attempted to communicate with the DPM Agent Coordinator service on the specified server.

Incorrect security settings for the COM object on the computer.

Verify COM permissions on the server.

Verify that the DCOM configuration settings are set as follows:

COM Security Default Access Permissions

• Local Access and Remote Access permitted to Self
  
  
• Local Access permitted to System
  
  

COM Security Machine Access Restriction (Security Limits)

• Local and Remote Access permitted to NT AUTHORITY\ANONYMOUS LOGON
  
  
• Local and Remote Access permitted to BUILTIN\Distributed COM Users
  
  
• Local and Remote Access permitted to \Everyone
  
  

COM Security Default Launch Permissions

• Launch permitted to NT AUTHORITY\SYSTEM
  
  
• Launch permitted to NT AUTHORITY\INTERACTIVE
  
  
• Launch permitted to BUILTIN\Administrators
  
  

COM Security Machine Launch Restriction (Security Limits)

• Local Launch and Activate permitted to \Everyone
  
  
• Local and Remote Launch, Local and Remote Activate permitted to BUILTIN\Administrators
  
  

Local and Remote Launch, Local and Remote Activate permitted to BUILTIN\Distributed COM Users

Error 271:

The user does not have administrator access.

- Or -

Error 377:

The agent operation failed because the minimum requirements in the DCOM configuration were not met.

The DCOM configuration settings did not meet the minimum requirements.

Verify that DCOM is enabled. If DCOM is enabled, verify that the DCOM configuration settings are set as follows:

COM Security Default Access Permissions

• Local Access and Remote Access permitted to Self
  
  
• Local Access permitted to System
  
  

COM Security Machine Access Restriction (Security Limits)

• Local and Remote Access permitted to NT AUTHORITY\ANONYMOUS LOGON
  
  
• Local and Remote Access permitted to BUILTIN\Distributed COM Users
  
  
• Local and Remote Access permitted to \Everyone
  
  

COM Security Default Launch Permissions

• Launch permitted to NT AUTHORITY\SYSTEM
  
  
• Launch permitted to NT AUTHORITY\INTERACTIVE
  
  
• Launch permitted to BUILTIN\Administrators
  
  

COM Security Machine Launch Restriction (Security Limits)

• Local Launch and Activate permitted to \Everyone
  
  
• Local and Remote Launch, Local and Remote Activate permitted to BUILTIN\Administrators
  
  
• Local and Remote Launch, Local and Remote Activate permitted to BUILTIN\Distributed COM Users
  
  

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 Microsoft Knowledge Base article 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 DPM 2007 Behind a Firewall (http://go.microsoft.com/fwlink/?LinkId=101313).

The agent operation failed while creating the local group DPMRADCOMTrustedMachines.

The protection agent installation fails when installing on two domain controllers that are in parallel replication.

The protection agent installations cannot occur simultaneously on the domain controllers that are in parallel replication mode. Wait for the replication to occur between the domain controllers before you install the protection agent on the second domain controller. You can also force the replication by doing the following:

From the command prompt, type repadmin /syncall.

The repadmin is a utility that you install with the Windows Server 2003 support tools.

Note
Two or more domain controllers in parallel replication mode must be protected by the same DPM server.

The Windows SharePoint Services farm backend server does not appear as protected in DPM Administrator Console.

After you install a protection agent on a backend 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 backend 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 Knowledge Base article 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).