This Knowledge Base article describes a known issue when having the EVault Remote Disaster Recovery for IIS Plug-in and the EVault Remote Disaster Recovery for SQL Server Plug-in on a machine that host IIS Server and SQL Server Reporting Services.
When EVault Remote Disaster Recovery is installed on a server that hosts IIS Server and SQL Server Reporting Services, and the SQL Server plug-in is installed before the IIS Server plug-in, the HTTP service doesn’t respond to stop commands generated by EVault Remote Disaster Recovery.
The HTTP service fails to stop when you click Stop Applications in the EVault Remote Disaster Recovery Management Client, or when a Switchover or Failover is performed. 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).
The HTTP service has a hidden dependency on the SQL Server Reporting Services and refuses to be stopped on demand as long as SQL Server Reporting Services is running.
ResolutionThere are two available solutions:
Uninstall EVault Remote Disaster Recovery for SQL Server.
Stop the EVault Remote Disaster Recovery Group (leave protected applications running).
Delete the SQLServer directory located in the
<EVault RDR installation folder>\R2\plugins
on the active server.
Start the EVault Remote Disaster Recovery Group.
Install the EVault Remote Disaster Recovery for SQL Server plug-in.
- Uninstall EVault Remote Disaster Recovery for SQL Server.
Option 2: Add the missing dependency between HTTP and SQL Server Reporting service:
- Open a command prompt.
Run the following command:
sc config ReportServer depend= http
Repeat the steps on the other server(s).
EVault Remote Disaster Recovery, all versions.
RDR-REFID-1869 — HTTP Service Fails to Start or Stop in Response to Neverfail Heartbeat on Servers Hosting IIS Server and SQL Server Reporting Services