BUG: Striped Dumps May Cause Error 18001

Last reviewed: April 4, 1997
Article ID: Q166387

The information in this article applies to:

Microsoft SQL Server, versions 6.0 and 6.5

BUG #: 15703 (6.0)

       16758 (6.5)

SYMPTOMS

If a striped database dump runs into an operating system error (like error 112 -- out of disk space), an error 18001 may occur that can cause SQL Server to become unresponsive. The following is the message that is written to the errorlog:

   Spid10 Process 10 entered sequencer without owning dataserver semaphore.

WORKAROUND

To work around this problem, either make sure that there is sufficient disk space available for the dump, or do not stripe the dump. For sample code to create an extended stored procedure that reports free drive space, see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q164970
   TITLE     : BUG: Disk Dumps May Cause Handled AV When Space Is Low

STATUS

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

MORE INFORMATION

If SQL Server is not run as a service, you may see the following additional errors in the command prompt where SQL Server was started. However, these messages are not written to SQL Server's errorlog:

   RELEASE_DATASERV semcount < 0
   RELEASE_DATASERV_FOR_SLEEP semcount < 0
   GET_DATASERV_POST_SLEEP semcount < 0

Keywords : kbusage SSrvAdmin SSrvGPF kbbug6.00 kbbug6.50
Version : 6.0 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbpending

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