Muokkaa

Jaa

rsProcessingError - Reporting Services error

  • Artikkeli

Details

Category Value
Product Name SQL Server
Event ID rsProcessingError
Event Source Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources
Component Reporting Services
Message Text Errors occurred in report processing.

Explanation

One or more errors were encountered while publishing, processing, previewing locally, viewing from the report server, 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.

  • A filter definition specified two expressions that evaluated to data types that couldn't be compared.

  • An expression referenced a nonexisting field in the Fields collection.

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

  • An expression referenced a nonexisting 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 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.

User action

Find more information

Do one or more of the following actions:

  • If you're viewing the report from the report server or if you're 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're authoring a report in Report Designer and encounter this error when you preview the report, additional information is provided. The Error List window contains details about the issue.

  • If you're 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're viewing a report on the report server, and if you're 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're 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\MSRS12.MSSQLSERVER\Reporting Services\LogFiles\ReportServerService__datetimestamp.log. For more information, see Reporting Services log files and sources.

Failed to load expression host assembly

Custom assemblies must have strong name signing and the attribute AllowPartiallyTrustedCallers set. For more information, see Use custom assemblies with reports and Understand security policies.

A built-in global name does not exist

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 the name is spelled correctly. For more information, see Built-in collections in expressions (Report Builder and SSRS).

Parameter properties and null

A multivalue parameter can't be Null. For more information, see Report parameters (Report Builder and Report Designer).

Main report with subreport could not be processed

The same version of the Reporting Services report processor must process a report with subreports. When you upgrade reports to the current version of the report definition schema, the main report and the subreports might or might not be updated at the same time. If the version isn't compatible between a report and its subreports, the following message is displayed: "Subreport couldn't be processed."

Change either the main report or the subreports so that the same version of the report processor can process all the reports. For information about why a report fails to upgrade, see Upgrade reports.

Verify Function Calls are Visual Basic and Not SQL

You can use SQL functions in query text on a relational database. You can't 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 can't use SQL functions in an expression.

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

Cannot compare data types for a filter

In a filter equation, the filter expression that defines what to filter on and the filter value must be the same data type 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> can't be performed. Can't compare data of types <type> and <type>. 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 that has an error: <error string>.

For more information, see Filter, group, and sort data (Report Builder and SSRS).

Invalid or conflicting scope specification in an aggregate function call

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 name 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 isn't 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 function 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 Expression scope for totals, aggregates, and built-in collections (Report Builder and SSRS) and Built-in collections in expressions (Report Builder and SSRS).

Default dataset scope for a top level text box

Don't 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").

Related content