Article ID: 927290 - View products that this article applies to.
Bug #: 50000413 (SQL Hotfix)
NoticeMicrosoft 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.
This article describes the following about this hotfix release:
When you open a report that uses multiple report models in Report Manager in Microsoft SQL Server 2005 Reporting Services, you may receive one or more of the following error messages:
Error message 1
An error has occurred during report processing. There is already an open DataReader associated with this Command which must be closed first.
Error message 2
An error has occurred during report processing. The report server has encountered a configuration error. See the report server log files for more information.
Error message 3
Additionally, you find that the following error message is logged in the SQL Server Reporting Services error log file:
An internal error occurred on the report server. See the error log for more details. Server failed to resume the transaction, desc: 3d0000005c. The transaction active in this session has been committed or aborted by another session.
The first time that you open the report, the report may display correctly, and you may not receive any error messages. However, when you later open the report, you receive one or more of these error messages.
Server failed to resume the transaction, desc: 3d00000061. The transaction active in this session has been committed or aborted by another session
SQL Server 2005 Reporting Services processes all datasets in parallel. Modeling datasets are the only datasets in SQL Server 2005 Reporting Services that require some metadata from the catalog database. However, SQL Server 2005 Reporting Services opens only a single connection to the catalog database. All the parallel datasets cannot use this single connection.
Hotfix informationA 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=supportNote 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 Service Pack 1 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/913089/ )How to obtain the latest service pack for SQL Server 2005
Restart informationYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
Registry informationYou do not have to change the registry.
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 item in Control Panel.
SQL Server 2005 32-bit version
Collapse this tableExpand this table
SQL Server 2005 x64-based version
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
SQL Server 2005 Reporting Services may recover from this problem after several minutes. However, you may have to restart Microsoft Internet Information Services and the SQL Server service.
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/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:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 927290 - Last Review: September 17, 2011 - Revision: 2.0
Contact us for more help