Anybody know how to clean this up on a Log Reader Agent:
The specified LSN (0000f7b8:000000f6:0001) for repldone log scan occurs before the current start of replication in the log (00014d5f:00000814:0004).
That is what I ended up having to do.
I also ran sp_repldone with @reset = 1 to help clean things up.
You will have to manually fix the replication metadata tables. However the quick and dirty way to fix this is to
1) drop your subscription
2) recreate your subscription with a no-sync subscription
3) use the continue on data consistency errors profiler
4) do a validation to determine which tables are out of sync
5) manually fix these tables
-- Hilary CotterLooking for a SQL Server replication book?http://www.nwsu.com/0974973602.htmlLooking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
Don't rebuild and drop and all that, just use
In order to restart the Logreader, use SQL Suery analyser, select the replicated database and execute : sp_replrestart
This will reinitialise the LogReader