"michael.swinarski@cox.com" <mswinarski@gmail.com> wrote in message
news:1161963719.365159.113360@m7g2000cwm.googlegroups.com...
> Yesterday, we attempted to add a new table to an existing publication.
> We then created the table on the subscriber and populated it manually.
> We expected that replication would then take over the data flow to this
> table. This morning, I found that the log reader had failed with the
> following:
>
> 2006-10-27 15:20:46.966 Status: 0, code: 9003, text: 'The log scan
> number (94570:3522:134) passed to log scan in database 'RawData' is not
> valid. This error may indicate data corruption or that the log file
> (.ldf) does not match the data file (.mdf). If this error occurred
> during replication, re-create the publication. Otherwise, restore from
> backup if the problem results in a failure during startup. '.
> 2006-10-27 15:20:46.966 Status: 0, code: 22037, text: 'The process
> could not execute 'sp_replcmds' on 'CARZ0DB16\ARZSQL16'.'.
>
>
> Has anyone seen this error before?
>

"michael.swinarski@cox.com" <mswinarski@gmail.com> wrote in message
news:1161968994.976347.155110@i42g2000cwa.googlegroups.com...
> That part makes since.
>
> However this error does not tell me what subscription it is tripping
> over. I am guessing that it is associated with one of the publications
> that I added a table too; but I am not sure of this. Is there anyway
> to determine this for certain?
>
> -ms
>
>
> Hilary Cotter wrote:
>> I've encountered this. Basically the log reader writes the last LSN read
>> from the log into the distribution database. When you get this error it
>> means that the LSN read does not agree with what is in the distribution
>> database. Dropping the subscription and recreating it normally clears
>> this
>> error.
>>
>> --
>> 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
>>
>>
>>
>> "michael.swinarski@cox.com" <mswinarski@gmail.com> wrote in message
>> news:1161963719.365159.113360@m7g2000cwm.googlegroups.com...
>> > Yesterday, we attempted to add a new table to an existing publication.
>> > We then created the table on the subscriber and populated it manually.
>> > We expected that replication would then take over the data flow to this
>> > table. This morning, I found that the log reader had failed with the
>> > following:
>> >
>> > 2006-10-27 15:20:46.966 Status: 0, code: 9003, text: 'The log scan
>> > number (94570:3522:134) passed to log scan in database 'RawData' is not
>> > valid. This error may indicate data corruption or that the log file
>> > (.ldf) does not match the data file (.mdf). If this error occurred
>> > during replication, re-create the publication. Otherwise, restore from
>> > backup if the problem results in a failure during startup. '.
>> > 2006-10-27 15:20:46.966 Status: 0, code: 22037, text: 'The process
>> > could not execute 'sp_replcmds' on 'CARZ0DB16\ARZSQL16'.'.
>> >
>> >
>> > Has anyone seen this error before?
>> >
>