Chances are you have a named instance for your SCCM SQL install, which is definitely the way to go. However, when installing SCCM 2012 (R2) you are presented with the following error.
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
To resolve this is pretty pain-less.
In my scenario, I implemented the following two solutions:
- Enable Named Pipes for your SQL Server Network Configuration
- Delete all Dynamic (TCP/IP) Ports within the Protocols for your SQL Named Instance
First, to Enable Named Pipes, Launch SQL Server Configuration Manager, expand the SQL Server Network Configuration. Locate your named instance, right-click on TCP/IP and enable.
Second, within the same console view, double-click and open the TCP/IP properties.
- Here you need to delete any 0‘s (Zero’s) assigned to the TCP Dynamic Ports (Yes, remove for all IPv4, IPv6, IPAll, etc.).
- Also within the IPAll there will be a random port assigned here (TCP Dynamic Ports), go ahead and delete this too.
- Lastly, now you need to assign some port (ensure this port is open between your SCCM server and SCCM SQL server, if you are making use of the Windows or any Firewall(s)). In my case, I decided to assign port 1433. Within each interface, IPv4, IPv6, etc. apply your port here within the TCP Port. (See below)
Once you have implemented the two solutions above, now go ahead and restart the SQL Server (instance name) service.
Now proceed with your SCCM 2012 R2 Install.
If you want to learn more on Configuring SQL Server and TCP Port(s), please see the following Microsoft article, HERE.