"Setup failed to configure sql service broker"  While Installing SCCM on Primary Site

Hi,

I am facing the following issue with SCCM 2012 Deployment.

I have one CAS , One SQL Server 2012, and One Primary site. I Installed SCCM on CAS with Default instance of SQL with Service broker port 4022 and TCP port 1433.

When i install SCCM Primary Site On Other Machine with same SQL Server and A new Named instance(which i created for primary site) am getting the error ""Setup failed to configure sql service broker"" Its showing that the service broker port is already using.

(Because CAS also using the same service broker port 4022).

This is happening while installing SCCM even after all the prerequisites check.

Can i use another port rather than 4022? or Do i need a separate SQL Server for primary Site? 

 

June 17th, 2015 9:35am

Honestly, that install makes no sense. If you only have a single primary site, then you don't need a CAS. *Ff* and *only if* you actually need a CAS, it should not share the same SQL instance (or even the same SQL host) as a primary site.
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 10:43am

Thank you. I am planning to add one more primary site in future. that is why i am using CAS. So i need to have separate SQL Hosts for each Primary Site and CAS. Right?
June 18th, 2015 12:46am

Then you have more than 150,000 managed Windows systems which means it really makes no sense whatsoever to share a host for the SQL instance because scalability is an issue.
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2015 8:26pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics