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

Article Contents

• Summary
• Introduction
  • Problems that are fixed in this hotfix package
  • Hotfix information
  • Prerequisites
  • Restart information
  • Registry information
  • Hotfix file information
• Status
• References

SUMMARY

• 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.

Introduction

Problems that are fixed in this hotfix package

• 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.
• 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.
• You can create a main report that has a sub-report. You can set the Visibility/Hidden property of the sub-report control to "True." 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.