SSRS error when exporting as PDF: Index was outside the bounds of the array

Question

SSRS error when exporting as PDF: Index was outside the bounds of the array

lisa.randles

Default port

Points: 1448
More actions
September 24, 2013 at 7:51 am

#278369

Hello all...
I have an SSRS report that, when you try to save it as a pdf, tiff, or print preview, returns the error: "An error occurred during the local report processing. Index was outside the bounds of the array". If you export it any other way, it works fine.
I've searched all over the internet, and of course the SSC forums, but have not found an answer that can be applied. There is a hotfix (link below) that specifies "Reporting Services 2008" and indicates "The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 Service Pack 1.", however, we use SQL 2008 R2 sp2 (and Reporting Services 2008 R2, sp2?). I assume the hotfix would have been included as part of the cumulative upgrade and subsiquent service packs - but if so, why are we even having this issue?
Since I couldn't find a fix specifically for 2008 R2, I went ahead and tried to install it (thinking Reporting Services may still be regarded as regular 'ol 2008), I receive the error: "There are no SQL Server instance or shared features that can be updated on this computer." SQL and Reporting Services are definately installed (tried to apply to 3 different servers and my local machine).
According to the hotfix, "This problem occurs because SSRS 2008 does not normalize the column header width for the inner tablix on the second page of the matrix."
This is the hotfix that appears to be the solution but does not seem to apply to 2008 R2 sp2: http://support.microsoft.com/kb/978636?wa=wsignin1.0
Any suggestions would be greatly appreciated, please let me know if i could supply additional information.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Tee Time Hall of Fame Points: 3745 More actions · Answer 1

Hi Lisa,

Just this one report is acting this way? Have you tried renaming it and publishing it to the report server and seeing if that makes any difference?

Steven.Howes SSCertifiable Points: 6230 More actions · Answer 2

what about the reporting services logs? any additional info there?

lisa.randles Default port Points: 1448 More actions · Answer 3

Thanks for the replies and sorry for the delay in response. The person I'm troubleshooting this for is out on leave so it became a lower priority. 😉

Just this one report is acting this way? Have you tried renaming it and publishing it to the report server and seeing if that makes any difference?

We can recreate it with other reports if we set them up the same way, rename yields the same results. Reports that are not set up the same way can publish to pdf without a problem. I have not tried publishing the report yet...as I'm waiting for her to return so I do it correctly.

Per the user: The error I receive happens when I uncheck the ability to repeat header columns on one of the matrices. According to Microsoft this is occurs because SSRS 2008 does not normalize the column header width for the inner tablix on the second page of the matrix.

what about the reporting services logs? any additional info there?

I don't see anything in the ReportServerService error log when this error occurs.

Steven.Howes SSCertifiable Points: 6230 More actions · Answer 4

When you say "the same way." What exactly do you mean, how do the reports that work and the ones that don't differ?

lisa.randles Default port Points: 1448 More actions · Answer 5

Thank you for your replies. It took some time but we've found a workaround and MS believes it is a bug and they are going to investigate further.

The answer was found here:

========

http://connect.microsoft.com/SQLServer/feedback/details/357255/reporting-print-layout-error-index-out-of-bounds

Scenario

========

The report needed to be set up with each different "policy holder" begining on a new page of the report and the header for the "policy holder" should only be visible on the first page of their group of policies.

Issue

========

When trying to export report to PDF getting an error “Index was outside the bounds of the array”.

Cause

========

The hidden property for the outermost column group, i.e. PolicyHolder was set to “True”.

Resolution

========

Edited the report in BIDS, for the outermost column group, set the Visibility to "Show" and changed the Hidden field to “False” (which was previously set to True).

Workaround

========

The report designer used floating text boxes for column groupings instead of using the combined tablix column groupings. Apparently there is a limit if there is more than one page per grouping.

Hopefully this could help someone else. As I mentioned, this appears to be a bug and we will be notified if a fix is created. If so, I will post the fix here, also.