Installing a New SQL Instance Post Heartbeat Install Generates Warnings Repeatedly

Follow

Summary

This Knowledgebase article provides information about the occurrence of warnings generated repeatedly by Neverfail Heartbeat when a new SQL instance is installed post Neverfail Heartbeat installation.


More Information

Symptoms

When installing a new SQL instance post Neverfail Heartbeat installation, on one machine only, the following warnings are repeatedly generated:

Error: [Unable to protect <servicename> because <servicename> was not found on
computer]

Warning: [Could not find service: <servicename>]

Warning: [Exception setting recovery actions for service: Object reference
not set to an instance of an object]

Cause

These errors are generated from the passive server, which does not have the instances present to
be protected.

Resolution

To correct this situation, follow the steps below:

  1. Shutdown Neverfail Heartbeat and leave the protected applications running.
  2. Restart the Secondary server.
  3. Restart Neverfail Heartbeat.

Note: To protect a n ew SQL instance, the new instance must be installed on the Secondary server as well. For details on this operation please see section "Installing a New Instance of SQL Server" in the Knowledgebase article #1331 - 'Neverfail for SQL Server Plug-in - Online Help'.


Applies To

Neverfail for SQL Server Plug-in V201.5.1 and Later


Related Information

None

KBID-1454

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.