September 15, 2012 at 12:28 pm
When I try to run sanpshot job is also failing.
When I replication monitor, I see below error. Help needed.
Error messages:
The process could not execute 'sp_repldone/sp_replcounters' on 'Server_name'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
The log scan number (690:13675:299) passed to log scan in database 'DB_Name' 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. (Source: MSSQLServer, Error number: 9003)
Get help: http://help/9003
The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)
Get help: http://help/MSSQL_REPL22017
The process could not execute 'sp_repldone/sp_replcounters' on 'USSTLPMPINFDB63'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037
September 16, 2012 at 2:10 am
Danzz (9/15/2012)
The log scan number (690:13675:299) passed to log scan in database 'DB_Name' 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. (Source: MSSQLServer, Error number: 9003)
I should start by running checkdb on the published database. If that reports no errors you are going to have to set up the publication again. It seems the log reader cannot find a pointer in the log file to get any additional transactions (post BCP data export).
September 19, 2012 at 9:51 pm
This was removed by the editor as SPAM
December 16, 2013 at 10:59 am
To give a little background on my case.. the below error can be seen only when I run the trace from profiler for the event " Exception " :
the DBCC checkdb has no errors and I have run the sp_replrestart.. again.. but still gives the same error..
The log scan number (10040:15138:1) passed to log scan in database 'dbanme' 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.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply