Troubleshoot site data reinit

In a multi-site hierarchy, Configuration Manager uses SQL Server replication to transfer data between sites. For more information, see Database replication.

Use the following diagram to start troubleshooting SQL Server replication reinitialization (reinit) for site data in a Configuration Manager hierarchy:

Queries

This diagram uses the following queries:

Check if reinit isn't finished for site replication

SELECT * FROM RCM_DrsInitializationTracking dt
INNER JOIN ReplicationData rg
ON dt.ReplicationGroup = rg.ReplicationGroup
WHERE dt.InitializationStatus NOT IN (6,7)
AND rg.ReplicationPattern=N`Site'

Get the TrackingGuid & Status from the CAS

SELECT RequestTrackingGUID, InitializationStatus
FROM RCM_DrsInitializationTracking dt
INNER JOIN ReplicationData rg
ON dt.ReplicationGroup = rg.ReplicationGroup
WHERE dt.InitializationStatus NOT IN (6,7)
AND rg.ReplicationPattern=N'Site'

Get the TrackingGuid & Status from the primary site

SELECT RequestTrackingGUID, InitializationStatus
FROM RCM_DrsInitializationTracking dt
WHERE RequestTrackingGUID=@trackingGuid

Check primary site isn't in maintenance mode

SELECT * FROM ServerData
WHERE SiteStatus = 125
AND SiteCode=dbo.fnGetSiteCode()
AND ServerRole=N'Peer'

Check request status for the tracking ID

SELECT Status FROM RCM_InitPackageRequest
WHERE RequestTrackingGUID=@trackGuid

Next steps

• Reinit missing message
• Global data reinit