SCCM 2012 SP1 Upgrade Fails - Setup Failed to configure SQL Service Broker

[bhscorp]

Setup:

SCCM 2012 on Windows Server 2008 R2

SCCM 2012 Database running in SQL Server 2012 on separate server

 

Had SCCM 2012 running well, OS deployments worked, but I received an error when attempting to Create an Application. Continously got an "SMS Provider Reported an Error " error. Found someone else who had the same issue, and they resolved it with the SP1 Upgrade.

 

Now when upgrading, I receive the error "Setup failed to configure SQL Service Broker". I have found some other posts about this, but not one that includes logs that look like below.

 

SQL Server is setup not to use Dynamic ports, the user account is a sysadmin (tho I don't have a user called SMSAdmin, there is one with the SCCM Server computer name with a dollar sign at the end which is a sysadmin though.

 

 

ConfigMgrSetup log:

 

INFO: Creating local group ConfigMgr_DViewAccess on BHSDEVSQL1.dev.bhs-corp.com for distributed view access. $$<Configuration Manager Setup><07-17-2013 05:51:23.070+420><thread=2500 (0x9C4)>

~Call NetLocalGroupAdd on server <\\BHSDEVSQL1.dev.bhs-corp.com> $$<Configuration Manager Setup><07-17-2013 05:51:23.102+420><thread=2500 (0x9C4)>

INFO: DRS components are installed and configured. $$<Configuration Manager Setup><07-17-2013 05:51:23.117+420><thread=2732 (0xAAC)>

INFO: 'BHSDEVSQL1.dev.bhs-corp.com' is a valid FQDN. $$<Configuration Manager Setup><07-17-2013 05:51:23.117+420><thread=2500 (0x9C4)>

INFO: SQL Connection succeeded. Connection: BHSDEVSQL1.DEV.BHS-CORP.COM SCCMSQL1\MASTER, Type: Secure $$<Configuration Manager Setup><07-17-2013 05:51:23.133+420><thread=2500 (0x9C4)>

INFO: Registered type SMS_ACCESS for BHSDEVSQL1.dev.bhs-corp.com sccmsql1\CM_BH2 $$<Configuration Manager Setup><07-17-2013 05:51:23.133+420><thread=2500 (0x9C4)>

INFO: SQL Connection succeeded. Connection: SMS_ACCESS, Type: Secure $$<Configuration Manager Setup><07-17-2013 05:51:23.133+420><thread=2500 (0x9C4)>

INFO: Registered type SMS_ACCESS for BHSDEVSQL1.dev.bhs-corp.com sccmsql1\CM_BH2 $$<Configuration Manager Setup><07-17-2013 05:51:23.148+420><thread=2500 (0x9C4)>

INFO: SQL Connection succeeded. Connection: SMS_ACCESS, Type: Secure $$<Configuration Manager Setup><07-17-2013 05:51:23.148+420><thread=2500 (0x9C4)>

INFO: Registered type SMS_ACCESS for BHSDEVSQL1.dev.bhs-corp.com sccmsql1\CM_BH2 $$<Configuration Manager Setup><07-17-2013 05:51:23.148+420><thread=2500 (0x9C4)>

INFO: SQL Connection succeeded. Connection: SMS_ACCESS, Type: Secure $$<Configuration Manager Setup><07-17-2013 05:51:23.148+420><thread=2500 (0x9C4)>

INFO: Replication security upgrade complete. $$<Configuration Manager Setup><07-17-2013 05:51:23.148+420><thread=2500 (0x9C4)>

INFO: Upgrading Service Broker configuration... $$<Configuration Manager Setup><07-17-2013 05:51:23.148+420><thread=2500 (0x9C4)>

INFO: Configuring SQL Server service broker... $$<Configuration Manager Setup><07-17-2013 05:51:23.148+420><thread=2500 (0x9C4)>

INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure $$<Configuration Manager Setup><07-17-2013 05:51:23.148+420><thread=2500 (0x9C4)>

*** IF (dbo.fnIsCasOrStandalonePrimary() = 1) EXEC dbo.spUpdateMasterTableSchema $$<Configuration Manager Setup><07-17-2013 05:51:24.539+420><thread=2500 (0x9C4)>

*** *** Unknown SQL Error! $$<Configuration Manager Setup><07-17-2013 05:51:24.539+420><thread=2500 (0x9C4)>

ERROR: SQL Server error: *** Unknown SQL Error! $$<Configuration Manager Setup><07-17-2013 05:51:24.539+420><thread=2500 (0x9C4)>

Failed to execute sql command IF (dbo.fnIsCasOrStandalonePrimary() = 1) EXEC dbo.spUpdateMasterTableSchema~ $$<Configuration Manager Setup><07-17-2013 05:51:24.539+420><thread=2500 (0x9C4)>

ERROR: Failed to update global table schema record. $$<Configuration Manager Setup><07-17-2013 05:51:24.539+420><thread=2500 (0x9C4)>

~~===================== Failed Configuration Manager 2012 Server Setup - Upgrade ===================== $$<Configuration Manager Setup><07-17-2013 05:51:24.539+420><thread=2500 (0x9C4)>

Any thoughts?

[bhscorp]

Okay so, I went into SQL Server Management Studio and tried running the SP in the log. It came up with a TypeInitializationException. Looks like this is a recent issue due to a KB update. Here is the Microsoft link, with workarounds (uninstall the KB).

 

http://connect.microsoft.com/VisualStudio/feedback/details/793500/sqlclr-typeinitializationexception-in-sqlconnection-since-kb2840628