Recently we have seen replication failure issue, the replication was failed for Multiple group ,
We tried to fix with Replication Link Analyzer, the replication Link Analyzer suggested to reinit and fix the  issue. Proceeded with suggested step and it started reinit for replication Group "Configuration Data".
The "Configuration Data" re initialization was stuck for for more than 4-5 hours with  status 2 on Primary and status 4 on CAS for the replication group "Configuration Data" and it was not moving.
We have tried with restart Sms_executive on CAS and Primary sites but it did not help. Also tried with fail over on primary site SQL Server.
Below is the query to track the reinitialization status of 'Configuration Data' on CAS and  PR1 site CM database.     
SELECT * FROM RCM_DrsInitializationTracking WHERE ReplicationGroup = 'Configuration Data' and SiteRequesting = 'PR1' order by CreatedTime desc
Found both the site was trying to finish the re initialization for replication group 'Configuration Data' with different replication Request Tracking GUID
On primary Site (PR1): The request tracking GUID ending with E4F with status 2 and the same id was Aborted on CAS site.
On Central Site (CAS) : The request tracking GUID ending with 73C with status 4 and the same id was Aborted on PR1 primary site.

Hear one site was sending the process and other was not accepting due the aborted ( the request tracking status 7).
Solution :
Aborted the stuck replication Request Tracking GUID on Central Site CAS and Primary Site PR1 CM database using the below query. ( Change the request tracking GUID in Below
UPDATE CM_DrsInitializationTracking SET InitializationStatus =7 WHERE RequestTrackingGUID = '<<Request Tracking GUID>>'
After ran the Above query on both the site new process for reinit RG "Configuration Data" started automatically , and reinit completed, site came to active .
If initialization did not start automatically , we can use below SQL command  for reinit it manually.
To initialize the replication group ,you can run the below SQL query on the Primary site or CAS site CM database.  
EXEC spDrsSendSubscriptionInvalid  '<ReceivingSiteCode/Subscriber>',   '<SendingSiteCode/Publisher>', '<ReplicationGroupName>'
Example:
The replication are failed for Configuration data from PR1 to CAS .
      EXEC spDrsSendSubscriptionInvalid  'PR1',  'CAS',  'Configuration Data'
The replication are failed for "Configuration data" from CAS to PR1 .
      EXEC spDrsSendSubscriptionInvalid  'CAS',  'PR1',  'Configuration Data'
Query to check Initialization status.
select InitializationPercent, InitializationStatus, TryCount,* from RCM_DrsInitializationTracking where InitializationStatus not in (6,7)order by CreatedTime desc;

Initialization Status:

• 1 --> Making request 

• 2 --> Sent BCP 

• 3 --> ACK from CAZ

• 4 --> BCP finished.

• 5 --> CAS prepared CAB file , After copy of CAB to primary state changes to  

• 6 - 6 is good 

• 7 - Previous attempt is aborted 

Happy Learning :)

Ram Pratap Yadav
Email: [email protected], [email protected]
Facebook https://www.facebook.com/Hiraniconfigmgr-120189361980772/
Follow us: https://www.linkedin.com/in/hiraniconfigmgr
Twitter: https://twitter.com/hiraniconfigmgr