Microsoft KB Archive/889400

= FIX: Description of the problems that are fixed in hotfix build 8.0.902 in Microsoft SQL Server 2000 Reporting Services =

Article ID: 889400

Article Last Modified on 5/15/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Reporting Services

-





Article Contents
 Summary Introduction  Problems that are fixed in this hotfix package

 Hotfix information Prerequisites Restart information</li> Registry information</li> Hotfix file information</li></ul> </li> Status</li> References</li></ul>

<div class="summary_section">

SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this 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.

back to the top

<div class="summary_section">

Introduction
This article describes the problems that are fixed in hotfix build 8.0.902 in Microsoft SQL Server 2000 Reporting Services.

back to the top

Problems that are fixed in this hotfix package
The three problems that are fixed in hotfix build 8.0.902 follow:  You can successfully create a report that is more than 85.33333 inches wide in Report Designer. You can do this in Microsoft Visual Studio .NET. However, when you close the report and reopen the report in Report Designer, you may receive the following error message:

Microsoft Development Environment is cannot load this document: Deserialization failed. The value must be between 0in and 85.33333in.

Parameter name: Width.

</li> You can export a report that contains one or more images to a Microsoft Excel worksheet. However, you may not be able to open the Excel worksheet. You may receive the following error message:

Unable to read file

This problem occurs because of restrictions on the length values for the images.</li> You can create a main report that has a sub-report. You can set the Visibility/Hidden property of the sub-report control to &quot;True.&quot; However, if you do this, you notice that the sub-report is unexpectedly visible when you export the main report to an Excel worksheet.

Note This problem only occurs after you apply SQL Server 2000 Reporting Services Service Pack 1. The problem does not occur for HTML rendering and for Portable Document Format (PDF) rendering.</li></ul>

back to the top

<div class="moreinformation_section">

Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000 Reporting Services. For more information, 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

Hotfix information
back to the top

Prerequisites
This hotfix requires SQL Server 2000 Reporting Services Service Pack 1.

For more information about how to obtain SQL Server 2000 Reporting Services Service Pack 1, 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

To install this hotfix, follow these steps:
 * 1) Stop SQL Server 2000 Reporting Services.
 * 2) Shut down the Microsoft Integrated Information Services (IIS) server that runs the SQL Server 2000 Reporting Services Web site.
 * 3) Unzip the file that is named SQL2000.RS-KB889400-v8.00.902.00-Eng.zip.
 * 4) Run the file that is named SQL2000.RS-KB889400-v8.00.902.00-Eng.exe.

back to the top

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

back to the top

Registry information
You do not have to create or to modify any registry keys to enable this hotfix.

back to the top

Hotfix file information
This hotfix contains only those files that are required to correct the problems that are described. 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. <pre class="fixed_text">  Date         Time   Version            Size    File name --  24-Nov-2004  19:43  8.0.902.0         823,296  Dundaswebchart.dll 24-Nov-2004 19:43  8.0.902.0         815,104  Dundaswinchart.dll 24-Nov-2004 19:44  8.0.902.0       6,823,936  Microsoft.reportingservices.designer.dll 24-Nov-2004 19:42  8.0.902.0         270,336  Microsoft.reportingservices.diagnostics.dll 24-Nov-2004 19:43  8.0.902.0         360,448  Microsoft.reportingservices.excelrendering.dll 24-Nov-2004 19:42  8.0.902.0         253,952  Microsoft.reportingservices.imagerendering.dll 24-Nov-2004 19:43  8.0.902.0       1,327,104  Microsoft.reportingservices.processing.dll 24-Nov-2004 19:42  8.0.902.0          73,728  Reportingservicesemaildeliveryprovider.dll 24-Nov-2004 19:43  8.0.902.0         536,576  Reportingserviceslibrary.dll 24-Nov-2004 19:43  8.0.902.0         495,616  Reportingserviceswebserver.dll Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

back to the top

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

This problem was first corrected in Microsoft SQL Server 2000 Reporting Services Service Pack 2.

back to the top

<div class="references_section">