FIX: Merge Agent Fails with Error Message: "The publisher has been restored from a backup whose schema change version is different..." (319961)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q319961
BUG #: 356918 (SHILOH_BUGS)

SYMPTOMS

The Merge Agent fails with the following error message:
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.
					

CAUSE

You have two publications created on the same database. When both of the publications were created, the @enabled_for_internet parameter of the sp_addmergepublication stored procedure was set to TRUE to enable internet access.

After the snapshot job runs for both publications, and the corresponding merge jobs have both run, if you re-run the snapshot for one of the publications, the subsequent execution of the corresponding merge job may fail with the same error message.

RESOLUTION

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 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix should have the following file attributes or later:
   Date         Time          Size          File name
   -------------------------------------------------------

   03/18/2001   04:02:05 PM   3,584 bytes   Readme.txt
   03/18/2001   01:56:33 PM   9,751 bytes   Qfe356918.sql
				
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbSQLServ2000sp3fix kbbug kbfix kbSQLServ2000preSP3fix KB319961