I'm hoping someone can point me to information on something that was fixed in SSRS 2008R2 that would help me understand what's going on and find a work-around for SSRS 2008. I have a report (one out of nearly 100 in my product) that displays some #Error values when rendered by SSRS 2008 SP3, but that works properly when rendered by SSRS 2008R2 SP1. The report is very straightforward: a single MDX query that populates a single table (tablix). The table contains one column for each returned column from the query, one row for each returned row from the query, plus a totals row that displays, not surprisingly, Sum(Fields!FieldForThisColumn) for each of the columns. It is the totals row that's having problem: More than 1/2 of the columns are displaying #Error instead of the correct sum. All columns contain integer values. All Nulls/NaNs and other unusual values are converted to 0 by the query itself, so none of them make it to SSRS. Does this ring a bell with anyone? I need to come up with a workaround to get this report to render properly on SSRS 2008 - I'm really surprised to be hitting this since, as I mentioned, I have many dozens of reports, many of which have totals rows, that all render correctly in 2008. Also helpful would be some way to discover what the #Error means - this error does not repro in the design tools (which are 2008R2, of course), nor does it appear to be logged anywhere. -cd Mark the best replies as answers!

Is your datasource pointing same Cube as in R2 ? Hope this will help you !!! Sanjeewan

Is your datasource pointing same Cube as in R2 ? Of course! I have two SSRS instances - one 2008 SP3, one 2008 R2 SP1, both pointed at the same SSAS instance, same database, same cube, same report parameters, same RDL file deployed on both servers. -cd Mark the best replies as answers!

Well, I found a work-around, but it's nonsensical. In the MDX query, most of the returned columns were computed members of the form: with member [Measures].[ShortName] as coalesceEmpty([Measures].[Longer Name],0) The measures in question are integer values (they're all counts), but adding a seemingly useless CInt() around each of the calls to coalesceEmpty eliminated the problem with the report. I have a recollection that SSAS likes to return everything as float (or decimal?), so I'd have to guess that some kind of bug related to summing floats/decimals and formatting as an integer was fixed in SSRS 2008 R2.-cd Mark the best replies as answers!