rsProcessingError

New: 17 July 2006

Details

Explanation

One or more errors were encountered while publishing, processing, or creating a subscription for a report. This error message indicates at least one error was detected.

Possible Causes

Possible causes include:

• A processing error occurred on the report server.
• A processing error occurred during local report processing when previewing a report.
• A group expression evaluated to an incorrect data type.
• An expression referenced a non-existing field in the Fields collection.
• An expression referenced a non-existing parameter in the report parameters collection.
• A custom assembly or a Reporting Services assembly that was incorrectly deployed failed to load.
• A filter expression evaluated to an incorrect data type.
• A parameter that has the Nullable property set to False has detected a null value in the parameter.
• A hidden expression for a data region contains an error: Object reference not set to an instance of an object.

User Action

Finding More Information

Do one or more of the following actions:

• If you are viewing the report from the report server or if you are viewing the report as a subscription, look at the entire text of the error message. Additional information is provided in the expanded text.
• If you are authoring a report in Report Designer, and see this error when you process or publish the report, additional information is provided in the Error List window.
• If you are viewing a report on the report server, and if you are running as local administrator on the report server, you can view the call stack if you right-click the page and select View Source. Additional information is provided in the call stack.
• If you are running as local administrator on the report server, search the log for the token that appears in parentheses just after the message "An error has occurred during report processing, for example, rsProcessingAborted." Log entries contain more information. The report server log file is typically located at <installdrive>:\Program Files\Microsoft SQL Server\MSSQL.N\Reporting Services\Logfiles\ReportServer_datetimestamp.log.

Failed to Load Expression Host Assembly

Custom assemblies need to have strong name signing and the attribute AllowPartiallyTrustedCallers set.

A Non-existing Parameter or Field

Check your spelling: parameter names and field names are case-sensitive. Check that the parameter or field being referenced in the expression actually exists and is spelled correctly.

Parameter Properties and Null

A multivalue parameter cannot be Null.

Verify Function Calls are Visual Basic and Not SQL

You can use SQL functions in query text on a relational database. You cannot use Visual Basic functions in a query.

In Reporting Services, expressions can use Visual Basic functions, System.Math or System.String functions, fully qualified .NET Framework functions, or custom functions that you provide in custom code or a custom assembly. You cannot use SQL functions in an expression.

Verify that the function calls made in the query and in the expression are valid.

See Also

Other Resources

Creating Expressions in Reporting Services
Using Report Functions in Expressions (Reporting Services)
Expression Examples in Reporting Services
Defining Report Datasets
Using Parameters to Control Report Data
Using Parameters in Expressions
Working With Fields in a Report Dataset
Using Custom Code References in Expressions (Reporting Services)
Debugging and Publishing Reports

Help and Information

Getting SQL Server 2005 Assistance