The DPM protection agent service cannot start in System Center Data Protection Manager 2007

Article translations Article translations
Article ID: 947682 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

After you deploy the DPM protection agent in Microsoft System Center Data Protection Manager 2007, the DPM protection agent service cannot start on the protected servers. (A protected server is a server that contains data sources that are protection group members.)

Additionally, the following event is logged in the System log on the protected servers:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The DPMRA service terminated with service-specific error 10048 (0x2740).

CAUSE

This problem may occur for one of the following reasons:
  • Another process is using TCP port 5718 and TCP port 5719. These two ports are required by the DPM protection agent service.
  • TCP port 5718 and TCP port 5719 are not open for firewall applications or for firewall devices on the computer.

RESOLUTION

Resolution 1

To resolve this problem, find the process that is using the required TCP ports. To do this, follow these steps:
  1. Open a Command Prompt window. Run the following commands at the command prompt:
    netstat -ano > netstat.txt
    tasklist > tasklist.txt
    tasklist /svc >svclist.txt
    Note In this step, the command outputs of the netstat command and the tasklist command are written to text files so that you can check the outputs more easily. Run the tasklist command together with the /svc switch because the process that is using the required ports may be running as a service.
  2. Open the text files that were generated in step 1. To do this, run the following commands at the command prompt:
    notepad netstat.txt
    notepad tasklist.txt
    notepad svclist.txt
  3. In the Netstat.txt file, find any entries that correspond to TCP port 5718 and to TCP port 5719. Note the process identifier (PID) for each entry.
  4. In the Tasklist.txt file, locate the PIDs that you found in step 3 to determine which processes are using the required ports. If you do not find the PIDs in the Tasklist.txt file, try to find the PIDs in the Svclist.txt file.
  5. After you find out which process is using the required ports, configure the corresponding program to use other available ports. If you cannot change the program's ports, or if the program uses ports dynamically, you must stop the program.
Note If another application is using the port or ports (5718 and 5719), the ports cannot be changed. In this case, you can, instead, use the SetAgentcfg.exe tool. This tool provides the ability to change the default ports that the DPM agent uses.

To change the ports that are used by the DPM agent, follow these steps on the protected computer that is experiencing the problem. Make sure that the ports that you reassign will not used by any other applications.
  1. Locate the SetAgentcfg.exe file from the DPM server. By default, the file is located at the following path:
    %PROGRAMFILES%\Microsoft DPM\DPM\Setup\SetAgentCfg.exe
  2. Copy the file to the protected computer that is experiencing the problem. Copy the file to the agent DPM\Bin directory. By default, the file is located at the following path:
    %PROGRAMFILES%\Microsoft Data Protection Manager\DPM\bin
  3. On the protected computer that is experiencing the problem, open an administrative Command Prompt window.
  4. In the Command Prompt window, change to the directory to which the SetAgentCfg.exe file was copied. For example, change to the following directory:
    %PROGRAMFILES%\Microsoft Data Protection Manager\DPM\bin
  5. Run the following command to change the ports that are used by the DPM Agent:
    SetAgentCfg e dpmra <port number> <alternate port number>
  6. Restart the DPMRA service.
If these steps do not resolve this problem, determine whether the firewall applications require that you verify these ports. Then, manually open the ports.

Resolution 2

To reserve TCP ports 5718 and 5719, follow the steps that are documented in the following Microsoft Knowledge Base (KB) article:
812873 How to reserve a range of ephemeral ports on a computer that is running Windows Server 2003 or Windows 2000 Server

MORE INFORMATION

Data Protection Manager 2007 and protected servers open connections over TCP port 5718 and over TCP port 5719 to enable Data Protection Manager operations, such as synchronization and recovery. The current problem may occur on protected servers that are running the Microsoft Exchange System Attendant service. This service uses TCP ports dynamically. This service may take one or both of the required ports.

Data Protection Manager 2007 also uses the following ports:
  • TCP 135 dynamic
  • User Datagram Protocol (UDP) 53
  • UDP 88
  • TCP 88
  • UDP 137
  • UDP 138
  • TCP 139
  • TCP 389
  • UDP 389

Additional information

Properties

Article ID: 947682 - Last Review: July 23, 2009 - Revision: 2.1
APPLIES TO
  • Microsoft System Center Data Protection Manager 2007
Keywords: 
kbexpertiseinter kbtshoot kbprb KB947682

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com