Knowledge Base

FIX: Merge Replication with Alternate Synchronization Partners May Not Succeed After You Change the Retention Period

Article ID: 814460

Article Last Modified on 11/2/2007

APPLIES TO

Microsoft SQL Server 2000 Developer Edition
Microsoft SQL Server 2000 Standard Edition
Microsoft SQL Server 2000 Enterprise Edition
Microsoft SQL Server 2000 Personal Edition
Microsoft SQL Server 2000 Enterprise Edition
Microsoft SQL Server 2000 Workgroup Edition
Microsoft SQL Server 2000 Desktop Engine (Windows)
Microsoft SQL Server 2000 Developer Edition
Microsoft SQL Server 2000 Enterprise Edition 64-bit

SYMPTOMS

A merge replication environment with alternate synchronization partners may not succeed after you change the retention period on the primary publication or on the main publication. Immediately after you apply the change, subscriptions still can successfully synchronize with the main publication. But after you apply the failover steps to the alternate synchronization partners, the merge agent may not succeed, and you may receive the following error message:

Category:NULL
Source: Merge Process
Number: -2147200940
Message: The Publisher has been restored from a backup whose schema change version is different from the Subscriber. Rerun the Snapshot Agent and reinitialize the subscription.

After this, the alternate synchronization environment does not continue to work. You can still merge with the publisher that you synchronized with first after you changed the retention period, but all tries to synchronize with the other partners do not succeed. Even if you reinitialize the alternate synchronization partners and the subscribers, this action does not help.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

Hotfix information

This problem is fixed for SQL Server 2000 Service Pack 2 systems that are running version 8.00.0729.

The problem exists in SQL Server 2000 Service Pack 3, version 8.00.0760. To fix this version, you must apply SQL Server 2000 Service Pack 3 rollup, version 8.00.0765.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2000 Service Pack 2

Use this hotfix build for a server that is running SQL Server 2000 Service Pack 2.

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   17-Jan-2002  18:45  2000.80.568.0      29,244  Dbmslpcn.dll     
   17-Jan-2003  16:23                    786,432  Distmdl.ldf
   17-Jan-2003  16:23                  2,359,296  Distmdl.mdf
   11-Dec-2002  07:50                        180  Drop_repl_hotfix.sql
   02-Jul-2002  05:35  2000.80.650.0     107,088  Impprov.dll      
   17-Jan-2003  10:33                    774,409  Instdist.sql
   11-Dec-2002  07:50                      1,402  Inst_repl_hotfix.sql
   20-Aug-2002  06:24  2000.80.679.0     111,172  Logread.exe      
   15-Dec-2002  13:21  2000.80.717.0      90,692  Msgprox.dll      
   06-Apr-2002  16:08  2000.80.606.0      62,024  Odsole70.dll     
   02-Jan-2002  15:59                     18,185  Qfe356326.sql
   20-Aug-2002  06:47  2000.80.679.0     135,748  Qrdrsvc.exe      
   26-Aug-2002  12:49  2000.80.679.0     406,088  Rdistcom.dll     
   03-Oct-2001  15:36                    437,302  Replcom.sql
   20-Aug-2002  06:33  2000.80.679.0     152,136  Replmerg.exe     
   25-Nov-2002  11:43                  1,004,990  Replmerg.sql
   15-Dec-2002  13:21  2000.80.717.0     221,768  Replprov.dll     
   15-Dec-2002  13:21  2000.80.717.0     303,688  Replrec.dll      
   22-Jan-2003  09:27                  1,002,101  Replsys.sql
   03-Oct-2001  15:36                    881,228  Repltran.sql
   26-Aug-2002  12:49  2000.80.679.0     283,208  Rinitcom.dll     
   16-Sep-2002  12:31                    390,045  Securityhotfix.sql
   26-Aug-2002  12:49  2000.80.679.0      28,672  Sqlagent.dll     
   26-Aug-2002  08:39  2000.80.679.0     311,872  Sqlagent.exe     
   28-Aug-2002  06:32  2000.80.679.0      49,152  Sqlagent.rll
   26-Aug-2002  12:49  2000.80.679.0      53,824  Sqlcmdss.dll     
   28-Aug-2002  06:40  2000.80.679.0      12,288  Sqlcmdss.rll
   14-Jan-2003  11:39  2000.80.725.0     172,600  Sqlmap70.dll     
   20-Jan-2003  19:06  2000.80.728.0   7,479,377  Sqlservr.exe     
   01-Nov-2002  08:56  2000.80.698.0      45,644  Sqlvdi.dll       
   17-Jan-2002  18:45  2000.80.568.0      29,244  Ssmslpcn.dll     
   19-Dec-2002  14:55  2000.80.719.0      82,492  Ssnetlib.dll     
   02-Jan-2003  10:12  2000.80.722.0      25,148  Ssnmpn70.dll     
   06-Apr-2002  16:08  2000.80.606.0      70,208  Xplog70.dll      
   06-Apr-2002  16:08  2000.80.606.0      53,828  Xpqueue.dll      
   06-Apr-2002  16:08  2000.80.606.0     156,228  Xprepl.dll       
   11-Jul-2002  15:00  2000.80.658.0     279,104  Xpstar.dll       
   16-Sep-2002  13:12  2000.80.686.0      98,872  Xpweb70.dll

SQL Server 2000 Service Pack 3

Use this hotfix build for a server that is running SQL Server 2000 Service Pack 3.

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   07-Feb-2003  19:44                    786,432  Distmdl.ldf
   07-Feb-2003  19:44                  2,359,296  Distmdl.mdf
   29-Jan-2003  15:55                        180  Drop_repl_hotfix.sql
   31-Jan-2003  14:32  2000.80.763.0   1,557,052  Dtsui.dll        
   29-Jan-2003  19:18                    746,470  Instdist.sql
   29-Jan-2003  15:55                      1,402  Inst_repl_hotfix.sql
   07-Feb-2003  20:40  2000.80.765.0      90,692  Msgprox.dll      
   07-Feb-2003  17:53                  1,065,895  Replmerg.sql
   07-Feb-2003  20:40  2000.80.765.0     221,768  Replprov.dll     
   07-Feb-2003  20:40  2000.80.765.0     307,784  Replrec.dll      
   29-Jan-2003  19:18                  1,084,318  Replsys.sql
   07-Feb-2003  20:40  2000.80.765.0     176,696  Sqlmap70.dll     
   07-Feb-2003  20:40  2000.80.765.0      57,920  Sqlrepss.dll     
   07-Feb-2003  20:41  2000.80.765.0   7,528,529  Sqlservr.exe     
   07-Feb-2003  20:40  2000.80.765.0      45,644  Sqlvdi.dll       
   07-Feb-2003  20:40  2000.80.765.0      82,492  Ssnetlib.dll

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

REFERENCES

This hotfix is also available in the MS03-031 security patch. For additional information about the MS03-031 security patch, click the following article number to view the article in the Microsoft Knowledge Base:

821277 MS03-031: Security patch for SQL Server 2000 Service Pack 3

For additional information about how to set up alternate synchronization partners, click the following article number to view the article in the Microsoft Knowledge Base:

321176 HOW TO: Set Up Alternate Synchronization Partner in SQL Server 2000 Merge Replication

Keywords: kbbug kbfix kbsqlserv2000presp3fix kbqfe kbsqlserv2000presp4fix kbsqlserv2000fix kbhotfixserver KB814460

Microsoft KB Archive/814460

Contents