Configuration of SSRSStatTest

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.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host for which the test is to be configured has to be specified.

• In the PORT text box, enter the port number at which the target host being monitored listens.

• Specify the name of a specific SQL Report server instance that is to be monitored in the INSTANCE text box. 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.

• If the value for the ISPASSIVE parameter is chosen as 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.

• In some Windows networks, NTLM (NT LAN Manager) may be enabled. NTLM is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. NTLM version 2 NTLMv2 was concocted to address the security issues present in NTLM. By default, the IS NTLMv2 flag is set to No, indicating that NTLMv2 is not enabled by default on the target Microsoft SQL server hosting the SSIS database. Set this flag to Yes if NTLMv2 is enabled on that Microsoft SQL server.

• This test queries the report server database to pull details related to the status of the report requests. For this, the test needs to connect to the report server database. To enable this connection, enter the IP address of the report server database against the Report Server Database IP parameter, enter the port at which the report server database listens against the Report Server Database Port parameter, and enter the name of the report server database against the Report Server Database Name parameter. To determine the database IP, port, and name, refer to Monitoring the Microsoft SQL Report Server document.

• To run queries on the report server database, the test requires to connect to the report server database as a user with SELECT permissions to the ExecutionLog, Catalog, runningjobs, and users tables of that database. For this purpose, you can create a special user on the Microsoft SQL server, grant the required monitoring privileges to that user, and configure the User and Password parameters with the credentials of that user. To know how to create such a user, refer to Monitoring the Microsoft SQL Report Server document.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• By default, none is displayed in the DOMAIN text box. If the ‘SQL server and Windows’ authentication has been enabled for the server being monitored, then the Domain can continue to be none. On the other hand, if ‘Windows only’ authentication has been enabled, then, in the Domain text box, specify the Windows domain in which the SSIS database that this test connects to exists. Also, in such a case, the User name and Password that you provide should be that of a user authorized to access the Microsoft SQL server hosting the SSIS database of interest.

• By default, the DD Row Count parameter is set to 10. This implies that by default the detailed diagnosis of the test reports the top-10 reports in terms of the running time of the reports. If you want detailed diagnosis to include more or less number of reports, then change the value of this parameter.

• To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.