FIX: DUMP or LOAD with Tape May Fail on Windows NT 3.51

Last reviewed: June 27, 1997
Article ID: Q161125
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16346 (6.5)

SYMPTOMS

A SQL Server dump or load with a tape may fail on a computer running Windows NT 3.51 and some SCSI controllers.

WORKAROUND

To work around this problem, do any of the following:

  • Try to put the tape drive on a different SCSI adapter.
  • Upgrade to Windows NT 4.0.
  • Dump to disk files instead of tape files.

STATUS

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

MORE INFORMATION

The following are some of the possible errors that can be seen in the SQL Server errorlog:

   Error : 3201
   Can't open dump device '<device name>', device error or device off line.
   Please consult the SQL Server error log for more details.

   kernel   Unnamed tape \\.\tape0 mounted on tape drive \\.\tape0
   kernel   tprhdrs: failed to seek Tape Mark, operating system error:
      1101 (A tape access reached a filemark.)
   kernel   tbsreadhdr: Tape rejected
   kernel   tprvol: read returned 1104 (no more data is on the tape.)
      reading volume header


Additional query words: 6.50 blocksize backup restore
Keywords : kbbug6.50 kbhw kbinterop SSrvAdmin SSrvErr_Log SSrvGen kbbuglist
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix


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: June 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.