Microsoft KB Archive/303344

From BetaArchive Wiki
Knowledge Base


Article ID: 303344

Article Last Modified on 10/15/2002



APPLIES TO

  • Microsoft SQL Server 7.0 Standard Edition



This article was previously published under Q303344

BUG #: 101756 (SQLBUG_70)

SYMPTOMS

Use of a query that involves the AN identity may result in the SQL Server client being forcefully disconnected and the following stack trace is reported in the SQL Server error log:

0x0043cc05 Module(sqlservr+3cc05) (CONSTANT::CONSTANT+6e)                   
0x00782df9 Module(sqlservr+382df9) (trConstant::trConstant+31)              
0x005faad4 Module(sqlservr+1faad4) (PtrBldGetIdentity+125)                  
0x00531660 Module(sqlservr+131660) (CCompPlan::Result+5dc)                  
0x0044a4ab Module(sqlservr+4a4ab) (CCompPlan::FPreprocess+19c)              
0x004383d0 Module(sqlservr+383d0) (CCompPlan::FCompileStep+7e6)             
0x0043d00f Module(sqlservr+3d00f) (CProchdr::FCompile+5d9)                  
.
.
. 
                

CAUSE

The CONSTANT::CONSTANT code line attempts to copy an extra character from the table name, which then causes the exception error.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack


NOTE: The following hotfix was created prior to Microsoft SQL Server 7.0 Service Pack 4.

The English version of this fix should have the following file attributes or later:

   Filename       Platform
   -----------------------

   701000i.exe    Intel
                

NOTE: Because of file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

WORKAROUND

Change the length of the table to help avoid an allocation on a Microsoft Windows NT page boundary.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.

Keywords: kbbug kbfix KB303344