Mentioned
In
|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 910416 - Last Review: June 1, 2006 - Revision: 2.6 FIX: Error message when you run certain queries or certain stored procedures in SQL Server 2005: "A severe error occurred on the current command"BUG #: 412387 (SQLBUDT) 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. On This PageSUMMARYThis article describes the following about this hotfix
release: - The issues that are fixed by the hotfix package
- The prerequisites for installing the hotfix
package
- Whether you must restart the computer after you install the
hotfix package
- Whether the hotfix package is replaced by any other hotfix
package
- Whether you must make any registry changes
- The files that are contained in the hotfix
package
SYMPTOMSWhen you run certain queries or certain stored procedures in Microsoft SQL
Server 2005, you receive an error message that is similar to the following:
Msg 0, Level 11, State 0, Line 0 A severe error
occurred on the current command. The results, if any, should be
discarded. Additionally, information that is similar to the following may appear in the SQL Server 2005 Exception.log file: <date> <time> spid 56 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION reading address 00000020 at 0x0110B72B 2. You may experience this problem after you upgrade a computer
that is running SQL Server to the release version of SQL
Server 2005. RESOLUTIONService pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089Â
(http://kbalertz.com/Feedback.aspx?kbNumber=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: 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. PrerequisitesTo apply this hotfix, you must have SQL Server 2005 installed on the computer. 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 informationThis 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 tool in Control Panel. SQL Server 2005 32-bit versionsCollapse this tableExpand this table | File name | File version | File
size | Date | Time | Platform |
|---|
| Dtspipeline.dll | 2005.90.1500.0 | 600,280 | 09-Nov-2005 | 04:19 | x86 | | Microsoft.datatransformationservices.vsintegration.dll | 9.0.1500.0 | 330,456 | 09-Nov-2005 | 04:19 | x86 | | Microsoft.reportingservices.excelrendering.dll | 9.0.1500.0 | 326,360 | 09-Nov-2005 | 04:19 | x86 | | Msmdlocal.dll | 9.0.1500.0 | 15,581,912 | 09-Nov-2005 | 04:19 | x86 | | Msmdpp.dll | 9.0.1500.0 | 3,824,856 | 09-Nov-2005 | 04:19 | x86 | | Msmdpump.dll | 9.0.1500.0 | 3,912,408 | 09-Nov-2005 | 04:19 | x86 | | Msmdredir.dll | 9.0.1500.0 | 3,926,744 | 09-Nov-2005 | 04:19 | x86 | | Msmdsrv.exe | 9.0.1500.0 | 14,559,448 | 09-Nov-2005 | 04:19 | x86 | | Msmgdsrv.dll | 9.0.1500.0 | 5,935,320 | 09-Nov-2005 | 04:19 | x86 | | Msolap90.dll | 9.0.1500.0 | 4,202,200 | 09-Nov-2005 | 04:19 | x86 | | Nsservice.exe | 9.0.1500.0 | 18,648 | 09-Nov-2005 | 04:19 | x86 | | Reportingservicesservice.exe | 9.0.1500.0 | 14,552 | 09-Nov-2005 | 04:19 | x86 | | Sqlaccess.dll | 2005.90.1500.0 | 349,400 | 09-Nov-2005 | 04:19 | x86 | | Sqlca.dll | 2005.90.1500.0 | 3,207,384 | 09-Nov-2005 | 04:19 | x86 | | Sqldiscoveryapi_s.dll | 2005.90.1500.0 | 527,064 | 09-Nov-2005 | 04:19 | x86 | | Sqlncli.dll | 2005.90.1500.0 | 2,208,528 | 09-Nov-2005 | 04:19 | x86 | | Sqlservr.exe | 2005.90.1500.0 | 28,769,040 | 09-Nov-2005 | 04:20 | x86 |
SQL Server 2005 x64 editionsCollapse this tableExpand this table | File name | File version | File
size | Date | Time | Platform |
|---|
| Dtspipeline.dll | 2005.90.1500.0 | 1,054,936 | 09-Nov-2005 | 18:50 | x64 | | Microsoft.reportingservices.excelrendering.dll | | 326,360 | 09-Nov-2005 | 18:50 | x86 | | Msmdlocal.dll | 9.0.1500.0 | 30,001,368 | 09-Nov-2005 | 18:51 | x64 | | Msmdpp.dll | 9.0.1500.0 | 4,881,112 | 09-Nov-2005 | 18:51 | x64 | | Msmdpump.dll | 9.0.1500.0 | 4,951,256 | 09-Nov-2005 | 18:51 | x64 | | Msmdredir.dll | 9.0.1500.0 | 4,830,936 | 09-Nov-2005 | 18:51 | x64 | | Msmdsrv.exe | 9.0.1500.0 | 29,326,040 | 09-Nov-2005 | 18:51 | x64 | | Msmgdsrv.dll | 9.0.1500.0 | 8,907,992 | 09-Nov-2005 | 18:51 | x64 | | Msolap90.dll | 9.0.1500.0 | 5,663,960 | 09-Nov-2005 | 18:51 | x64 | | Nsservice.exe | 9.0.1500.0 | 18,648 | 09-Nov-2005 | 18:50 | x86 | | Reportingservicesservice.exe | 9.0.1500.0 | 14,552 | 09-Nov-2005 | 18:50 | x86 | | Sqlaccess.dll | 2005.90.1500.0 | 356,568 | 09-Nov-2005 | 18:50 | x86 | | Sqlca.dll | 2005.90.1500.0 | 4,278,488 | 09-Nov-2005 | 18:50 | x64 | | Sqldiscoveryapi_s.dll | 2005.90.1500.0 | 745,688 | 09-Nov-2005 | 18:50 | x64 | | Sqlncli.dll | 2005.90.1500.0 | 3,151,632 | 09-Nov-2005 | 18:50 | x64 | | Sqlservr.exe | 2005.90.1500.0 | 39,466,712 | 09-Nov-2005 | 18:51 | x64 |
SQL Server 2005 IA-64 editionsCollapse this tableExpand this table | File name | File version | File
size | Date | Time | Platform |
|---|
| Dtspipeline.dll | 2005.90.1500.0 | 1,915,608 | 09-Nov-2005 | 17:17 | IA-64 | | Microsoft.reportingservices.excelrendering.dll | 9.0.1500.0 | 326,360 | 09-Nov-2005 | 17:17 | x86 | | Msmdlocal.dll | 9.0.1500.0 | 48,409,304 | 09-Nov-2005 | 17:18 | IA-64 | | Msmdpp.dll | 9.0.1500.0 | 6,469,848 | 09-Nov-2005 | 17:17 | IA-64 | | Msmdpump.dll | 9.0.1500.0 | 6,519,512 | 09-Nov-2005 | 17:17 | IA-64 | | Msmdredir.dll | 9.0.1500.0 | 6,071,512 | 09-Nov-2005 | 17:17 | IA-64 | | Msmdsrv.exe | 9.0.1500.0 | 47,369,944 | 09-Nov-2005 | 17:18 | IA-64 | | Msmgdsrv.dll | 9.0.1500.0 | 12,840,152 | 09-Nov-2005 | 17:18 | IA-64 | | Msolap90.dll | 9.0.1500.0 | 7,683,800 | 09-Nov-2005 | 17:17 | IA-64 | | Nsservice.exe | 9.0.1500.0 | 18,648 | 09-Nov-2005 | 17:17 | x86 | | Reportingservicesservice.exe | 9.0.1500.0 | 14,552 | 09-Nov-2005 | 17:17 | x86 | | Sqlaccess.dll | 2005.90.1500.0 | 351,448 | 09-Nov-2005 | 17:17 | x86 | | Sqlca.dll | 2005.90.1500.0 | 10,563,288 | 09-Nov-2005 | 17:18 | IA-64 | | Sqldiscoveryapi_s.dll | 2005.90.1500.0 | 1,924,312 | 09-Nov-2005 | 17:17 | IA-64 | | Sqlncli.dll | 2005.90.1500.0 | 5,384,464 | 09-Nov-2005 | 17:17 | IA-64 | | Sqlservr.exe | 2005.90.1500.0 | 72,186,584 | 09-Nov-2005 | 17:18 | IA-64 |
Note Because of file dependencies, the most recent hotfix or feature
that contains these files may also contain additional files. STATUSMicrosoft
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 1. MORE INFORMATION
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 Â
(http://kbalertz.com/Feedback.aspx?kbNumber=822499/
)
New naming schema for Microsoft SQL Server software update
packages
For more information about the terminology that Microsoft uses when Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe
Microsoft software updates
APPLIES TO- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Workgroup Edition
| kbautohotfix kbsql2005sp1fix kbsql2005engine kbsql2005presp1fix kbbug kbfix kbhotfixserver kbqfe KB910416 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please
|
 |
 |
 |
 |
 |
 |
 |
| |