eG Monitoring
 

Measures reported by SSRSStatTest

Capturing report failures on-the-fly and rapidly troubleshooting them can go a long way in ensuring that user experience with the report server is above-par at all times. This can be achieved using the SSRSStatTest test!

This test tracks the status of reports processed by the report server for each user, and promptly captures report failures, cancellations, and time-outs per user. Additionally, the test deduces why the reports failed, and reveals the count of reports that failed due to each reason. This way, the test points to the users who experienced the maximum number of report failures, and also enables administrators to instantly determine the cause of the failures. Detailed diagnostics of the test also point you to the precise reports that failed / were cancelled / have timed out, thus significantly reducing the troubleshooting cycle for administrators.

Outputs of the test : One set of results for each user of the report server being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Sucess_rprts Indicates the number of reports that were completed successfully by this user during the last measure period. Number  
Cancelled_rprt Indicates the number of reports of this user that were cancelled during the last measurement period. Number Ideally, the value of this measure should be 0. If this measure reports a non-zero value, then use the detailed diagnosis of this measure to identify the top-10 cancelled reports in terms of their running duration.
Param_error_rprt Indicates the number of reports of this user that failed in the last measure period due to parameter errors. Number Ideally, the value of this measure should be 0. If this measure reports a non-zero value, then use the detailed diagnosis of this measure to identify the top-10 reports in terms of their running duration, which had parameter errors.
Timeout_expired Indicates the count of reports of this user that timed out during the last measure period. Number If the value of this measure is very high, you may want to consider increasing the time-out setting for reports.

Report servers support three time-out values:

  • An embedded dataset query timeout value is the number of seconds that the report server waits for a response from the database. This value is defined in a report.

  • A shared dataset query time- out value is the number of seconds that the report server waits for a response from the database. This value is part of the shared dataset definition and can be changed when you manage the shared dataset on the report server.

  • A report execution time-out value is the maximum number of seconds that report processing can continue before it is stopped. This value is defined at the system level. You can vary this setting for individual reports

Most time-out errors occur during query processing. If you are encountering timeout errors, try increasing the query timeout value. Make sure to adjust the report execution time-out value so that it is larger than the query time-out. The time period should be sufficient to complete both query and report processing.

You can use the detailed diagnosis of this this test to know which reports of a user timed-out.
Param_val_notset Indicates the number of reports of this user that failed in the last measurement period, because certain parameter values were missing. Number Ideally, the value of this measure should be 0. If this measure reports a non-zero value, then use the detailed diagnosis of this measure to identify the top-10 reports in terms of their running duration, which were missing parameter values.
Internal_error_rprt Indicates the number of reports of this user that failed due to internal report server issues. Number Internal errors are uncommon. If you get this error, more information is available in report server trace logs. In addition, if you are running as local administrator on the same computer on which the error occurs, you can view the call stack for more information.

To determine the specific cause for this message, review the report server log files, which are located at \Microsoft SQL Server\MSRS12.\Reporting Services\LogFiles.

You can also use the detailed diagnosis of this measure to view the top-10 reports in terms of running duration, which failed due to internal report server errors.
Render_err_rprt Indicates the number of reports of this user that failed in the last measurement period because of errors in rendering. Number This error can occur if Reporting Services cannot render or export the report.

The table below discusses the probable causes for rendering errors and how to resolve them:

Use the detailed diagnosis of this measure to view the top-10 reports (in terms of running time) that failed due to rendering errors.

Probable Cause Possible Solution
Specified RDL page size is not valid Specify a valid RDL page size and then try to generate the report again.
An unsupported unit type is specified Valid unit types are cm, in, mm, pc, and pt. Specify a valid unit type and then try again.
A negative measurement for the page size, for example -5 cm, is specified Specify a positive number for the page size and then try again.
Measurement for the page size is outside of the valid page margin size Specify a measurement for the page size that is within the valid page margin sizes.
A color specified in the RDL is not valid Choose a color supported by RDL and then try again.
An action label is specified and it is not valid Specify a valid action label for each action.
An incorrect style value for the data type is specified. Specify a correct value and then try again.
The border style specified is not valid Specify a supported border style and then try again.
The specified mime type for an image report item is not valid Specify a supported mime type for the report item and then try again.
Running_report Indicates the number of reports of this user that are currently running. Number Using the detailed diagnosis of this measure, you can view the top-10 running reports (in terms of running duration). In the process, you can instantly identify the long-running reports.