FIX: Exists with Full Outer Join May Generate Access Violation

This article was previously published under Q290642
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 351266 (SHILOH_BUGS)
SYMPTOMS
When you execute a statement in which an EXISTS clause contains a FULL OUTER JOIN, an access violation may be raised, and you may receive the following error message:
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.Connection Broken
The SQL Server error log may contain an error similar to the following:
********************************************************************************* BEGIN STACK DUMP:* 02/28/01 21:58:41 spid 51** Exception Address = 0055A73F (COptExpr::DeriveGroupProperties(unsigned long) + 00000016 Line 0+00000000)* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION* Access Violation occurred reading address 00000014
RESOLUTION
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
STATUS
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
Properties

Article ID: 290642 - Last Review: 01/16/2015 21:47:55 - Revision: 3.2

Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB290642
Feedback