FIX: No table headers appear in the Excel report when you use SQL Server 2005 Reporting Services to export information to Excel

This 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

When you use Microsoft SQL Server 2005 Reporting Services to export information to Microsoft Excel, no table headers appear in the Excel report.

This problem may occur if a second grouping level is defined on the table from which you export the information to Excel. If a second grouping level is defined on the table, no table headers appear in the Excel report regardless of whether the following conditions are true:

• The grouping level is hooked to a related item.
• Group header or footer rows are used in the report.
• Data appears after the header or footer levels.

You are more likely to experience this problem if the information that you export to Excel contains a combination of the following items:

• A table header is present or absent in the reporting output.
• Group page breaks exist in the reporting output.
• Repeatable table headers exist in the reporting output.
• Multiple levels of grouping exist.

Service 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:

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.

Prerequisites

To 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 information

This 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 versions

SQL Server 2005 x64 editions

SQL Server 2005 IA-64 editions

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

To work around this problem, use one of the following methods:

• Add a page break at the start of the inner group.
• Do not mark the table header as repeatable.

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

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: 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: