You might want to take a look at the just released SQL Server 2005 SP1 hotfix rollup. This package contains a collection fixes that came in too late to fit into the SP1 release process. Unfortunately, the descriptions of some of the bugs in the fix list isn’t very obvious, so I’ve listed the Reporting Services specific fixes below:
- Page breaks may not be respected when a table is rendered in Microsoft Office Excel if the report contains tables with the conditions of NoRows=true, NoRowsMessage=null, and the table contains a table header or footer.
- When a report contains an image that is external or is a resource in Reporting Services and the report uses the interactive sorting functionality, the image is replaced by a red x.
- If you include a subreport in a group footer and you enable the HideDuplicates property in a detail row on a grouping item, Reporting Services raises an internal error when you try to export the report. The error also occurs when you click Print Preview on the Preview tab in Report Designer.
- Reporting Services may intermittently display a System.NullReferenceException exception in the ReportSnapshot.EnsureAllStreamsAreClosed procedure. This behavior generates a mini-dump.
- When you try to run a linked report that uses the User!UserID variable and the execution properties are set to use Snapshots, you receive the following error message:
3wp!library!1!1/27/2006-13:10:27:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
If Y-axis margins are enabled and the minimum Y-value of all data points is a “nice” integer value, the Y-axis minimum value will be adjusted to a lower value. For example, the chart control rounds 4.0 to 4 to create a “nice” integer value. However, the generated Y-axis labels are incorrect.
When using a Report Builder Model on an Analysis Services data source, dates in the generated MDX queries may have the month and day parts transposed.