BUG: SQL Server Uses 100% of the CPU When Dump PendingLast reviewed: April 28, 1997Article ID: Q88483 |
The information in this article applies to:
SYMPTOMSSQL 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: 2Other clients attempting to log on at this time are not successful. The SQL Server machine becomes unusable.
WORKAROUNDIf you can, finish the dump. Otherwise, you must stop and restart SQL Server.
STATUSMicrosoft 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
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |