Where are expression exceptions logged in an RDL report?
SQL Server 2008 R2, Visual Studio 2008 + R2. When an exception occurs in a code module interpreted by the RDL Report Processor I see "#Error" in the cell as the returned value. I also see the exception in the Output window in VS when I preview the report. However once deployed, the report execution shows up in the log files but there is no indication of the exception (other than the #Error in the cell). Did I miss something? Shouldn't these exceptions be logged? If so, where? __________________________________________________________________ William Vaughn Mentor, Consultant, Trainer, MVP http://betav.com http://betav.com/blog/billva http://www.hitchhikerguides.net “Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)” Please click the Mark as Answer button if a post solves your problem!
October 29th, 2010 2:54pm

Hi William, Only show "#Error" in a report when an exception occurs is default behavior in SQL Server Reporting Services. Usually, I catch the exception in code, return the exception(use a string variable), and then display the exception in the report. Thanks, Jin ChenJin Chen - MSFT
Free Windows Admin Tool Kit Click here and download it now
November 1st, 2010 7:40am

Good tactic but this does not answer the question of why the errors are not logged--or if they are, where they are logged.__________________________________________________________________ William Vaughn Mentor, Consultant, Trainer, MVP http://betav.com http://betav.com/blog/billva http://www.hitchhikerguides.net Hitchhikers Guide to Visual Studio and SQL Server (7th Edition) Please click the Mark as Answer button if a post solves your problem!
November 1st, 2010 12:06pm

Hi William, The exception from a custom code or custom assembly is not logged. Personally, this may be due to that, the SQL Server Reporting Services(SSRS) will compile the custom code or assembly dynamically(.NET reflection), the compiled application is running in new thread other than the SSRS runtime. Here, I would like to suggest you to submit a wish at https://connect.microsoft.com/sqlserver. We can suggest to add the exception to the SSRS logs. Thanks, Jin ChenJin Chen - MSFT
Free Windows Admin Tool Kit Click here and download it now
November 2nd, 2010 2:33am

Mr. Chen's answer is simply wrong. After having done more research I have discovered that in order to see report code-generated exceptions one has to enable "verbose" logging in the config file as mentioned in http://support.microsoft.com/kb/2146315. This only makes sense. For SQL Server to be compliant with federal security regulations, all errors like this must be logged--they always have been. I would appreciate if Microsoft did not permit people who do not know the right answers from posting here. Now I have to go back and spend more hours redocumenting the actual behavior and re-checking the answers Mr. Chen has given in the past.__________________________________________________________________ William Vaughn Mentor, Consultant, Trainer, MVP http://betav.com http://betav.com/blog/billva http://www.hitchhikerguides.net Hitchhikers Guide to Visual Studio and SQL Server (7th Edition) Please click the Mark as Answer button if a post solves your problem!
November 3rd, 2010 2:32pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics