Post reply

Getting "Index was outside the bounds of the array" for Cached Reports

  • May 1, 2005 at 5:07 pm

    #110124

    Hi ALL,

    I have a published a few Reports with drill down features and the reports work fine. The only thing is that the Data is large and it takes a while to process the data even to use the drill down feature.

    Am opting to use 60 minutes cached report. The first run works well but with the subsequent runs am getting a Reporting Services Error with the message

    "An error has occurred during report processing. (rsProcessingAborted) Get Online Help

    Index was outside the bounds of the array."

    I really need assistance on this. Many thanks to those who help.....

    Cheers

     

  • May 4, 2005 at 8:00 am

    This was removed by the editor as SPAM

  • May 4, 2005 at 11:45 pm

    #556989

    Try checking your event viewer: application and system logs.

    Felix.

  • October 28, 2005 at 7:05 am

    #600885

    For Cached reports, credentials need to be stored within report, otherwise, you receive this error message. You didn't receive any error for the first time because report is not rendered from Cached copy, but for the subsequent runs it rendered from the cached copy. All you need to do is to store credentials within report.

    One more wired thing, global variable User!UserID should not be there in header or footer, its ok if its in report body

  • January 19, 2007 at 3:21 am

    #684217

    Its a bit late in the day after this was posted, but I had the same problem and found this post. I subsequently ound the solution which is to clear the cache by deleting the rdl.data file for the report in question.

    Regards

    Carolyn

     

     

    Facts are stubborn things, but statistics are more pliable - Mark Twain
    Carolyn
    SQLServerSpecialists[/url]

  • February 17, 2009 at 6:52 am

    #945150

    Hi,

    deleting the rdl.data file worked for me too!

    Thanks a lot!

    Romina

  • August 19, 2011 at 5:14 am

    #1370634

    Hi..... The best solution for this is to refresh the page and check for the report. It really works.

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

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