SCCM SQL Based Replication InComingMessagesInQueue Backlog Issue ConfigMgr SQL Troubleshooting? My SCCM CB upgrade experience is explained in the following post “SCCM CB 1702 Upgrade of CAS and Primary Sites A Real-world Experience“. During the SCCM/ConfigMgr CB upgrade process, we noticed backlog of files in SQL DB.
It was found that there are millions of messages stuck in the transmission queue. In this post, I will share the experience of “SCCM SQL Based Replication InComingMessagesInQueue Backlog Issue”.
How to solve the InComingMessagesInQueue Backlog Issue?
SQL-based replication links between CAS and Primary servers went into the state called “Link Degraded“. We checked the RCM.log and RCMCTRL.log to check the replication links between SCCM CB CAS and Primary servers. We didn’t find anything specific in the log files.
I have a blog post that explains “SCCM SQL based Replication Monitoring and Troubleshooting”. More details SCCM ConfigMgr 2012 Site to Site replication and SQL Based Replication Guide. Following are the quick tips on SCCM CB SQL based replication troubleshooting:-
- SCCM Console Monitoring Status Gives an idea where to look
- SCCM Console Replication Link Checker
- Status Messages for RCM and Hman. Also, HMAN.log and RCM.log
- RcmCtrl.log is next place look for pre requisite errors of replication
- SQL Management Studio – spDiagDrs store procedure to check the backlog
- vLogs – BCP and SQL errors – to get more errors
Use spDiagDrs store procedure to Check the Backlog
We opened SQL Management Studio to run stored procedure “spDiagDrs” to check the status of the replication status between SCCM CB CAS and Primary servers. Even the site status shows as ACTIVE in spDiagDrs; the replication status was changing/flickering around Active to Link Degraded and back. We could also see that the processing of messages was very slow.
Resolution to InComingMessagesInQueue Backlog Issue
Microsoft recommended installing the KB4013098 patch on the SQL 2014 on all the SQL boxes in the hierarchy. We have tested this with the CAS server and one of the primary servers. The results were good, and the link status became stable after applying SQL 2014 CU KB4013098.
The cumulative update package 5 (build number: 12.0.5546.0) for Microsoft SQL Server 2014 Service Pack 2 (SP2). This update contains fixes that were released after the release of SQL Server 2014 SP2.
I would recommend installing this CU on all SQL servers on your SCCM CB hierarchy.
SCCM CB Backlog Fix – Cumulative Update 5 for SQL Server 2014 SP2 – Here