Reporting Print Layout error: index out of bounds - by Webfred

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 357255 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 7/22/2008 5:39:58 AM
Access Restriction Public

Description

Hidden column of a table causes error index out of bounds:
An error occured during local report processing.
Index was outside the bounds of the array.

Making the column visible, then the error is gone.
Sign in to post a comment.
Posted by Microsoft on 8/1/2008 at 10:40 AM
Hello, I'm classifying this as 'Not Repro' because we don't have enough information to begin to investigate. Please reactivate if you attach the requested files.

Best regards,
Chris B.
SQL Server Reporting Services
Posted by Microsoft on 7/24/2008 at 4:19 PM
Also, can you please attach a report that we can run in-house (or a database bak that we can use with the report you attached)? We need to be able to run the report in-house to investigate. Also, we still need the report server log file with the callstack.

Thanks,
Chris B.
Posted by Microsoft on 7/24/2008 at 9:50 AM
Thanks, can you please also attach your report server log file that shows the call stack for this error?
Posted by Webfred on 7/23/2008 at 1:59 AM
Now I have completed the Text for Steps to Reproduce and i have uploaded the rdl-file.
Remark: Built-in Fields causes that error only in footer and header but not in body.
Best Regards
Webfred
Posted by Microsoft on 7/22/2008 at 4:13 PM
I'm going to resolve this as Not Repro until we receive the requested info from you. We'll look at it as soon as we receive it.

Thanks,
Chris B.
Posted by Microsoft on 7/22/2008 at 9:09 AM
Hello,

Thanks for reporting this. In order to investigate we need some more information from you:

1) Please attach your RDL file
2) Please also include your report server log file so that we can see the call stack for this exception.

Thanks,
Chris B.
SQL Server Reporting Services