FIX: Concurrent Create and Drop of Stored Procedures May Cause Error 707

This article was previously published under Q194662
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 17134 (SQLBUG_65)
SYMPTOMS
If multiple connections are simultaneously creating and dropping storedprocedures, an error 707 may be generated and SQL Server may appear to stopresponding (hang). However, the SQL Server process is actually in a CPU-intensive loop and the system will return to normal within a few minutes.
Msg 707: System error detected during attempt to free memory at address 0x1a99000. Please consult the SQL Server error log for more details.
A typical situation in which this might occur is when an ODBC-basedapplication which is calling SQLPrepare() has also selected the option tocreate temporary stored procedures. These stored procedures are usuallydropped when the connection is closed, but may also be dropped when theODBC statement handle is closed, if the option is set to SQL_UP_ON_DROP.For additional information about prepared statements, please see thefollowing article in the Microsoft Knowledge Base:
151536 INF: SQLPrepare and Temporary Stored Procedures in SQL Server
WORKAROUND
To avoid this problem, minimize the number of times that procedures arecreated and dropped by either disabling the option to generate temporarystored procedures for prepared statements, or by dropping the proceduresonly when the connection is closed.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a
For more information, contact your primary support provider.
sp sp5prodsql cpu spike errorlog
Properties

Article ID: 194662 - Last Review: 10/10/2013 22:36:56 - Revision: 4.0

  • Microsoft SQL Server 6.5 Standard Edition
  • kbnosurvey kbarchive kbbug kbfix kbsqlserv650sp5fix KB194662
Feedback