FIX: The Excel worksheet may be corrupted, and you may receive an error message when you export a report to an Excel worksheet in SQL Server 2000 Reporting Services Service Pack 2 (909108)



The information in this article applies to:

  • Microsoft SQL Server 2000 Reporting Services Service Pack 2

BUG #: 408705 (SQLBUDT)
Microsoft distributes Microsoft SQL Server 2000 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 2000 fix release.

SUMMARY

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

SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2000 Reporting Services Service Pack 2 (SP2), you export a report to a Microsoft Excel worksheet. The report contains lots of data. Then, you try to open the Excel worksheet. In this scenario, the Excel worksheet may be corrupted. Additionally, you may receive the following error message:
This file is not in a recognizable format.
When you export the report to the Excel worksheet, the following error message may be logged in the Reporting Services log:
w3wp!library!310!<Data>-<Time>:: i INFO: Call to RenderNext( '/<path>/test_issue' )
w3wp!chunks!310!<Data>-<Time>:: i INFO: ### GetReportChunk('RenderingInfo_EXCEL', 2), chunk was not found! this=ef865a28-9cf7-47fc-93c6-ea42df76e83f

CAUSE

This problem may occur when data is exported from a table column that contains very long strings.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

  • SQL Server 2000 Reporting Services SP2

    For more information about how to obtain SQL Server 2000 Reporting Services service packs, click the following article number to view the article in the Microsoft Knowledge Base:

    842440 How to obtain the latest service pack for SQL Server 2000 Reporting Services

Restart information

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

Registry information

You do not have to create a registry key or modify a registry key to use one of the hotfixes that this package contains.

Hotfix file information

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

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.
File nameFile versionFile sizeDateTimePlatform
Microsoft.reportingservices.diagnostics.dll8.0.1047.0270,33614-Oct-200522:57x86
Ms.rs.diagnostics.dll8.0.1047.0270,33614-Oct-200522:57x86
Ms.rs.pabin.csvrendering.dll8.0.1047.057,34414-Oct-200522:57x86
Ms.rs.pabin.excelrendering.dll8.0.1047.0364,54414-Oct-200522:57x86
Ms.rs.pabin.htmlrendering.dll8.0.1047.0389,12014-Oct-200522:57x86
Ms.rs.pabin.imagerendering.dll8.0.1047.0262,14414-Oct-200522:57x86
Ms.rs.pabin.webserver.dll8.0.1047.0503,80814-Oct-200522:57x86
Reportingservices.csvrendering.dll8.0.1047.057,34414-Oct-200522:57x86
Reportingservices.diagnostics.dll8.0.1047.0270,33614-Oct-200522:57x86
Reportingservices.excelrendering.dll8.0.1047.0364,54414-Oct-200522:57x86
Reportingservices.htmlrendering.dll8.0.1047.0389,12014-Oct-200522:57x86
Reportingservices.imagerendering.dll8.0.1047.0262,14414-Oct-200522:57x86
Reportingservicesnativeserver.dll2000.80.1047.048,64014-Oct-200522:57x86
Reportingserviceswebserver.dll8.0.1047.0503,80814-Oct-200522:57x86
Rswebuserinterface.dll8.0.1047.0770,04814-Oct-200522:57x86

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

You may also experience this problem in SQL Server 2000 Reporting Services Service Pack 1 (SP1) and in SQL Server 2000 Reporting Services without a service pack. However, this hotfix only applies to SQL Server 2000 Reporting Services SP2.

For more information, 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


Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbQFE kbhotfixserver kbpubtypekc KB909108 kbAudITPRO kbAudDeveloper