I have a asp.net web app using the standard ReportViewer control.
Among other things we have reports that are essentially a raw data dump, a single default line of fields intended for export to Excel.
One of our users is trying to run one of these reports and the return is over 1900 pages. He reports that the export screen crashed with a message stating '100 is unexpected token'.
I am aware of that forum entry (http://forums.asp.net/t/1374211.aspx) that suggests restarting the SSRS service but in general is there any other way to deal with this situation?
(Or should I just tell the users to stop generating such huge reports?)
----------
Late breaking news: It appears we can side-step this problem by exporting to CSV rather than Excel. The exported file was about 42 meg.
Firstly, 1900 pages is far too large of a Report to be generating (in my opinion).
You might consider adding some filtering functionality to the Reports that might require the user to define a more specific range of Dates or filtering by certain field to hopefully narrow the size of the results that they are currently getting.
Another option would be to consider using a different method of outputting the results or considering refactoring the code that you are currently using to output the files that might be more efficient (as you mentioned using CSV as opposed to a proprietary
format like Excel).
Member
27 Points
424 Posts
When is a report too 'large'?
Jan 27, 2014 10:01 AM|bchernick|LINK
Just looking for some general feedback.
I have a asp.net web app using the standard ReportViewer control.
Among other things we have reports that are essentially a raw data dump, a single default line of fields intended for export to Excel.
One of our users is trying to run one of these reports and the return is over 1900 pages. He reports that the export screen crashed with a message stating '100 is unexpected token'.
I am aware of that forum entry (http://forums.asp.net/t/1374211.aspx) that suggests restarting the SSRS service but in general is there any other way to deal with this situation?
(Or should I just tell the users to stop generating such huge reports?)
----------
Late breaking news: It appears we can side-step this problem by exporting to CSV rather than Excel. The exported file was about 42 meg.
ssrs reportviewer error export
All-Star
113010 Points
18360 Posts
MVP
Re: When is a report too 'large'?
Jan 27, 2014 01:25 PM|Rion Williams|LINK
Firstly, 1900 pages is far too large of a Report to be generating (in my opinion).
You might consider adding some filtering functionality to the Reports that might require the user to define a more specific range of Dates or filtering by certain field to hopefully narrow the size of the results that they are currently getting.
Another option would be to consider using a different method of outputting the results or considering refactoring the code that you are currently using to output the files that might be more efficient (as you mentioned using CSV as opposed to a proprietary format like Excel).
ssrs reportviewer error export