Article ID: 276427
Article Last Modified on 3/14/2006
APPLIES TO
- Microsoft SQL Server 7.0 Standard Edition
This article was previously published under Q276427
BUG #: 58156 (SQLBUG_70)
SYMPTOMS
When using pull merge replication, the initial snapshot may fail to be applied to the subscriber due to the following errors:
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
MORE INFORMATION
This problem occurs under the following conditions:
- One main publisher/distributor server (ServerA) has a publication P1.
- One republisher/distributor server (ServerB), which has a pull merge subscription to P1 on ServerA, republishes P1.
- One subscriber (ServerC) has a pull merge subscription to the publication P1 on the republisher server (ServerB).
- On the main publisher server (ServerA), add publication P2.
- Publications P1 and P2 do not have overlapping articles.
- On the republisher server (ServerB), add a pull merge subscription to P2 on the main publisher server (ServerA), and then republish P2.
When the initial snapshot of publication P2 is applied from the republisher server (ServerB) to its subscriber (ServerC), the pull merge replication process fails with the errors shown in the "Symptoms" section.
Topology
ServerA <--------- ServerB <---------- ServerC
(publisher <========= (subscriber <====X===== (subscriber)
distributor) republisher
distributor)
<--: Pull merge replication to publication P1.
<==: Pull merge replication to publication P2.
X : The initialization step that fails with the errors above.
Additional query words: MSmerge_genhistory;nc3MSmerge_genhistory
Keywords: kbbug kbfix KB276427
