rsProcessingError

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.

• A filter definition specified two expressions that evaluated to data types that could not be compared.

• An expression referenced a non-existing field in the Fields collection.

• An expression included an aggregate function call with an invalid or conflicting scope.

• 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 parameter that has the Nullable property set to False has detected a null value in the parameter.

• An expression for the Hidden property of a data region contains an error: Object reference not set to an instance of an object.

• An expression included an invalid function call or syntax error.

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 preview or publish the report, additional information is provided in the Error List window.

• If you are authoring a report in Report Designer Preview, look at the entire text of the error message. Additional information is provided in the expanded text.

• 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 file for ReportProcessingException. Log entries contain more information. The report server log file is typically located at <drive>:\Program Files\Microsoft SQL Server\MSSQL.N\Reporting Services\Logfiles\ReportServerService_datetimestamp.log.

Custom assemblies must have strong name signing and the attribute AllowPartiallyTrustedCallers set. For more information, see Using Custom Assemblies with Reports and Understanding Security Policies.

Check the spelling in expressions. Built-in globals, parameters, and field names are case-sensitive. In the expression causing the error, check that the name actually exists in the report and that it is spelled correctly. For more information, see Using Built-in Report and Aggregate Functions in Expressions (Reporting Services).

A multivalue parameter cannot be Null. For more information, see Creating Report Parameters and Setting Report Parameter Properties.

A report with subreports must be processed by the same version of the Reporting Services report processor. When upgrading reports to the SQL Server 2008 Reporting Services (SSRS) report definition schema, the main report and the subreports may or may not be updated at the same time. If the version is not compatible between a report and its subreports, the following message is displayed: "Subreport could not be processed." 

You must change either the main report or the subreports so that all the reports can be processed by the same version of the report processor. For information about why a report fails to upgrade, see Upgrading Reports.

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

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 expressions are valid.

In a filter equation, the filter expression that defines what to filter on and the filter value must be the same data type in order to be compared. If you see one of the following errors, modify the field expression or the filter value so that the data types match:

• The processing of <report item type> for the <report item name> cannot be performed. Cannot compare data of types <type> and <type>. Please check the data type returned by the <report item name>.

• Failed to evaluate the <property name>.

• Failed to evaluate the <property name>. It references a dataset field which has an error: <error string>.

For more information, see Filtering Data in a Report.

When you include aggregate function calls to an expression in a Tablix cell, the report processor evaluates the expression in the scope of the innermost groups to which the cell belongs.

You can also pass the name of a specific scope to an aggregate function. Scope can refer to the name of a dataset, a data region, or the name of a scope higher on the data hierarchy. This applies to the following messages:

• The <report item type> '<report item name>' has an invalid scope “<scope name>”. The scope must be the current scope, or contained within the current scope.

• The <property name> expression for the <report item type> '<report item name>' has a scope parameter that is not valid for an aggregate function. The scope parameter must be set to a string constant that is equal to either the name of a containing group, the name of a containing data region, or the name of a dataset.

For aggregate functions that calculate running totals (Previous, RunningValue, or RowNumber), you can specify a scope parameter that is either a row group name or a column group name, but not both. This applies to the following error message:

• Previous, RunningValue or RowNumber aggregate functions used in the data cells of the <report item type> '<report item name>' refer to grouping scopes in both the columns and rows of the <report item type>. The scope parameters of all Previous, RunningValue and RowNumber aggregate functions within a <report item type> can refer to row groupings or data column groupings, but not both.

For more information, see Calculating Totals and Other Aggregates (Reporting Services) and Using Built-in Report and Aggregate Functions in Expressions (Reporting Services).

Do not use a default scope for a text box added to the report design surface when the report has more than one dataset. Use an expression that includes the name of the dataset as the scope, and an aggregate function. For example, =First(Fields!FieldName.Value, "DataSet2").