Clever Geek Handbook

SSRS 2005 Exception Not Exposed

We are using SSRS 2005 SP1 and the latest Reportviewer items.
We have situations where some of the exceptions in the reporting framework are not subject to any exception handling.

A concrete example is that the SQL Server Reporting Services Windows service was stopped due to a VM issue. In this scenario, the report displays correctly, but when it is displayed to the user in the report viewer web control, the user sees the following message instead of the report:

An error has occurred during report processing. 

The Report Server Windows service 'ReportServer$MSSQL2005' is not
running. The service must be running to use Report Server.

The problem is that we are catching exceptions in every possible place: all methods outside the page, ReportViewer OnReportError

and application OnError

. In no way do we see or throw exceptions for the client code. Run in the debugger, an exception is thrown at runtime, but never raised to client client code.

Has anyone ever seen this?

0


source to share


2 answers


Thanks for your answer Bob. It is surprising and disappointing that SSRS eats these exceptions. We will probably avoid DLL hacking and try to figure out a way to monitor and warn from the internal SSRS logs.



+1


source


I saw something similar to this in Reporting Services 2008 where I was trying to catch certain types of exceptions. Nobody answered my question.



What I actually learned by asking this question might be helpful to you. I went and used reflector and poked around some DLLs. I'm looking for specific lines I've seen and found that Reporting Services seems to use its own exceptions and just throw lines away, so there isn't much you can do about such an issue other than hacking the DLL itself. This works differently than you would have to remove the strong name check and make it completely unreachable.

0


source






More articles:


All Articles