locked
Error: SQL Broker Service Broker on 1702 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am building a QA environment (stand-alone primary site) where I am doing a base install (no upgrade) of SCCM 1702 Current Branch on SQL 2016. I am not using the default instance, I have created another SQL instance. The install confirms that all the requirement are met and the actual install kicks off. 

    I get the error message below.

    

    I can reproduce it with SQL2012 as well in the same fashion so it's not 2016 related. Before anybody asks, yes the primary server and user account used for the install are both sysadmin on the database side. I would have shared the logs but this is production and don't have the permission to do so. Firewall is off on both SCCM and SQL. Also, the error message is misleading as this is the only ConfigMgr database on that instance, if that was the case the install would have never initialized and it would have flagged it before the install.

    I have opened a case with Microsoft and they're somewhat puzzled as well. Has anyone seen that issue before?

    Thanks.

    Wednesday, May 10, 2017 9:20 AM

All replies