Thanks for the responses. I ended up droping and recreating the
"Hilary Cotter" wrote:
> This is a problem with your log reader agent. It could be data related or
> possibly something with your system. It might be solved by a reboot.
>
> A quick fix is to run sp_repldone, but then you will be marginally out of
> sync. Its also possible to locate the offending command and delete it. You
> could also drop the subscriptions and do a no-sync, again there will be
> synchronization errors.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> Looking for a SQL Server replication book?
>
http://www.nwsu.com/0974973602.html >
> Looking for a FAQ on Indexing Services/SQL FTS
>
http://www.indexserverfaq.com >
>
>
> "Frank" <Frank@discussions.microsoft.com> wrote in message
> news:F9CA8418-51D3-4524-9535-59647399861C@microsoft.com...
> > An invalid datetime value was encountered. Value exceeds the year 9999.
> >
> > I'm running SQL Server 2000 Transaction Replication. The replication has
> > been running without issue for 377 days. This morning I got the
> > following:
> >
> > Error Message:
> > The process could not execute 'sp_replcmds' on 'servername'.
> >
> > Error Details:
> > An invalid datetime value was encountered. Value exceeds the year 9999.
> > (Source: servername (Data source); Error number: 542)
> >
> > I've read through all the other threads where this has been mentioned and
> > have tried changing the default profile settings for QueryTimeout and
> > ReadBatchSize to 50000 and 1 respectively, but after restarting the
> > LogReader, I get the error above. I've run DBCC CHECKDB and no errors
> > were
> > returned. I tried querying the articles being published for invalid
> > dates,
> > but nothing was returned. Anything else out there I can try?
> >
> > Regards,
> > Frank
>
>