Has anyone found the answer to why an SSRS report will periodically crash when paging up or down. The error is usually
Sys.WebForms. PageRequestManagerParseErrorException.
Etc
It is annoying enough that the Page Up/Page Down keys can't be used but it adds insult to injury when it crashes like this.
Thanks
That's what happens now. What would help is if they were the same. THen you could print ONLY the pages you needed. Now we can print a page and find the data needed is not there.
Ultimately we need a report that can be interactive and not crash.
Remember that you can set the interactive page settings to be different from the actual print page settings.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Leslie McKinley Sent: Monday, June 27, 2016 10:54 AM To: Brian W. Grundstrom Subject: Re: [Tessitura Technical Forum] SSRS Page error
Thanks for the info. The problem of course is users using the report actively, drilling down on records etc. This idle problem means users cannot use the system to assist with working within the system. If print out are always needed. Since some reports can be rather extensive and it gets to be a waste of paper.
Another pet peeve is the page count is never "real".
From: Fernando Margueirat <bounce-fernandomargueirat4910@tessituranetwork.com> Sent: Monday, June 27, 2016 10:29 AM To: McKinley, Leslie Subject: Re: [Tessitura Technical Forum] SSRS Page error
Leslie
This is a simplified description of what's happening. When you run a report with multiple pages, the report server sends you the first page and stores the data for the other report pages in its cache. When you click next page, your client is telling report server "send me the next page of the report you have cached with ID xxxxxxx". But if you take too long to go to the next page, the report server already timed-out the session and drops the cached information. That's the error you are getting.
I haven't been able to find a way to increase the time-out, so the only "solution" I found is to be sure you go through the pages before it times out, or export the report to PDF or other offline format.
Fernando
From: Leslie McKinley <bounce-lesliemckinley4321@tessituranetwork.com> Sent: 6/26/2016 3:44:10 PM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
You can try saving the report as a MHTML file, it keeps some of the dynamics aspect of the SSRS reports.
There seems to be an entry in t_defaults (SSRS_TIMEOUT) that declares the timeout for SSRS reports. It didn't worked when I changed it, but it might require a restart.