Article ID: 226125 - View products that this article applies to.
This article was previously published under Q226125
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 18663 (SQLBUG_65)
Some errors encountered when executing an INSERT..EXEC of an extended stored procedure can lead to one of the following errors incorrectly written to the ERRORLOG with no message text:
Error: 3601, Severity: 25, State: 1
Error: 3602, Severity: 25, State: 0
Error: 3603, Severity: 25, State: 0
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:
197177If 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:
(https://support.microsoft.com/kb/197177/EN-US/ )INF: How to Obtain SQL Server 6.5 Service Pack 5a
274036For more information, contact your primary support provider.
(https://support.microsoft.com/kb/274036/EN-US/ )INF: How to Obtain SQL Server 6.5 Post Service Pack 5a Update
These errors have no message text associated with them. These errors are not intended to be written to the ERRORLOG or returned to the user. They are considered "control" errors within the server. The errors are used to direct the flow of control for certain types of error conditions such as a deadlock.
Article ID: 226125 - Last Review: October 20, 2013 - Revision: 4.0