Showing results for 
Search instead for 
Did you mean: 

Understanding the V-16-1-10600 error message for Windows

Level 3

The hacli command communicates with the high availability daemon (HAD) process for any operations on objects such as clusters, systems, service groups, and resources. If the hacli command cannot communicate with the HAD process, the following error message occurs:

VCS ERROR V-16-1-10600 Cannot connect to VCS engine

This message is displayed when:

  • The cluster cannot start, because GAB cannot seed the cluster. As a result, HAD cannot start on a node. Veritas Cluster High Availability Engine (Had.exe) hangs in the Starting state.
    • GAB requires a minimum number of nodes be online to successfully seed the cluster. The minimum number of nodes is defined in the C:\Program Files\VERITAS\comms\gab\gabtab.txt file. When all nodes go down and one or more nodes do not come online, it is possible that the minimum node requirement is not reached.
  • Symantec Product Authentication Service (vxat or vxeat depending on version) is having problems even if HAD is in the Running state. 

To determine the cause of the error:

  1. Check if the HAD error message is displayed in the Application Event Viewer, as shown in the figure below:

Figure 1 - Command Prompt and Application Event Viewer.


  1. Check the Services Control Panel to see if the Veritas High Availability Engine Startup service is in the Starting state.
  2. Use one of the following commands to determine the state of the cluster:

C:\>hastatus -sum


C:\>hasys –state

To fix the error in the case where HAD cannot start:

  1. Check the gabtab.txt file for information that defines the seeding requirement: the minimum number of nodes for this cluster that must be available before HAD can start. HAD will not start until the cluster is seeded, even on only a subset of nodes. HAD must be running on a node for cluster operations to commence on that node.
  2. If the Veritas High Availability Engine Startup service is in the Starting state, you must manually seed GAB. Enter the following commands:

C:\>gabconfig -c –x    (This command configures GAB, if needed, and seeds a node or nodes, regardless of the minimum specified in the gabtab.txt file.)

C:\>hasys –state         (This command displays the current status of all cluster nodes that are online.)

Note: Starting with version 6.0.2,  the VCS Administrator’s Guide instructs users to use gabconfig -x to manually seed the cluster, while the VCS Administrator’s Guides for 6.0.1 and earlier versions specify using gabconfig -c -x  instead.

The -x option forces a subset of the required minimum nodes to seed. In a two node cluster that has only one node online, this seeds the one node and allows HAD to start on that node. Once HAD has started on one node, bringing the other node online allows it to join the cluster, as long as the private network communication between nodes is working.

If the configuration file is valid, the node should transition from LOCAL_BUILD to RUNNING. However, you must run the hasys –state command repeatedly to see if the status changes, as the command shows a snapshot of the current state.

In the case where Symantec Product Authentication Service is having issues, you need to fix and reconfigure the Symantec Product Authentication Service to resolve the HAD connectivity issue.

For more information, see:

 Symantec Storage Foundation and High Availability documentation for other releases and platforms can be found on the SORT website.


Employee Accredited Certified

Sophie, you should post information as a Blog or an Article.

Level 3

Thanks for your comment, Amol. I'm not very sure if I got your question right, but isn't this an article? :)

It resulted from the Social Media initiative that's been around a while. Diana Pham is the lead for it.