FIX: Dump or Load w/Tape Devices Results in Errors, AVs

 Last reviewed: May 19, 1997
Article ID: Q153006
The information in this article applies to:
  • Microsoft SQL Server, version 6.5

SYMPTOMS

Attempts to dump or load with tape devices may generate errors 3201, tbswritecheck, or access violations (AVs). Msg 3201 and the tbswritecheck errors are seen when attempting to dump; the AV may occur during the load.

WORKAROUND

Do not dump to a tape device; dump and load using a different type of dump device, such as disk. If dumping to disk, use another backup package, such as Windows NT Backup, to archive the dump file to tape.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. The problem does not occur in SQL Server version 6.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

MORE INFORMATION

The behavior and error messages may vary from computer to computer. Some computers may report a Msg 3201 while the same tape drive and software may work correctly on a different computer, or the load process may generate an access violation (AV).

The 3201 and tbswritecheck errors may occur on any of the DUMP commands (DATABASE, TRANSACTION), and the AV may occur on any of the LOAD commands (DATABASE, TRANSACTION, TABLE).

For a robust backup and restore strategy, Microsoft recommends occasional verification that dumps can be loaded, along with additional testing when a device or software is changed. Certain database errors may also prevent a successful load, so it is important to run the recommended DBCC commands at the time of each backup.

Additional query words: dump load tape AV access violation
Keywords : kbbug6.50
Version : 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.