FIX: Merge Agent Fails with "Setting Sentgen Too High" Error Message

Article translations Article translations
Article ID: 263955 - View products that this article applies to.
This article was previously published under Q263955
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57912 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

After you upgrade the Microsoft SQL Server merge publisher to service pack 2, and you run the snapshot process against the publication, if an existing merge subscriber is upgraded to service pack 2 from service pack 1, the merge agent marks the subscription for reinitialization and might fail with the following error message:
Setting sentgen too high.

CAUSE

This problem occurs because of optimization introduced in service pack 2, which ensures that the subscriber that processes the snapshot marks its sentgen or recgen values to make sure that the values are as high as the ones that were propagated in the snapshot. However, the optimization process does not account for existing subscriptions, which do not process a snapshot, and attempts to mark the sentgen or recgen values for these as well.

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.

Properties

Article ID: 263955 - Last Review: February 28, 2014 - Revision: 5.1
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 7.0 Service Pack 2
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbqfe KB263955

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com