Troubleshooting DPM 2007 Installation Issues

  • Article

Applies To: Data Protection Manager, System Center Data Protection Manager 2007

The following table provides guidance for troubleshooting issues that may occur when you are installing System Center Data Protection Manager (DPM) 2007.

DPM Installation Issues

Issue Possible Cause Resolution

Microsoft System Center Data Protection Manager 2007 is not supported on this operating system. Install Data Protection Manager on a computer running Windows Server 2003 Service Pack 2 or later.

Attempting to install DPM on a Domain controller.

DPM 2007 is designed to run on a dedicated, single-purpose server that cannot be either a domain controller or an application server.For more information, see DPM Server Operating System Prerequisites (https://go.microsoft.com/fwlink/?LinkId=102202)

A DPM installation interrupts non-DPM applications.

During DPM installation, Setup restarts the Windows Management Instrumentation (WMI) service. If you are running applications other than DPM and its prerequisite software on the DPM server, you may experience an interruption in the operation of those applications while the WMI service is restarted.

To prevent an interruption, shut down all other applications before you run DPM Setup.

The DPM installation fails.

An IIS installation failure occurs causing the DPM installation to fail.

Uninstall IIS using Add or Remove Windows Components, and then manually reinstall it. When the Windows Components Wizard prompts you for the IIS files, insert the Windows Server product CD.

To install IIS, note the following:

  • If you installed only the Windows Server 2003 operating system and then later updated to Service Pack 2 (SP2), you must provide the Windows Server 2003 CD.

  • If you slipstreamed Windows Server 2003 Service Pack 1 (SP1) with the operating system and then later updated to Windows Server 2003 SP2, you must provide the Windows Server SP1 slipstream CD.

  • If you slipstreamed Windows Server 2003 SP2 with the operating system, you must provide the Windows Server 2003 SP2 slipstream CD.

ID: 370. Agent operation failed.

The Quality of Service (QoS) Packet Scheduler may be missing or disabled on the DPM server.

To install or enable QoS Packet Scheduler, perform the following steps:

  1. On the DPM Server, open Network Connections.

  2. Click any connection, and then on the File menu, click Properties.

  3. Click Install, click Service, and then click Add.

  4. Click QoS Packet Scheduler, and then click OK.

    Note

    If QoS Packet Scheduler is not on the list, click Install and follow the prompts.

Information about functional differences

Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web (https://go.microsoft.com/fwlink/?LinkId=129347).

ID: 370. Agent operation failed.

When you install DPM 2007 on Windows Server 2008, the firewall exceptions for DPMRA.exe, MSDPM.exe, and port 135 are not added, which causes the agent refresh to time out.

This issue occurs on Windows Server 2008 because DPM only changes the private network profile. The exceptions that DPM creates in the network profiles will not work if one of the networks is configured as public.

To resolve this issue, perform the following steps to change all of your public networks to private:

  1. In Control Panel, open the Network and Sharing Center.

  2. On the Network and Sharing Center screen, for each public network, click Customize.

  3. In the Customize network settings dialog box, click Private, and then click Next.

  4. In the Successfully set network settings dialog box, click Close.

Error 810 or ID: 4315. The trust relationship between this workstation and the primary domain failed.

If the DPM server is unable to connect to the domain controller during installation, the DPM installation fails.

Verify that the DPM server can communicate with the domain controller. In addition, verify that the DNS entries are for the domain controller and that they are correctly configured.

Error 812. Configuration of reports failed.

This problem occurs when both SQL Server Reporting Services and Windows SharePoint Services are installed in the same Internet Information Services (IIS) application pool.

To resolve this issue, perform one of the following tasks:

  • Uninstall Windows SharePoint Services by using Add or Remove Programs, uninstall DPM, and then install DPM again.

-Or-

  • Configure a side-by-side installation of SQL Server Reporting Services and Windows SharePoint Services. For instructions, see Troubleshooting a Side-by-Side Installation of Reporting Services and Windows SharePoint Services (https://go.microsoft.com/fwlink/?LinkId=50877).

    Note

    The Rsactivate tool referred to in “Troubleshooting a Side-by-Side Installation of Reporting Services and Windows SharePoint Services” is located in the DPM installation path at Microsoft Data Protection Manager\Prerequisites\MSSQL\Reporting Services\ReportServer\RSReportServer.config.

Error 820. Setup cannot query the system configuration while performing the prerequisite check on Windows Server 2008 operating system.

This issue occurs if IIS has been installed without all of the components that DPM requires.

To resolve the issue, remove IIS, and then run DPM setup again.

DPM is unable to configure the Windows Server account because the password you entered does not meet the Group Policy requirements.

The custom password filter software is installed on the domain controllers.

Disable the custom password filter before you install DPM 2007.