Microsoft KB Archive/166387

= FIX: Striped dumps may cause error 18001 =

Article ID: 166387

Article Last Modified on 2/22/2005

-

APPLIES TO


 * Microsoft SQL Server 6.0 Standard Edition
 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q166387



BUG #: 15703 (SQLBUG_60)

BUG #: 16758 (SQLBUG_65)



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:

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



STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in U.S. Service Pack 5a for Microsoft SQL Server 6.5. For additional information about how to download and install the latest SQL Server service pack, click the following article number to view the article in the Microsoft Knowledge Base:

274036 How to obtain SQL Server 6.5 Post Service Pack 5a Update

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

Keywords: kbbug kbfix kbusage KB166387

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.