DPM Support Tip: ID 41 Details: No connection could be made because the target machine actively refused it (0x8007274D) - The Official System Center Data Protection Manager Team Blog - Site Home - TechNet Blogs

DPM Support Tip: ID 41 Details: No connection could be made because the target machine actively refused it (0x8007274D)

DPM Support Tip: ID 41 Details: No connection could be made because the target machine actively refused it (0x8007274D)

  • Comments 1
  • Likes

GrayAndYellowGearsWhen trying to restore to a Recovery Database (RDB) you may get an agent timeout with the following error message:

ID 41 Details: No connection could be made because the target machine actively refused it (0x8007274D)

You may also see errors in the Exchange Application event log for VSS like this one:

Log Name: Application
Source: MSExchangeIS
Date:
Event ID: 9619
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User: N/A
Computer: <Server name>
Description:
Exchange VSS Writer failed with error code -543 when processing the post-restore event.

If any databases were restored, they are likely in a dirty-shutdown state.

Cause

Exchange is using ports 5718 and 5719 which are the same ports that DPM agent communication uses.

Resolution 1

To verify that Exchange is the process using the ports:

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.

Resolution 2

NOTE It depends on what version of the OS is running on the Exchange server exhibiting the behavior, however the goal is to ensure that ports 5718 and 5719 are not being used by Exchange.

For Windows Server 2000\2003:

The DPM protection agent service cannot start in System Center Data Protection Manager 2007 http://support.microsoft.com/default.aspx?scid=kb;EN-US;947682

How to reserve a range of ephemeral ports on a computer that is running Windows Server 2003 or Windows 2000 Server
http://support.microsoft.com/kb/812873

For Windows Server 2008 and 2008 R2:

You cannot exclude ports by using the ReservedPorts registry key in Windows Server 2008 or in Windows Server 2008 R2
http://support.microsoft.com/kb/2665809

More Information

You can use the command below to reserve these ports using the command line:

netsh int ipv4 Add excludedportrange protocol=tcp startport=5719 numberofports=2

Once those ports are freed up for DPM, the recovery should complete successfully.

Andy Nadarewistsch | Senior Support Escalation Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • I am getting this error for SQL DB protected servers. ID 41. I checked these ports are used by DPMRA only. But could be other issue?