Merge replication problems - Subscriptions expiring prematurely

  • Environment:

    Publisher: SQL 2000 EE 8.00.2039 on Windows 2003 (32-bit)

    Subscribers: SQL 2000 EE 8.00.2040 or 8.00.2039 on Windows 2003 (both 32-bit and 64-bit subscribers)

    We have an 18 subscriber merge replication infrastructure. It ran pretty well for most of the last two years until early December. We applied Windows updates on a number of our subscribers in early November and our problems cropped up shortly afterwards. (Windows Updates on 11/07/2010 and 01/09/2011)

    Problem #1: (11/23/2010)

    Our merge subscriber indicated a problem inserting a row into the MSmerge_genhistory table - after this failure, the subscription was marked as "expired". This is a "pull" merge subscription with no prior history of these issues.

    Problem #2: (11/30/2010)

    Almost exactly a week later, our same subscription had the same behavior as described in problem #1.

    Problem #3: (01/09/2011)

    Nine of our merge replication subscriptions (all "pull") show up as "expired". I rebuilt them all as "push" instead. This was the day we installed Windows Updates. (the system from problems 1 & 2 was impacted - but on a different publication)

    Here is the list of Windows Updates and the date they were installed:

    11/07/2010:

    KB979687

    KB2416451

    KB2378111

    KB2345886

    KB2296011

    KB2279986

    KB2387149

    KB981957

    KB2360131

    KB2360937

    KB982132

    01/09/2011:

    KB2443105

    KB2423089

    KB2436673

    KB2296199

    KB2467659

    KB2416400

    KB2440591

    I am dying to know if this is just really bad luck or if any of the above patches might have played a role in my problems.

    Anyone have any ideas? I can get more background information if required.

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply