Help and Support

FIX: Repetitive Connect/Disconnect May Shut Down SQL Server

View products that this article applies to.
Article ID:164734
Last Review:October 16, 2003
Revision:3.0
This article was previously published under Q164734
BUG #: 16416 (6.5)

SYMPTOMS

If a client application calls dbopen/dbclose (using DB-Library) or SQLConnect/SQLDisconnect (using ODBC) repetitively, it may cause the following error and shut down SQL Server. Web Servers also exhibit this behavior.
18001 Process %d entered sequencer without owning dataserver semaphore

This problem only happens on computers running Windows NT Server 4.0, and it occurs more frequently when both the clients and server are running on the same computer. In the scenarios where Microsoft was able to reproduce this error, the processor speed of the server needed to be fairly high, and even then this problem only surfaced occasionally.

Back to the top

WORKAROUND

To work around this problem, either move the client application to a separate computer or try to take advantage of the 'Connection Pooling' functionality provided by ODBC Driver Manager 3.0.

Back to the top

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

Back to the top

APPLIES TO
•Microsoft SQL Server 6.5 Standard Edition

Back to the top

Keywords: 
kbenv kbfix kbprogramming KB164734

Back to the top

Article Translations

 

Other Support Options

  • Contact Microsoft
    Phone Numbers, Support Options and Pricing, Online Help, and more.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.