January 24, 2012 at 5:39 am
Hi All
Windows Server 2008
I ran a report yesterday and it worked fine, but since this morning when I run the report I keep getting error
"Operation is not valid due to the current state of the object"
When I run the report in BIDS it works fine and it deploys to report manager fine, but when it is ran it does not work.
Can anyone advise?
Thanks
R
January 28, 2012 at 8:07 pm
Server updates ran mid-January; reports failing to render were noted 2 days afterwards;
I have the same issue with a series of reports and have narrowed it to a set of report parameters of sizable string length on those reports. The error raised differs from the DEV server to the Production server with the Production server raising the same error as what's noted on this thread. Checking the Reporting Service Log Files, both conditions are attributed to rsInternalError.
I do not believe the issue is due to the parameter lengths themselves, but to some action taken by these query-type parameters that prevents the report from being rendered.
My team and I have tried backing out two .NET Framework updates (3.5 & 4) listed as potential causes for the issue by limiting the value of the httpCollectionKeys to 1000. This did not resolve the issue. Additionally, modifying the Web config file to include a new maximum key value in the app settings section and restarting the server did not prevent the reports from crashing on large parameter loads. This modification was backed out for its security risk.
We noticed that the reports are accessible on opening and that deselecting SELECT ALL and reducing the number of values in the report parameters allows the report to render successfully. We tried combinations to see if one parameter was the issue with nothing conclusively found.
Intriguingly, checking the Report Server database shows no rsInternalError status raised for these crashes -yet the limited-parameter successes are (e.g. Status = rsSuccess). In short, no failed attempts are being logged for these attempts. Yet, checking Reporting Services Log Files I can see the error being raised followed, most notably, by a maxhttpcollectionkeys exceeded event.
Lastly, the report designer is in the process of altering the parameters and setting the query to 1000 records to prevent the end user from experiencing the failed load. This is a strangled version of a report that once ran... a temporary fix.
May 7, 2012 at 7:44 am
Our solution required patching the web configuration files in both the Report Manager and Report Server -a solution that I'd overlooked while focusing only on the Report Manager.
This patching included the insertion of a MaxHttpCollectionKey value within the appSetting tag as described elsewhere. Report Server requires adding an appSettings element within the configuration tags.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply