Hello all.
Since our recent upgrade to v12, users have been getting Script Errors when running SSRS reports. Specifically when they move among pages, or when using interactive sorting. The error messages look something like this:
Error: Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed.
URL: https://(our server)/TessituraWeb/ScriptResource.axd?d=Y1qsUug7ZRrvTxLsidrzd94oiRgvRudfVzI_EpH2dzi0bjgiP19pQwo-tfr2_YzdOmPhPEFLxAu1Xkt0PY_zYsbXP8BR_7Hfh-W7ybosjMH_jZIyVrwolAUxh8uEPQLOmMt1jOWU0wdGLz9ZKPV0gNwyP3rLRvzSL4J9qRLnZsAGmfFlzWLutwoKkbRsi3DD0&t=ca758f3
I navigated to the URL and found a lengthy bit of code that looks to be javascript, but I'm not equal to the task of interpreting it.
I suspect that it's a v12 issue because we only started having the issues after the upgrade, and not all of the reports were affected by the upgrade (no table-structure changes, etc.). Does anyone have any suggestions?
Thanks!
Nathan
We've experienced it also. Reports run fine at first, but if you leave the report window open for a few minutes, we start running into the errors. The problem happens with both canned and custom SSRS reports.
Us too. If anyone has had any luck with this, let us know. What I have done to work around it is just remove the pagination and have the results all display on one page for our custom reports by changing the interactive height of the report to 0.
Michael, This sounds like the following issue that Matt reported to us about a month ago:
A script parser error occurs if an SSRS report is run and the result window allowed to idle for 5 minutes or more and you attempt to navigate to any other pages in the report
This is currently under investigation by Development. Another work-around would be to save the report as a PDF and view it that way.
Dale
Thanks Dale. I'll let folks know they can try this workaround as well.
-Mike
Hi all,
Did anybody find anything new in regard to this discussion?
Thanks,
Matt
I haven't heard anything new, but we've taken to telling users to save the report as a PDF and navigate through that rather than navigating through the SSRS report in Tessitura. A work-around until there's a fix.
Edit: That's exactly what Dale suggested. So no, nothing new :)
Anything further on this? Is it being addressed in v12.5?
It has been another year -- any luck on a resolution to this error.?
For other people following this thread, see http://www.tessituranetwork.com/Community/forums/t/16251.aspx, for more details and potential solution to increase timeout.
Fernando