SCCM Installation Failure: Unable to Connect to SQL Server

Tobias 40 Reputation points
2025-01-22T17:11:28.0466667+00:00

Attempting to install SCCM results in the following error message:

Setup is unable to connect to SQL Server with the connection information provided. Verify the following:

The SQL Server and instance names are entered correctly 
The specified SQL Server instance is not configured to use dynamic ports 
If a firewall is enabled on the SQL Server, inbound rules exist to allow connections to the correct ports 
The account used to run Setup has permissions to connect to the specified SQL Server instance

Are there any additional suggestions to troubleshoot this issue?

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
1,028 questions
0 comments No comments
{count} votes

Accepted answer
  1. XinGuo-MSFT 20,641 Reputation points
    2025-01-23T01:51:20.3833333+00:00

    Hi,

    I found a relevant case that might help you troubleshoot your SCCM installation issue. In this case, a user was unable to connect SCCM to the SQL Server database during a fresh install. Here are some key points from their experience

    SQL Server Configuration:

    • They ensured that TCP/IP was enabled for the SQL Server instance.
    • They set a static port for the SCCM instance, as dynamic ports were causing issues.

    Firewall and Network:

    • They verified that the firewall allowed connections on the necessary ports.
    • They tested the connection using SQL Server Management Studio (SSMS) from the SCCM server to ensure there were no network issues.

    Permissions:

    • They confirmed that the account running the SCCM setup had the necessary permissions to connect to the SQL Server instance.

    SQL Server Browser Service:

    • They made sure the SQL Server Browser service was running, which is essential for named instances. You can find more details and discussions on this case here

    I hope this helps! Let me know if you need further assistance or if there's anything specific, you'd like to explore.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.