Install DPM 2022 with remote SQL 2019 server failure

adam900331 50 Reputation points


I am deploying a DPM 2022 with remote SQL 2019. I followed this:

When I would like to connect to SQL server I got the following error: "DPM configuration failed. (ID: 4081)"

I enabled the TCP 1433 and UDP 1434 on SQL server.

If I disable the SQL firewall, the wizard can connect to SQL.

Which ports is required to connect the DPM install to SQL Server?


Microsoft System Center
Microsoft System Center
A suite of Microsoft systems management products that offer solutions for managing datacenter resources, private clouds, and client devices.
852 questions
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,877 questions
0 comments No comments
{count} votes

Accepted answer
  1. Simon Ren-MSFT 30,681 Reputation points Microsoft Vendor


    Thanks very much for your sharing. We're glad that the issue is gone now. It's appreciated that you could click "Accept Answer" to the helpful reply, this will help other users to search for useful information more quickly. Here's a short summary for the problem.


    DPM 2022 failed to connect to SQL server with the error: "DPM configuration failed. (ID: 4081)"


    Created an inbound firewall rule with dynamic RPC ports enabled. The connection is good.

    Thanks again for your time. Have a nice day!

    Best regards,


    If the response is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments No comments

6 additional answers

Sort by: Most helpful
  1. adam900331 50 Reputation points

    OK, I created an inbound firewall rule with dynamic RPC ports enabled. The connection is good.

    2 people found this answer helpful.
    0 comments No comments

  2. Bjoern Peters 8,856 Reputation points

    Hi Lovas,

    Welcome to Q&A Forum; this is a great place to get support, answers, and tips.

    Thank you for posting your query; I'll be more than glad to help you out.

    You said you'd followed the instructions... so why did you open TCP/1433 for the SQL Server? ;-)

    Set up firewall rules so that the DPM server can communicate with the SQL Server computer:

    • Ensure TCP/IP is enabled with default failure audit and enable password policy checking.
    • To allow TCP on port 80, configure an incoming exception for sqlservr.exe for the DPM instance of SQL Server. The report server listens for HTTP requests on port 80.
    • Enable RPC on the remote SQL Server.
    • The default instance of the database engine listens on TCP port 1443. This setting can be modified. To use the SQL Server Browser service to connect to instances that don't listen on the default 1433 port, you'll need UDP port 1434.
    • Named instance of SQL Server uses Dynamic ports by default. This setting can be modified.
    • You can see the current port number used by the database engine in the SQL Server error log. You can view the error logs by using SQL Server Management Studio and connecting to the named instance. You can view the current log under the Management - SQL Server Logs in the entry Server is listening on ['any' <ipv4> port_number].

    The instructions say... TCP/1443

    Maybe you check on this little detail ;-) Or change the port on your SQL Server instance to "whatever you want" or back to 1433...

    I hope my answer is helpful to you,


    Bjoern Peters

    If the reply was helpful, please upvote and/or accept it as an answer, as this helps others in the community with similar questions. Thanks!

    1 person found this answer helpful.

  3. Olaf Helper 41,101 Reputation points

    DPM is a SQL client as any other and utilize the same port as any other.

    Have you setup inbound as well as outbound; it's a bidirectional communication

    See Configure the Windows Firewall to allow SQL Server access

    1 person found this answer helpful.
    0 comments No comments

  4. adam900331 50 Reputation points

    Hy Peters.

    OMG, thanks, its too friday today. :)

    I modified to TCP/1443 and create UDP/1434, but the problem is same, I got the error message when the DPM server want to connect to SQL Server. Any idea?

    0 comments No comments