SCCM SQL Service Broker ConfigMgrRCMQueue is Getting Disabled Configuration Manager ConfigMgr

SCCM SQL Service Broker ConfigMgrRCMQueue is Getting Disabled Configuration Manager ConfigMgr. Recently, I’ve received a comment from Johan Pol on how to Check backlog of Inboxes in SCCM 2012.

The command was regarding an issue related to the Service broker queue “ConfigMgrRCMQueue”.

One old secondary server site entry is not removed from DB, and those old entries are causing issues with DB replication. Also, ConfigMgrRCMQueue is getting disabled again and again. 

SCCM SQL Service Broker ConfigMgrRCMQueue

The secondary site attached to SCCM / ConfigMgr 2012 hierarchy was removed/deleted, but the entries from the SCCM 2012 console were not getting removed. Other secondary server replication links are getting impacted. Always use recommended way “Preinst /delsite” to remove (secondary) sites from SCCM 2012 database.

The /DELSITE option does not uninstall the site on the computer specified by the ChildSiteCodeToRemove parameter. This option only removes the site information from the Configuration Manager site database. 

After searching, I found similar kinds of issues discussed in the TechNet forum thread here. So I thought of simulating the issue in a lab environment and providing more information.  ####Warning#### Do NOT perform this in production environment.

Directly editing SCCM 2012 DB is not supported by Microsoft. Contact CSS to perform this action for you. Following are a few steps you can perform to test and resolve the issue in your lab environments. 
1. How to validate the broker service is enabled and running select is_broker_enabled, * from sys.databases where name = ‘CM_PR1’ When is_broker_enabled = 1 then broker service is enabled. In this case, the Service broker is fine.

2. To validate the requests executed by the SQL server, select * from sys.dm_exec_requests Returns information about each request that is executing within SQL Server. Most of the status looks good.

3. List of transaction details created to validate data is being written to or received. When we still have the data of old secondary over here. That may cause problems to ConfigMgrRCMQueue.  select * from sys.transmission_queue  ConfigMgrRCM_SiteSE2 and ConfigMgrBGB_SiteSE2 are two conversations related to my old secondary site SE2.

4. ConfigMgrRCMQueue is getting disabled again, and again problem  The old site conversations we’ve seen in step 3 may create problems that may intern disable ConfigMgrRCMQueue….. How to get into ConfigMgrRCMQueue and enable the ConfigMgrRCMQueue : CM_PR1 -> Service Broker -> Queues ->ConfigMgrRCMQueue

5. How to remove the unwanted or orphan conversations listed in ConfigMgr DB Here, old secondary site SE2 entries (conversations) create problems. This conversation handle (conversations_handle) mentioned below is related to that secondary site. To remove the conversation, run the following command with conversation_handle ID. END CONVERSATION ‘conversation_handle’  END conversation ‘A84D7AE3-2E93-E311-ADF0-00155D80801B’END CONVERSATION ‘conversation handles’ More troubleshooting tips on SQL Service Broker here.

Resources

SCCM Related Posts Real World Experiences Of SCCM Admins (anoopcnair.com)

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…