Knowledge Base

BUG: Concurrent Insert with Open Object Reuse May Cause the Server to Stop Responding

Article ID: 178296

Article Last Modified on 10/3/2003

Microsoft SQL Server 6.5 Standard Edition

This article was previously published under Q178296

BUG #: Windows NT: 17420 (6.5)

SYMPTOMS

Concurrent insert activity on a SQL Server with multiple processors when open objects must be reused may cause the server to stop responding. Existing connections will not be able to process commands or receive results. New connections will either stop responding or fail if the server is past the user connection limit.

A primary symptom of this problem is that the following message appears in the SQL Server errorlog:

spid10 Warning: OPEN OBJECTS parameter may be too low
spid10 attempt was made to free up descriptors in localdes()
spid10 Run sp_configure to increase parameter value

WORKAROUND

To work around this problem, increase the 'open objects' configuration value.

STATUS

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

MORE INFORMATION

For more information about the 'open objects' configuration option, see the following article in the Microsoft Knowledge Base:

114843 : INF: Explanation of Open Objects in SQL Server

Additional query words: hang hung lock locked up freeze frozen crashed crash crashes

Keywords: kbbug kbsqlserv650bug KB178296