Microsoft KB Archive/267599

= FIX: Running a Stored Procedure While SET FMTONLY is Off and On Can Cause 602, 604 and 618 Error Messages =

Article ID: 267599

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q267599



BUG #: 58127 (SQLBUG_70)



SYMPTOMS
Under the following conditions, error messages 602, 604 and 618 might appear in the SQL Server errorlog with a severity level of 21, which terminates the client connection:


 * A stored procedure is run repeatedly while SET FMTONLY is enabled and disabled.


 * The stored procedure creates and selects from temporary tables.



WORKAROUND
Minimize the use of temporary tables in stored procedures that are run on a frequent basis.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.



MORE INFORMATION
Here is the expected text from the errorlog for the three possible error messages:

Error 602:

2000-06-30 11:10:18.33 spid16 Error: 602, Severity: 21, State: 1

2000-06-30 11:10:18.33 spid16 Could not find row in sysindexes for database ID 2, object ID 1967346073, index ID -1. Run DBCC CHECKTABLE on sysindexes..

Error 604:

2000-06-30 11:13:30.85 spid16 Error: 604, Severity: 21, State: 5

2000-06-30 11:13:30.85 spid16 Could not find row in sysobjects for object ID 0 in database '0'. Run DBCC CHECKTABLE on sysobjects..

Error 618:

2000-06-30 11:11:26.71 spid10 Error: 618, Severity: 21, State: 1

2000-06-30 11:11:26.71 spid10 A varno of 666 was passed to the opentable system function. The largest valid value is 257..

Keywords: kbbug kbfix KB267599

-

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

© Microsoft Corporation. All rights reserved.