FIX: Scheduled Backups May Hang w/ Unexpired Tapes

Last reviewed: April 29, 1997
Article ID: Q117515

The information in this article applies to:

  - Microsoft SQL Server version 4.2

BUG# NT: 9463 (4.20)

SYMPTOMS

If a scheduled backup attempts to overwrite a tape and the tape has a media retention period on it that has not expired, the backup may hang. The backup cannot be killed, and SQL Monitor cannot be stopped. SQL Server must be restarted to get rid of the hung backup process.

CAUSE

SQL Monitor is not properly handling the tape expiration message from SQL Server.

WORKAROUND

If it is not critical to use expiration dates on the tapes, use sp_configure to change the media retention period to zero. Otherwise, ensure that when a dump is scheduled with the INIT option, the expiration date has expired.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for Windows NT. This problem was corrected in SQL Server version 4.21. For more information, please contact your primary support provider.

Additional query words: sqlmontr.exe freeze dump Windows NT
Keywords : kbbug4.20 kbfix4.21 kbtool SSrvAdmin
Version : 4.2 4.21
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: April 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.