Discussion Locked

SQL Server-Sync Partner-sentgen too high

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

(SQL Server 2000/Windows 2000 Server)
I have followed the steps specified by Microsoft for setting up an alternate sync partner for merge replication. When I attempt to replicate from the alternate, the first steps occur correctly (through bulk copy), but then I receive an error message that the schema script could not be propagated to the subscriber. The details show three other errors prior to this one:
1)The merge process was unable to reinitialize the subscription
2)The merge process timed out while executing a query
3)Setting sentgen too high
I assume that "setting sentgen too high" is the root error, but I have no idea how to resolve it.
Any help is appreciated.

Primary Publisher/Distributor : SQL Server 2000 Standard/Windows 2000 Server
Sync Partner : SQL Server 2000 Personal/Windows 2000 Pro

4 replies

by md_hashim

You proabably want to check if any new indexes and joins have been created since you last replicated and if these are not the cause for concern...
-Hashim

This discussion is closed to new replies.