Best Practices for Reporting Services Exception Handling

 

When developing Reporting Services applications, there are several methodologies you can use to eliminate or reduce the occurrence of exceptions. When exceptions do occur, provide clear and concise error messages to the user, and add adequate exception handling to prevent your applications from ending unexpectedly.

An application that sends requests to the Report Server Web service should do the following:

  • Avoid causing exceptions by preventing as many invalid requests as possible.

  • Catch exceptions and provide specific error-handling code whenever possible.

  • Deal with error cases that do not throw exceptions.

TopicDescription
Preventing Invalid RequestsDescribes techniques for preventing requests that are not valid from being sent to the report server.
Using Try and Catch BlocksDescribes how to further enhance the reliability of your application with try/catch blocks.
Handling Warnings and Cases That Do Not Cause ExceptionsExplains how to handle errors that do not result in an exception being thrown by Reporting Services.
Using the Detail Property to Handle Specific ErrorsExplains how to programmatically handle specific errors by using the Detail property of the SoapException object.

Detail Property
Introducing Exception Handling in Reporting Services
Reporting Services SoapException Class

Show: