Microsoft distributes Microsoft SQL Server 2008 Service Pack 1(SP1), or SQL Server 2008 R2 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 2008 Service Pack 1(SP1) or SQL Server 2008 R2 fix release.
Symptoms
SQL Server 2008 Reporting Services (SSRS 2008) or SQL Server 2008 R2 Reorting Services generates MHTML-formatted reports that are not compliant with the following standards:
-
(g) Row and column headers shall be identified for data tables.
-
(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
Note These are standards that are under "Web-based Intranet and Internet Information and Applications" in section 1194.22 of the Electronic and Information Technology Accessibility Standards. The Electronic and Information Technology Accessibility Standards implements section 508 of the Rehabilitation Act of 1973.For more information about the Electronic and Information Technology Accessibility Standards, visit the following United States Access Board website:
General information about Electronic and Information Technology Accessibility Standards
Resolution
Cumulative update information
SQL Server 2008 SP1
The fix for this issue was first released in Cumulative Update 11. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 1 (SP1), click the following article number to view the article in the Microsoft Knowledge Base:
2413738 Cumulative update package 11 for SQL Server 2008 Service Pack 1 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 1 (SP1) fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
SQL Server 2008 R2
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2438347 Cumulative Update package 5 for SQL Server 2008 R2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
SQL Server 2008 Service Pack 2
The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2467239 Cumulative update package 2 for SQL Server 2008 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
To apply this hotfix, you have to modify the following configuration element to the Rsreportserver.config file after you install this hotfix:<Extension Name="MHTML" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.MHtmlRenderingExtension,Microsoft.ReportingServices.HtmlRendering"/>To<Extension Name="MHTML" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.MHtmlRenderingExtension,Microsoft.ReportingServices.HtmlRendering"> <Configuration><DeviceInfo> <AccessibleTablix>true</AccessibleTablix></DeviceInfo></Configuration></Extension>Notes
-
The Rsreportserver.config file is located in the following path:
%ProgramFiles%\Microsoft SQL Server\MSRS10.<Database Instance>\Reporting Services\ReportServer
-
After you apply this hotfix, IDs are added to cells in tables for particular headers to comply with Section 508.
Important This hotfix does not claim full Section 508 standards compliance. This hotfix addresses specific standards to make SQL Server 2008 Reporting Services or SQL Server 2008 R2 Reporting Services more available to federal applications.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about "Web-based Intranet and Internet Information and Applications" in section 1194.22 of the Electronic and Information Technology Accessibility Standards, visit the following website:
General information about "Web-based Intranet and Internet Information and Applications" in section 1194.22 of the Electronic and Information Technology Accessibility Standards For more information about Section 508, visit the following Section 508 official website:
