Thursday, June 4, 2026
type here...
CM InfrastructureWSUS

After restore of primary site SUP not synchronizing on secondary site

By Haresh Hirani
0
912

Issue: After restore of primary site SUP not synchronizing on secondary site.

You will see this error on : replmgr.log

Replication file D:\CM2012\inboxes\replmgr.box\incoming\c8nhdyoq.RPT has an old transaction ID (Object Type = SMS_WSUS_SYNC_MANAGER, Object ID = P01.SYN, Transaction ID = 39), the current transaction ID is 710, delete it.

Solution:

Based on the design, if the registry value Transaction ID of sending site is smaller than the IDs stored in the destination sites .TRS file, destination sites replication manager will reject the replication filebecause it thought this file is an old file and can be ignored. Therefore, in this case, we need to increase the sites transaction IDs to fix this issue.

Point 1: On the sending site find the following registry hive:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_REPLICATION_MANAGER

Then in the right panel, find and write down the Transaction ID registry value.

Point 2: On the destination site open the SENDINGSITECODE.TRS file under the \inboxes\replmgr.box\history folder. You may find a lot of transaction IDs for many components. Please check if the Transaction ID registry value on sending site is smaller than any transaction IDs stored in the sendingsitecode.TRS file on the destination site.

If so, write down the largest Transaction IDs stored in the sendingsitecide.TRS file on destination site.

Point 3: Then go to site (sending site), change the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_REPLICATION_MANAGER | Transaction ID registry value to a number which is larger than the largest IDs stored in the sendingsitecode.TRS file on the destination site.

After Performing above steps Restart SUP AND SMS Service on the primary.

Note: Before performing make sure take backup or snapshot

Fore Reference Click Here

Happy Learning!!!

Thanks&regards,
Haresh Hirani
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

Author

  • Hi, I’m Haresh Hirani the mind behind Hiraniconfigmgr.com. I’m a seasoned IT professional with deep expertise in Microsoft technologies, especially in Configuration Manager (ConfigMgr/SCCM). Over the years, I’ve expanded my skill set to cover a broader range of modern device management platforms like Microsoft Intune, Jamf Pro, ManageEngine Endpoint Central, and VMware AirWatch (Workspace ONE UEM), I use this blog to document real-world, tested, working fixes and walkthroughs from my daily technical experiences. The 💡idea is simple: if it helped me, it might help someone like you. My goal is to create a living repository of practical IT solutions for the community. If you find something useful, or if you want to collaborate, feel free to connect with me on LinkedIn or drop a message through the Contact page. Happy to help.

Previous article
AWS Cloud Standalone WSUS Clients are not communicating with WSUS
Next article
SCCM 2012 monitoring Site Status Reporting Services Point Status Critical

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Search

Latest posts

I’m the person behind this webpage. Thank you for visiting the website and about me page! My website is all about Microsoft technologies. More about ConfigMgr and all other technologies which are interesting for me. However, larger percentage of my posts are related to SCCM. Normally, like to post the interesting issues which I came across in my day to day tech life. you will find only solutions which comes on my day to day life.

Hot Category

Popular Post

© COPYRIGHT Hiraniconfigmgr.com

Developed By : Deepcoder