• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 842
  • Last Modified:

What would generate an unhandled exception in SSRS 2008r2

Hi Experts,

I have an SSRS report running under 2008r2 that, most of the time, works perfectly. It produces invoices or credit notes based on user parameter selection from Microsoft AX. However, on four occasions now, users have selected to report on invoices that have a) taken significantly longer to appear in preview in the browser than usual, b) given a "Print Error - An error occurred during printing. (0x80004005)" when printing and c) "Server Error in '/Reports' Application - An internal error occurred on the report server. See the error log for more details. (rsInternal Error)" when exporting to PDF.

Exports to other formats, such as Word or Excel - though not normally used for this report - tend to produce an empty document except for page headers and footers.

One thing I have noticed in common about the 4 invoices to fail is that they are all rental invoices and have more rental line items invoiced than others. The significance this may signal is that each invoice line of a rental type has a sub-report to show different rental periods at different day rates, whereas a non-rental line has a simple quantity, unit price and line amount within the main report.

So, does anyone know how to determine the root cause from the stack dump, or the appropriate section of the server log (which I can get if necessary), have any ideas what the cause may be, or think I may be on the right lines due to some limitation on the number of rendered sub reports from SSRS 2008r2.

I should add that, when I run the same report for the same invoice from within VS 2012 - my development environment - the invoice prints and exports perfectly. I'm thinking some known issue since fixed, which may have a work-around or patch / hot-fix, but I just can't seem to find one on TechNet.

I am based in the UK, and am about to stop work for the evening, so don't expect a response for the next 16 hours or so.
Thanks for looking
  • 3
2 Solutions
lcohanDatabase AnalystCommented:
In my opinion there are three separate issues:

a) taken significantly longer to appear in preview in the browser than usual,
either the SSRS server is under heavier load than usual or most likely they select a different range therefore lot more data to be processed/reported on. you can try use some of the SSRS performance improvements described below:

 b) given a "Print Error - An error occurred during printing. (0x80004005)" when printing - see if any applies to your problem:


c) "Server Error in '/Reports' Application - An internal error occurred on the report server.
SeeHearMarkAuthor Commented:
Hi and thanks for your reply. Lots to digest there, so will take a while to come back, but interesting that you think there are 3 separate issues!
SeeHearMarkAuthor Commented:
Hi again,

Firstly, some of the links you provided relating to performance issues gave me pointers to articles I had not come across before, and held some interesting information. As I said, there's a lot to digest there, so thanks for that.

Unfortunately, none of the links related to the printing error involved my circumstances, or anything close, so were not of any help. The pointers on the internal server error were, of course, very generic and did little other than remind me that I still had not had a copy of the SSRS server trace log from the system admin. Quite why they can't give me access, I really don't know, but that's another problem :)

Anyway, the server log did give me the internal error stack trace, pointing the finger at
and an InternalCatalogException index out of range. A quick search gave me 2008 Reporting Services:An internal error occurred on the report server while exporting to PDF only for one report which described precisely my issue. Removing the single HideDuplicates I had in the report, which happened to only be for rental invoices under some fairly rare circumstances resolved the error.

So, I guess I'll accept your response as the solution, if only to underline the importance of checking the SSRS server log!

SeeHearMarkAuthor Commented:
The expert provided a link to a generic article on getting more information from the SSRS server log. This in itself is not a solution, but directed me to finding further information that led to the article I quoted that provided the solution.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now