FIX: Error message when you use a synonym for a stored procedure in SQL Server 2005: "A severe error occurred on the current command"

Article translations Article translations
Article ID: 928372 - View products that this article applies to.
Bug #: 50000495 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for applying this hotfix package
  • Whether you must restart the computer after you apply this hotfix package
  • Whether this hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply this hotfix package
  • The files that are contained in this hotfix package

SYMPTOMS

When you use a synonym for a stored procedure in Microsoft SQL Server 2005, you receive the following error message:
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Additionally, an access violation is logged in the SQL Server error log file.

This problem occurs if the following conditions are true:
  • You create the synonym for the stored procedure in the dbo schema.
  • The synonym name has the sp_ prefix.
  • You run the stored procedure by using the synonym.

RESOLUTION

Service pack information

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

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

  • SQL Server 2005 Service Pack 1 (SP1)

    For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    913089 How to obtain the latest service pack for SQL Server 2005

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
SQL Server 2005 32-bit version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Databasemailengine.dll9.0.2207.072,48020-11-200616:53x86
Logread.exe2005.90.2207.0398,11220-11-200616:53x86
Microsoft.analysisservices.adomdclient.dll9.0.2207.0543,52020-11-200616:53x86
Microsoft.analysisservices.deploymentengine.dll9.0.2207.0138,01620-11-200616:53x86
Microsoft.analysisservices.dll9.0.2207.01,215,26420-11-200616:53x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2207.075,55220-11-200616:53x86
Microsoft.sqlserver.sqlenum.dll9.0.2207.0908,06420-11-200616:53x86
Msasxpress.dll9.0.2207.022,30420-11-200616:53x86
Msgprox.dll2005.90.2207.0197,92020-11-200616:53x86
Msmdlocal.dll9.0.2207.015,614,75220-11-200616:53x86
Msmdredir.dll9.0.2207.03,990,30420-11-200616:53x86
Mssqlsystemresource.ldfNot Applicable524,28820-11-200614:28Not Applicable
Mssqlsystemresource.mdfNot Applicable40,108,03220-11-200614:28Not Applicable
Qrdrsvc.exe2005.90.2207.0366,88020-11-200616:53x86
Rdistcom.dll2005.90.2207.0640,80020-11-200616:53x86
Repldp.dll2005.90.2207.0184,60820-11-200616:53x86
Replmerg.exe2005.90.2207.0318,24020-11-200616:53x86
Replprov.dll2005.90.2207.0547,61620-11-200616:53x86
Replrec.dll2005.90.2207.0782,11220-11-200616:53x86
Replsub.dll2005.90.2207.0404,76820-11-200616:53x86
Spresolv.dll2005.90.2207.0174,36820-11-200616:53x86
Sqlaccess.dll2005.90.2207.0347,93620-11-200616:53x86
Sqlagent90.exe2005.90.2207.0318,75220-11-200616:53x86
Sqlservr.exe2005.90.2207.028,964,18420-11-200616:53x86
Sysdbupg.sqlNot Applicable218,48620-11-200611:26Not Applicable
Xmlsub.dll2005.90.2207.0192,80020-11-200616:53x86
Xpstar90.dll2005.90.2207.0292,64020-11-200616:53x86
Xpstar90.rll2005.90.2207.0152,86420-11-200616:53x86
SQL Server 2005 x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Databasemailengine.dll9.0.2207.072,48021-11-200612:23x86
Logread.exe2005.90.2207.0522,52821-11-200612:23x64
Mgdsqldumper.dll2005.90.2207.091,42421-11-200612:23x64
Microsoft.analysisservices.adomdclient.dll9.0.2207.0543,52020-11-200616:53x86
Microsoft.analysisservices.adomdclient.dll9.0.2207.0543,52021-11-200612:23x86
Microsoft.analysisservices.deploymentengine.dll9.0.2207.0138,01620-11-200616:53x86
Microsoft.analysisservices.dll9.0.2207.01,215,26420-11-200616:53x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2207.075,55220-11-200616:53x86
Microsoft.sqlserver.sqlenum.dll9.0.2207.0875,29621-11-200612:23x86
Msasxpress.dll9.0.2207.022,30420-11-200616:53x86
Msasxpress.dll9.0.2207.027,42421-11-200612:23x64
Msgprox.dll2005.90.2207.0259,36021-11-200612:23x64
Msmdlocal.dll9.0.2207.015,614,75220-11-200616:53x86
Msmdredir.dll9.0.2207.03,990,30420-11-200616:53x86
Mssqlsystemresource.ldfNot Applicable524,28820-11-200614:28Not Applicable
Mssqlsystemresource.mdfNot Applicable40,108,03220-11-200614:28Not Applicable
Qrdrsvc.exe2005.90.2207.0431,39221-11-200612:24x64
Rdistcom.dll2005.90.2207.0833,82421-11-200612:24x64
Repldp.dll2005.90.2207.0184,60820-11-200616:53x86
Repldp.dll2005.90.2207.0235,29621-11-200612:24x64
Replmerg.exe2005.90.2207.0415,00821-11-200612:24x64
Replprov.dll2005.90.2207.0745,24821-11-200612:24x64
Replrec.dll2005.90.2207.01,008,41621-11-200612:24x64
Replsub.dll2005.90.2207.0525,60021-11-200612:24x64
Spresolv.dll2005.90.2207.0223,00821-11-200612:24x64
Sqlaccess.dll2005.90.2207.0355,10421-11-200612:24x86
Sqlagent90.dll2005.90.2207.0389,92021-11-200612:24x64
Sqlservr.exe2005.90.2207.039,352,60821-11-200612:24x64
Sysdbupg.sqlNot Applicable218,48620-11-200611:26Not Applicable
Xmlsub.dll2005.90.2207.0317,21621-11-200612:24x64
Xpstar90.dll2005.90.2207.0540,96021-11-200612:24x64
Xpstar90eng.dll2005.90.2207.0153,37621-11-200612:24x64
SQL Server 2005 Itanium architecture version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Databasemailengine.dll9.0.2207.072,48020-Nov-200620:04x86
Logread.exe2005.90.2207.01,095,45620-Nov-200620:04IA-64
Microsoft.analysisservices.adomdclient.dll9.0.2207.0543,52020-Nov-200616:53x86
Microsoft.analysisservices.adomdclient.dll9.0.2207.0543,52020-Nov-200620:04x86
Microsoft.analysisservices.deploymentengine.dll9.0.2207.0138,01620-Nov-200616:53x86
Microsoft.analysisservices.dll9.0.2207.01,215,26420-Nov-200616:53x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2207.075,55220-Nov-200616:53x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2207.0163,10420-Nov-200620:04IA-64
Microsoft.sqlserver.sqlenum.dll9.0.2207.0875,29620-Nov-200620:04x86
Msasxpress.dll9.0.2207.022,30420-Nov-200616:53x86
Msasxpress.dll9.0.2207.055,07220-Nov-200620:04IA-64
Msgprox.dll2005.90.2207.0542,49620-Nov-200620:04IA-64
Msmdlocal.dll9.0.2207.048,610,08020-Nov-200620:04IA-64
Msmdredir.dll9.0.2207.06,244,12820-Nov-200620:04IA-64
Mssqlsystemresource.ldfNot Applicable524,28820-Nov-200614:28Not Applicable
Mssqlsystemresource.mdfNot Applicable40,108,03220-Nov-200614:28Not Applicable
Qrdrsvc.exe2005.90.2207.0941,34420-Nov-200620:04IA-64
Rdistcom.dll2005.90.2207.01,881,37620-Nov-200620:04IA-64
Repldp.dll2005.90.2207.0184,60820-Nov-200616:53x86
Repldp.dll2005.90.2207.0508,70420-Nov-200620:04IA-64
Replmerg.exe2005.90.2207.0954,65620-Nov-200620:04IA-64
Replprov.dll2005.90.2207.01,617,18420-Nov-200620:04IA-64
Replrec.dll2005.90.2207.02,141,47220-Nov-200620:04IA-64
Replsub.dll2005.90.2207.01,156,89620-Nov-200620:04IA-64
Spresolv.dll2005.90.2207.0495,39220-Nov-200620:04IA-64
Sqlaccess.dll2005.90.2207.0349,47220-Nov-200620:04x86
Sqlagent90.exe2005.90.2207.01,141,02420-Nov-200620:04IA-64
Sqlservr.exe2005.90.2207.072,291,10420-Nov-200620:05IA-64
Sysdbupg.sqlNot Applicable218,48620-Nov-200611:26Not Applicable
Xmlsub.dll2005.90.2207.0590,62420-Nov-200620:05IA-64
Xpstar90.dll2005.90.2207.0951,07220-Nov-200620:05IA-64
Xpstar90.rll2005.90.2207.0152,35220-Nov-200620:04IA-64

WORKAROUND

To work around this problem, use one of the following methods:
  • Rename the synonym without using the sp_ prefix.
  • Create the synonym in a user schema other than the dbo schema.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 2.

MORE INFORMATION

We strongly recommend that you do not use the sp_ prefix in any object name. SQL Server uses this prefix to designate system stored procedures. A user-defined stored procedure that has the same prefix as a system stored procedure is nonqualified or is never run by SQL Server.

For more information about the CREATE PROCEDURE statement, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms187926.aspx
For more information about how to create stored procedures, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/ms190669.aspx
For more information about how to run stored procedures, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/ms189915.aspx
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 928372 - Last Review: October 8, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Keywords: 
kbautohotfix kbsql2005sp2fix kbsql2005engine kbfix kbexpertiseadvanced kbHotfixServer kbqfe KB928372

Give Feedback

 

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