HTTP Service Fails to Start or Stop in Response to Neverfail Heartbeat on Servers Hosting IIS Server and SQL Server Reporting Services

Follow

Summary

This Knowledge base article describes a known issue when installing the Neverfail for IIS Plug-in on a machine that also hosts SQL Server Reporting Services, but does not have the Neverfail SQL Server Plug-in installed.


More Information

When Neverfail Heartbeat is installed on a server that hosts IIS Server and SQL Server Reporting Services, but only the IIS Server Plug-in is installed, the HTTP service fails to respond to start and stop commands generated by Neverfail Heartbeat.

Symptoms

Clicking Start or Stop Applications in the Neverfail Heartbeat Management Client fails to start or stop the HTTP service. The following error is displayed:

[ServiceAgent]: Error trying to start service HTTP. Please see the log for more information.

Also a number of warnings appear, such as:

Trying to stop service HTTP [try 1]: Time out has expired and the operation has not been completed. (Timeout).

Cause

The HTTP service has a hidden dependency on the SQL Server Reporting Services and cannot be stopped or started on demand as long as SQL Server Reporting Services is running.

Resolution

There are four available solutions:

  1. Install the SQL Server Plug-in.  (A license for this Plug-in is required.)
  2. Add the SQL Server Reporting Services service to the protected set through the Neverfail Heartbeat Management Client.

    NOTE: The SQL Server Reporting Services (REPORTSERVER) service must be running before you can add it to the protected set.
    1. In V6.0 and more recent, open the Applications : Services screen, right click REPORTSERVER in the list of services, and select Add... from the context menu. The Add Service dialog appears. Click OK to add the service with default settings.
    2. In v5.5 and earlier, click Application on the left navigation panel, select the Services tab in the panel to the right, and click Add... The Add Service dialog appears. Select REPORTSERVER from the Name: drop-down list. Click OK to add the service with default settings.
  3. If the service is not in use, stop and set the SQL Server Reporting Services service to manual.
  4. Add the missing dependency between HTTP and SQL Server Reporting service:
    1. Open a command prompt
    2. Run the following command:

      sc config ReportServer depend= http

    3. Repeat the steps on the other server(s)

Applies To

Neverfail Heartbeat, all versions.


Related Information

Knowledgebase Article #1870 HTTP Service Fails to Stop in Response to Neverfail Heartbeat on Servers Hosting IIS Server and SQL Server Reporting Services

KBID-1869

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.