BUG: SQL Server Uses 100% of the CPU When Dump Pending

Last reviewed: April 28, 1997
Article ID: Q88483

The information in this article applies to:
  • Microsoft SQL Server version 4.2 for OS/2
BUG# 1458 (4.2)

SYMPTOMS

SQL Server goes to 100-percent CPU usage if a client workstation has a dump pending. This can happen when, for example, a client workstation begins a dump to a disk on the server, but there's no disk in the drive on the server. The dump is pending while SQL Server waits for you to insert a disk in the server. While the dump is pending, if you restart the client workstation and then try to log on again, SQL Server goes to 100-percent CPU usage and puts the following messages in the error log:

   fbsspacket: can't mount first diskette
   Start up the console program to continue using the
   dump device.

   Cannot send, host process disconnected: SAF 9569 spid 1
   Error: 1608, severity: 21, State: 2

Other clients attempting to log on at this time are not successful. The SQL Server machine becomes unusable.

WORKAROUND

If you can, finish the dump. Otherwise, you must stop and restart SQL Server.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: dump
Keywords : kbbug4.20 kbother SSrvLock SSrvServer
Version : 4.2
Platform : OS/2
Issue type : kberrmsg


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