Hi All<o:p></o:p>

We have done a restore of our CAS site recently (restored from the site maintenance task Backup
Site Server), everything is working ok again.<o:p></o:p>

We have 2 servers configured as SCCM WSUS SUP one connected to our CAS (Site WC1) and this one
updates from Microsoft , and one configured to use our CAS Software update
point as upstream server (and connected to our primary site (W20)<o:p></o:p>

But I have noticed in the monitoring pane => Software Update Point Synchronization
status that there is a difference in the catalog versions of both software
update points, the one connected to the CAS (Site WC1) is catalog version 4 and
the other one is catalog version 94 (site W20)<o:p></o:p>

I've checked both wsussync.log files but I don't see any errors <o:p></o:p>

I see in the logging that our upstream server connect to Microsoft en sync's everything
(Logging: Set content version of update source
{33870787-A4D7-426F-9F7C-53CA212888D6} for site WC1 to 4, Sending sync
notification to child site(s): W20) and in the logging of the other server I
see that this one successfully synced (Logging: Successfully synced site with
parent WC1, version 91)<o:p></o:p>

I think this wrong , but I don't see any error.<o:p></o:p>

Do we have an issue here or is this something which is really not a concern. <o:p></o:p>

Thx in advance<o:p></o:p>

Regards <o:p></o:p>

J<o:p></o:p>

Could it be similar to this?

http://myitforum.com/myitforumwp/2012/12/15/cm12-rtm-site-restore-tasks/

Hi John

Yes we had that problem and we fixed this with the steps provided in that article

Everything is working I also deployed some new updates to a few test clients with no problems 

there are no errors/warnings in both wsussync.log files

But the only thing is that the catalog versions are not the same , this is really strange

Maybe someone has experienced the same , or has an explanation for this?

Regards,

J

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.

We recently performed a site recovery on our CAS and noticed that the catalog version on the CAS was different from that of our Primary and Secondary sites.

What we learned, was the the transaction ID being sent from the CAS to the Primary, was of a lower transaction ID than what the Primary was sitting at. To clarify - the CAS was sending a sync notification of say Transaction ID 10. The Primary was expecting a transaction ID greater than 1000, and as such the Primary was deleting the sync request assuming that the transaction was 'old', when in fact it was the the latest.

Reviewing logs on the CAS (i cant recall at the moment the logs and the order to review, but i believe the logs were wsyncmgr, despool and sender) we can confirm the sync notification was successfully sent to the Primary server. 

Reviewing logs on the Primary ( again, i can't recall exactly the logs or the order to review but believe they were wsyncmgr, despool and replmgr) we saw that the sync notice was properly received, but in another log (replmgr), noticed that the transaction ID was less than what the primary was expecting and deleted the sync request.

To resolve the issue - we needed to stop services on the CAS ( i'll clarify the services in a later post) and make an adjustment to the transaction ID registry key on the CAS (again, i'll clarify the reg. key in a later post).

I hope this helps you and others.

Matt S.