FIX: Striped Dumps May Cause Error 18001

• Microsoft SQL Server versions 6.0, 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:

Q164970 FIX: Disk Dumps May Cause Handled AV When Space Is Low

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 5a for Microsoft SQL Server version 6.5. For information about downloading and installing the latest SQL Server Service Pack, see http://support.microsoft.com/support/sql/.

For more information, contact your primary support provider.

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

Additional query words:

Keywords : kbusage SSrvAdmin SSrvGPF kbbug6.50 kbfix6.50.SP5
Version : winnt:6.0,6.5
Platform : winnt
Issue type : kbbug