SCCM 2012 RC2 on separate instances on the same SQL Server

My SCCM 2012 RC2 environment consists of one CAS and one Primary site.
To make this work in a common SQL hotel with seperate instances you need to make shure that they don't communicate with the database on the same ports.

During the SCCM 2012 site installation you need to set:
On the CAS-Server "SSB Port" = 4022
On the P01-Server "SSB Port" = 4023

To configure this, go to the SQL Server:
Start SQL Server Configuration Manager
Go to SQL Server Network Configuration
Protocols for CAS-Instance - TCP/IP - Properties - IP Addresses - Set TCP Port = 1433 on all
Protocols for P01-Instance - TCP/IP - Properties - IP Addresses - Set TCP Port = 1434 on all



  1. Hello Henrik,

    I have similar SQL setup (except mine is clustered) but I receive ERROR: Failed to get SQL Server connection to CAS myclustername (instancename\CM_CAS).
    Here's the post link on myITForum:

    Please help.


    1. Hi Kris!

      Have you done all port configurstion above? No firewalls that stops them from communicating?
      Is this your first server that is installed in the hierachy? Are there already other SQL instances on that SQL cluster?

      Best regards

    2. Since Kris doesn't answer and I'm having the same issue, I'll answer your questions:

      The config steps above are followed (the SQL server instance on the cluster which should be used as SCCM 2012 site database is listening on port 1434, which has been confirmed by a telnet from the siteserver-to-be.
      Because I have no CAS, only a primary site, I leave the SSB port on 4022. The firewall has also been opened on this port.
      What can still be going wrong?

      Stephan van der Plas

    3. Have you set the "TCP Dynamic Ports" to 0 in SQL Server Configuration Manager?


    4. Well, yes, I tried. But after restarting the server, or the SQL service, the tcpDynamicPorts is set on a value somewhere in the 50000 range again. How can I make this behavior stop?

    5. I might have been wrong about the Dynamic ports, I now see that mine is set to Blank..

      Also make sure that you use the correct Cumulutive Updates.
      For the RTM these are:

  2. Henrik,

    I found the issue. It was a firewall issue, because (temporarily) setting to allow all incoming traffic on the SQL servers firewall solved it.

    THanks for your help.