FIX: Procedure Names That Begin with "sp_" Can Fail with an Access Violation

Article translations Article translations
Article ID: 320406 - View products that this article applies to.
This article was previously published under Q320406
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 101142 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

An access violation may occur if a user runs a user-defined procedure (not system procedures such as sp_who) that begins with the characters "sp_". The access violation (AV) can cause SQL Server to become unresponsive to existing and to new user connections.

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:
   Version      File name
   --------------------------

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

WORKAROUND

To work around this behavior, rename the user-defined procedure to a name that does not being with "sp_".

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.

MORE INFORMATION

SQL Server will write one (or both) of the following stack dumps to the SQL Server error log file when it experiences this access violation:
Short Stack Dump
0x00420b45 Module(sqlservr+20b45) (CCache::PcoLookupName+ce)
0x00420a28 Module(sqlservr+20a28) (CSQLObject::FTransform+112)
0x00413923 Module(sqlservr+13923) (CSQLSource::Execute+11c)
0x00518c3b Module(sqlservr+118c3b) (CStmtExec::XretLocalExec+126)
0x00518afa Module(sqlservr+118afa) (CStmtExec::XretExecute+253)
0x004145f1 Module(sqlservr+145f1) (CMsqlExecContext::ExecuteStmts+11a)
0x0041409f Module(sqlservr+1409f) (CMsqlExecContext::Execute+16a)
				
Short Stack Dump
0x0046859d Module(sqlservr+6859d) (CCache::PcoLookupId+ab)
0x004681b2 Module(sqlservr+681b2) (CSQLObject::FGetFromDisk+260)
0x00420a8a Module(sqlservr+20a8a) (CSQLObject::FTransform+219)
0x00413923 Module(sqlservr+13923) (CSQLSource::Execute+11c)
0x00518c3b Module(sqlservr+118c3b) (CStmtExec::XretLocalExec+126)
0x00518afa Module(sqlservr+118afa) (CStmtExec::XretExecute+253)
0x004145f1 Module(sqlservr+145f1) (CMsqlExecContext::ExecuteStmts+11a)
0x0041409f Module(sqlservr+1409f) (CMsqlExecContext::Execute+16a)
				

Properties

Article ID: 320406 - Last Review: October 24, 2013 - Revision: 1.1
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbsqlserv700presp4fix kbqfe kbhotfixserver KB320406

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com