Article ID: 274266 - View products that this article applies to.
This article was previously published under Q274266
BUG #: 58279 (SQLBUG_70)
BUG #: 236167 (SHILOH_bugs)
Under the following conditions, a client can receive error 3624 (retail assertion) and the client's connection to SQL Server is terminated:
SQL Server 2000To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/EN-US/ )INF: How to Obtain the Latest SQL Server 2000 Service Pack
SQL Server 7.0To resolve this problem, obtain the latest service pack for SQL Server 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/301511/EN-US/ )INF: How to Obtain the Latest SQL Server 7.0 Service Pack
HotfixNOTE: The following hotfix was created prior to Microsoft SQL Server 7.0 Service Pack 3.
The English version of this fix should have the following file attributes or later:
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
Version File name Platform ---------------------------------- 7.00.905 s70905i.exe x86 7.00.905 s70905a.exe alpha
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
SQL Server 2000This problem was first corrected in SQL Server 2000 Service Pack 1.
SQL Server 7.0This problem was first corrected in SQL Server 7.0 Service Pack 3.
The following messages appear in the SQL Server error log file preceded by a stack trace:
A retail assertion is a check for invalid data so that the client can be stopped when it is running with unexpected values.
2000-08-14 15:13:44.21 kernel SQL Server Assertion: File: <r:\SPHINX\NTDBMS\storeng\drs\oledb\rowsort.h>, line=720 Failed Assertion = 'm_ecP == Ec'.
2000-08-14 15:13:44.23 spid7 Error: 3624, Severity: 20, State: 1.