Troubleshooting the Database Replication Service in Microsoft Configuration Manager
This guide helps administrators diagnose and resolve Database Replication Service (DRS) problems in the following products:
- Microsoft System Center 2012 Configuration Manager (ConfigMgr 2012)
- Microsoft System Center 2012 R2 Configuration Manager (ConfigMgr 2012 R2)
- Microsoft System Center Configuration Manager current branch (1502, 1602, etc.)
Administrators charged with diagnosing and resolving Database Replication Service (DRS) problems.
Getting Started
When faced with a Database Replication Service (DRS) problem in Microsoft Configuration Manager, the beginning investigative phase is the most critical point. Any type of change or fix should be made only after careful study and understanding of the problem at hand.
You can find the latest Configuration Manager builds and updates here.
RLA runs within the context of whomever launches it from the console, so be sure that the account you use has administrative privileges on both SQL and site servers.
RLA will check the following on both sites:
- The SMS service is running
- SMS Replication Configuration Monitor component is running
- Ports required for SQL replication are enabled
- SQL version is supported
- Network is available between the two sites
- There’s enough space for the SQL database
- SQL Server Broker service configuration exists
- SQL Server Broker service certificate exists
- Known errors in SQL log files
- Whether the replication queues are disabled
- Time is in sync
- Is the transmission of data stuck?
- Does a Key Conflict exist?
Getting Started
When faced with a Database Replication Service (DRS) problem in Microsoft Configuration Manager, the beginning investigative phase is the most critical point. Any type of change or fix should be made only after careful study and understanding of the problem at hand.
You can find the latest Configuration Manager builds and updates here.
RLA runs within the context of whomever launches it from the console, so be sure that the account you use has administrative privileges on both SQL and site servers.
RLA will check the following on both sites:
- The SMS service is running
- SMS Replication Configuration Monitor component is running
- Ports required for SQL replication are enabled
- SQL version is supported
- Network is available between the two sites
- There’s enough space for the SQL database
- SQL Server Broker service configuration exists
- SQL Server Broker service certificate exists
- Known errors in SQL log files
- Whether the replication queues are disabled
- Time is in sync
- Is the transmission of data stuck?
- Does a Key Conflict exist?
Getting details with SPDiagDRS
Section 1
- SiteStatus: This tells us whether the site is replicating or not. Anything other than ACTIVE is not good.
- CertificateThumbprint: The thumbprint of the certificate used for authentication that contains the site’s public key (Local DB trusts remote DB).
Section 2
- IncomingMessageInQueue: This tells us the incoming backlog that a site has. If the backlog is high due to the number of sites reporting to it, you may see the links going to a degraded or failed state because the heartbeat synchronizations are not processed in time.
- OutgoingMessageInQueue: This tells us the backlog that has yet to clear as we wait for the sites to receive the messages. This generally fluctuates, however if it continues to grow then this can represent a problem. Further troubleshooting should be performed to determine which site is not getting the messages.
Section 3
Section 4
Section 5
Section 6
Section 7
Check RCMCtrl.log for errors
7/4/2016 1:25:36 PM: ReplicationLinkAnalysis Information: 1 : Completed replication link analysis thread.7/4/2016 1:25:37 PM: ReplicationLinkAnalysis Error: 1 : Unable to find SiteCode or SiteNumber7/4/2016 1:25:37 PM: ReplicationLinkAnalysis Error: 1 : Microsoft.ConfigurationManager.ManagedBase.LocalServerDataNotFoundException: Unable to find SiteCode or SiteNumber at Microsoft.ConfigurationManager.ManagedBase.SiteData.Refresh() at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.ReplicationLinkAnalysisEngine.Initialize() at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.ReplicationLinkAnalysisEngine.RunRulesInBackground(Object sender, DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
07/04/2016 12:33:34 PM 6352 (0x18D0)CSqlBCP::ReadRowCount: Can't open file [F:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\42EEDF0E-17CF-4713-AA65-C0E66B51AD62\INSTALLED_EXECUTABLE_DATA.bcp.rowcount]. SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) CSqlBCP::DRS_Init_BCPIN: ReadRowCount failed. SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0)*** DRS_Init_BCPIN() failed SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) CBulkInsert::DRS_Init_BCPIN : Failed to BCP in SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) BCP in result is 2147500037. SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) ERROR: Failed to BCP in for table INSTALLED_EXECUTABLE_DATA with error code 2147500037. SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) ERROR: Failed to apply BCP for all articles in publication Hardware_Inventory_7. SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) Will try to apply BCP files again on next run.
Check RCM.log for errors
7/4/2016 1:25:36 PM: ReplicationLinkAnalysis Information: 1 : Completed replication link analysis thread.7/4/2016 1:25:37 PM: ReplicationLinkAnalysis Error: 1 : Unable to find SiteCode or SiteNumber7/4/2016 1:25:37 PM: ReplicationLinkAnalysis Error: 1 : Microsoft.ConfigurationManager.ManagedBase.LocalServerDataNotFoundException: Unable to find SiteCode or SiteNumber at Microsoft.ConfigurationManager.ManagedBase.SiteData.Refresh() at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.ReplicationLinkAnalysisEngine.Initialize() at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.ReplicationLinkAnalysisEngine.RunRulesInBackground(Object sender, DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
07/04/2016 12:33:34 PM 6352 (0x18D0)CSqlBCP::ReadRowCount: Can't open file [F:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\42EEDF0E-17CF-4713-AA65-C0E66B51AD62\INSTALLED_EXECUTABLE_DATA.bcp.rowcount]. SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) CSqlBCP::DRS_Init_BCPIN: ReadRowCount failed. SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0)*** DRS_Init_BCPIN() failed SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) CBulkInsert::DRS_Init_BCPIN : Failed to BCP in SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) BCP in result is 2147500037. SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) ERROR: Failed to BCP in for table INSTALLED_EXECUTABLE_DATA with error code 2147500037. SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) ERROR: Failed to apply BCP for all articles in publication Hardware_Inventory_7. SMS_REPLICATION_CONFIGURATION_MONITOR 07/04/2016 12:33:34 PM 6352 (0x18D0) Will try to apply BCP files again on next run.
Check Despool.log for errors
Signature checked out OK for instruction coming from site P01, proceed with the instruction execution. SMS_DESPOOLER 04-07-2016 7.32.05 PM 2208 (0x08A0)Executing instruction of type MICROSOFT|SMS|MINIJOBINSTRUCTION|PACKAGE SMS_DESPOOLER 04-07-2016 7.32.05 PM 2208 (0x08A0)Received package P0100017 version 1. Compressed file – C:\SMSPKG\P0100001.PCK.1 as C:\Program Files\Microsoft Configuration Manager\inboxes\despoolr.box\receive\ds_s916k.pkg SMS_DESPOOLER 04-07-2016 7.32.05 PM 2208 (0x08A0)This package[P0100001]'s information hasn't arrived yet for this version [1]. Retry later … SMS_DESPOOLER 04-07-2016 7.32.06 PM 2208 (0x08A0)Despooler failed to execute the instruction, error code = 12 SMS_DESPOOLER 04-07-2016 7.32.06 PM 2208 (0x08A0)
- Create a blank text file name 'Secondary Site Data.pub'
- Copy the file to the RCM.box of the secondary site server
Check for BCP Problems
If increased, the setting takes effect in real time with no restart of anything required.
Congratulations
Congratulations! Your Database Replication Service problem has been resolved.
If you’d like more information about DRS, see the following:
- DRS Initialization In Configuration Manager 2012
- ConfigMgr 2012 Data Replication Service (DRS) Unleashed
- Planning for Communications in Configuration Manager
- ConfigMgr 2012 DRS – Troubleshooting FAQs
- ConfigMgr 2012 DRS Initialization Internals
- DRS Initialization In Configuration Manager 2012
You can also post a question in our Configuration Manager support forum.
Visit our blog for all the latest news, information and tech tips on Microsoft System Center Configuration Manager.
Additional Information
For additional information regarding the Database Replication Service, see the following:
- DRS Initialization In Configuration Manager 2012
- ConfigMgr 2012 Data Replication Service (DRS) Unleashed
- Planning for Communications in Configuration Manager
- ConfigMgr 2012 DRS – Troubleshooting FAQs
- ConfigMgr 2012 DRS Initialization Internals
- DRS Initialization In Configuration Manager 2012
You can also post a question in our Configuration Manager support forum.
Visit our blog for all the latest news, information and tech tips on Microsoft System Center Configuration Manager.