Microsoft KB Archive/319693

= FIX: A Backup Log with the NO_TRUNCATE Option May Cause an Access Violation =

Article ID: 319693

Article Last Modified on 11/4/2002

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q319693



BUG #: 101131 (SQLBUG_70)



SYMPTOMS
For a suspect database, you can back up the current transaction log by using the Transact-SQL NO_TRUNCATE option.

When you try to do so, if the database is suspect because the secondary data file is not available, the query may fail with the following messages in SQL Query Analyzer:

Server: Msg 3013, Level 16, State 1, Line 1

Backup or restore operation terminating abnormally. ODBC: Msg 0, Level 19, State 1

SqlDumpExceptionHandler: Process 8 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

The following stack dump is written to the SQL Server 7.0 RTM error log file:   -- Short Stack Dump 0x41091082 Module(ums+1082) (UmsListBase::InsertTail+19) 0x410913aa Module(ums+13aa) (UmsList::InsertTail+1c) 0x41091379 Module(ums+1379) (UmsQueue::EnqueueTail+13) 0x410915e8 Module(ums+15e8) (UmsEvent::Wait+4c) 0x0057c28b Module(sqlservr+17c28b) (FCBIoRequestDispenser::GetIoreq+4c) 0x00409bd3 Module(sqlservr+9bd3) (FCB::AsyncRead+13) 0x00409eea Module(sqlservr+9eea) (DBTABLE::ScatterRead+65) 0x00409e73 Module(sqlservr+9e73) (bufgetfromdisk+1c3) 0x00402954 Module(sqlservr+2954) (bufget+13c) 0x00405229 Module(sqlservr+5229) (getpage2+68) 0x00404e8f Module(sqlservr+4e8f) (srchindex+131) 0x00407392 Module(sqlservr+7392) (prepscan+ce) 0x00407230 Module(sqlservr+7230) (LinkedPageSupplier::FirstPage+1d) 0x0040700c Module(sqlservr+700c) (LinkedPageSupplier::GetNextPage+41f) 0x00406e90 Module(sqlservr+6e90) (SDES::GetBiDi+1c2) 0x004102b7 Module(sqlservr+102b7) (createdes+28c) 0x00402cdb Module(sqlservr+2cdb) (opentabid+1b2) 0x00406052 Module(sqlservr+6052) (CSysScan::OpenScan+b4) 0x00405da8 Module(sqlservr+5da8) (CSysScan::StartScan+93) 0x004c43eb Module(sqlservr+c43eb) (CFileGroupScan::FStartScanAll+20) 0x0071b9a6 Module(sqlservr+31b9a6) (BackupOperation::LoadFileGroupList+36) 0x006f64cd Module(sqlservr+2f64cd) (BackupOperation::SnapshotMetadata+1d8) 0x006fe313 Module(sqlservr+2fe313) (BackupEntry::BackupLog+3ec) 0x005e0821 Module(sqlservr+1e0821) (CStmtDumpXact::XretExecute+5b) 0x00419efa Module(sqlservr+19efa) (CMsqlExecContext::ExecuteStmts+118) 0x00419a0f Module(sqlservr+19a0f) (CMsqlExecContext::Execute+16b) -



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.



MORE INFORMATION
To successfully back up the tail of a transaction log in SQL Server 7.0, both the transaction log file and the primary data file must be available. In SQL Server 2000, only the transaction log must be available.