MSSQLSERVER_9003
Details
Product Name |
SQL Server |
Product Version |
10.0 |
Product Build Number |
10.00.0000.00 |
Event ID |
9003 |
Event Source |
MSSQLSERVER |
Component |
SQLEngine |
Symbolic Name |
LOG_INVALID_LSN |
Message Text |
The log scan number %S_LSN passed to log scan in database '%.*ls' 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. |
Explanation
A component passed an invalid log sequence number to the log manager for the database. This could be replication, corruption, or an inconsistency between the primary data file and the log.
User Action
If this occurred during replication, recreate the publication. Otherwise, restore from backup.
Internal-Only
<xmrFileHeader><buildNo>10.00.0000.00</buildNo><component>SQLEngine</component><dsDbName></dsDbName><dsProjectName>SQLServer2005</dsProjectName><exportDate>2005-08-22T14:00:12</exportDate><importDate>2005-08-22T12:43:00</importDate><prodContact>pingwang</prodContact><prodName>SQL Server</prodName><prodVer>10.0</prodVer><sourceFileDepotPath></sourceFileDepotPath><sourceFileExt></sourceFileExt><sourceFileName></sourceFileName><userDefined></userDefined><xmrFilePath>.\sqlXMR.xml</xmrFilePath></xmrFileHeader><resourceString resourceStringGuid="7fdfb391-5c6f-428b-b434-6c3d0b30fd7b" resourceStringProxyID="MSSQL_ENG009003"><exportStatus>Do Not Export</exportStatus><importStatus>Unchanged</importStatus><inActive>No</inActive><inserts></inserts><message><cause>Some component passed an invalid log sequence number to the log manager for the database. Could be replication, corruption, or some disconnect between primary data file and the log.</cause><causeCorrectiveActionStatus>Dev Signed Off</causeCorrectiveActionStatus><correctiveAction>If replication, may need to recreate the publication. Otherwise, restore from backup if this cascades to a startup failure.</correctiveAction><error><exMsgBoxID></exMsgBoxID><exMsgBoxSource></exMsgBoxSource></error><event><eventCategory></eventCategory><eventFacility></eventFacility><eventLanguage></eventLanguage><eventSeverityType></eventSeverityType><eventType></eventType><momEvent>Yes</momEvent><momOwner>donv</momOwner><winRegEventID>9003</winRegEventID><winRegEventSource>MSSQLSERVER</winRegEventSource></event><msuid></msuid></message><numericID>9003</numericID><owner>peterbyr</owner><pssReview><pssComments></pssComments><pssDebugger>No</pssDebugger><pssEngineer></pssEngineer><PSSSupportability>No</PSSSupportability></pssReview><suspect>No</suspect><symbolicName>LOG_INVALID_LSN</symbolicName><text>The log scan number %S_LSN passed to log scan in database '%.*ls' 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. </text><type></type><ueReview><assignedTo></assignedTo><bugID></bugID><bugRequired>No</bugRequired><comments></comments><docStudio><dsTopicId></dsTopicId><export>Yes</export></docStudio><editor></editor><revisedStringText></revisedStringText><workStatus>Not Reviewed</workStatus><writer></writer></ueReview><userDefined><eventLoggingLevel></eventLoggingLevel></userDefined></resourceString>