If the report server fails to process HTTP requests to it or delays the processing of such requests, the user experience with the report server will suffer. To avoid this, administrators should closely track HTTP requests to and responses from the report server and promptly capture error responses (if any). This is where the SQL SSRS HTTP Errors test helps!

This test captures and reports the rate of HTTP error responses from the report server, thus throwing light on the probable causes for failed/delayed request processing by the server.

Target of the test : A Microsoft SQL Server Reporting Services server

Agent deploying the test : A remote agent

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

Configurable parameters for the test
Parameters Description

Test period

How often should the test be executed


The host for which the test is to be configured.


The port at which the specified Host listens.


The name of a specific SQL Report server instance to be monitored. The default value of this parameter is “default”. However, if the Microsoft SQL Server hosting the SQL Reporting Server database uses named instances, then do the following:

  • Configure the Instance parameter with the name of the SQL Server instance that hosts the SQL Report Server database.
  • Do not change the default value of the Port parameter

Is Passive

If the value chosen is Yes, then the Microsoft SQL server (hosting the SQL report server database) under consideration is a passive server in a SQL cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable’ by the agent if the server is not up.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Http requests processing errors

Indicates the number of errors that occur per second during the processing of HTTP requests.


Ideally, the value of this measure should be 0.