This article was previously published under Q253927
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 18759 (SQLBUG_65)
Under a load in which many deadlocks occur at the same time, a SQL Server with Service Pack 5a may experience an access violation and the server stops responding if you are using Trace flag 1204.
Turn off Trace flag -T1204.
Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in the Post Service Pack 5a Update for Microsoft SQL Server version 6.5. To install the Post Service Pack 5a Update, you must have either SQL Server 6.5 SP5 or SP5a installed.
For information about how to download and install the SQL Server 6.5 Service Pack 5a, refer to the following article in the Microsoft Knowledge Base:
197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a
If you already have SQL Server 6.5 SP5 or SP5a installed, you can download the Post SP5a Update from the following article in the Microsoft Knowledge Base:
274036 INF: How to Obtain SQL Server 6.5 Post Service Pack 5a Update
For more information, contact your primary support provider.
The symptoms you might experience if SQL Server stops responding can include:
SQL Server becomes totally unresponsive to existing connections (Commands like "Select @@version" may also fail to complete).
No new connections are possible (Make sure that you try to connect over a Local Pipe).
SQL Server Service may be in a undetermined state and it may not be possible to stop the service.