Best practices for Reporting Services exception management

When you develop 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:

• 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 don't throw exceptions.

In this section

Article	Description
Prevent invalid requests	Describes techniques for preventing requests that aren't valid from being sent to the report server.
Use try and catch blocks	Describes how to further enhance the reliability of your application with try/catch blocks.
Handle warnings and cases that do not cause exceptions	Explains how to handle errors that don't result in an exception occurring Reporting Services.
Use the Detail property to handle specific errors	Explains how to programmatically handle specific errors by using the Detail property of the SoapException object.

Related content

Detail property
Introduction to exception management in Reporting Services
Reporting Services SoapException class