R2 Page breaks
Hi,
I just upgraded to Reporting Services 2008 R2, and upgraded my project.
My report no longer worked. It gave the following error:
"An error occurred during local report processing. Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index"
My report has the following structure:
Report
Body
Tablix
Rectangle 1
Rectangle 2
Rectangle 3
By chance, I discovered what was causing the error. When I took off the page break from Rectangle 3, the report started working again.
Can anyone help here? I need the page breaks in the report.
Regards,
Fergus
May 10th, 2010 6:07pm
Try adding page break in top most data region in your rectangle. If it is table, then do the following
1. select Advanced view from column group
2. Select first static group and in the properties pane, select repeatonpage = true.
Free Windows Admin Tool Kit Click here and download it now
May 11th, 2010 12:17am
Thanks for your response.
I'm not sure I understand you. I have a list, containing 2 rectangles. I wan't a break between the rectangles.
Regards,Fergus
May 11th, 2010 12:57pm
sorry for not being clear. What do you have inside rectangles?...any other data region or just text boxes?
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2010 12:18am
Textboxes and subreports.
Regards,Fergus
May 12th, 2010 2:12am
Can anyone replicate this issue?
Add a list to a report, and inside the cell place a rectangle which contains 2 rectangles. This report will run fine.
Adding a page break to either of the rectangles inside the main rectangle results in the error.
Regards,Fergus
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2010 3:27pm
Hi,
I've found the solution.
My tablix had keeptogether = true. Adding the page break within the tablix seems to conflict with this, but doesn't reset it. I removed keeptogether = true, and the report started working.
Regards,Fergus
May 17th, 2010 3:48pm
This solution worked for me as well, however my table was nested inside a List that had the KeepTogether=True property. When I changed that to false, the index error no longer occurs. Thanks Fergus!
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2011 3:40pm
This work around resolved the issue for us as well.
May 3rd, 2011 8:42am