Error Message

When attempting to start the service from an elevated command prompt, it may give the below possible errors:

C:\Users\administrator.test>net start vcscomm
A system error has occurred

C:\Users\administrator.test>net start vcscomm
System error 1 has occurred

C:\Users\administrator.test>net start vcscomm
Incorrect function

Checking the Windows System Event log would report the error below.

Log Name:   System
Source:     Service Control Manager
Event ID:   7023
Level:      Error
Description:
The Veritas VCSComm Startup service terminated with the following error: 
Incorrect function.

Further, the High Availability Engine (HAD) will fail and report the following error:

Log Name:   System
Source:     Service Control Manager
Event ID:   7001
Level:      Error
Description:
The Veritas High availability engine service depends on the Veritas VCSComm Startup service which failed to start because of the following error:
The operation completed successfully.

The issue can occur if:

1) CommStartup value is set to 0 at [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VCSComm\Parameters]

AND/OR

2) gabtab.txt from from %VCS_ROOT%\comms\gab and/or LLT files (llttab.txt and llthosts.txt) from %VCS_ROOT%\comms\llt path are missing or misconfigured. 

To begin addressing this issue, check the Application Event Log for any VCSComm specific errors.

Log Name:     Application
Source:       VCSComm
Event ID:     1
Level:        Error
Description:
VCSCOMM error: lltconfig -c: LLT lltconfig ERROR V-14-2-15069 cannot open configuration file C:\Program Files\Veritas\\Comms\LLT\llttab.txt

Next, follow the steps below to update the registry.

1. Check the registry key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VCSComm\Parameters]

2. Set the "CommStartup" value as 1 (Type: REG_DWORD)

3. Start the VCSComm service using the command: net start vcscomm

4. If the service is still unable to start, browse to %VCS_ROOT%\comms\llt and confirm the llttab.txt and llthosts.txt files exist.

NOTE:  The llthosts.txt file should list all nodes in the cluster

Below is a sample file for a cluster with 2 nodes: Server1 and Server2.

# This is program generated file, please do not edit.
0 SERVER1
1 SERVER2

5. Verify the llttab.txt is listing the appropriate MAC addresses/IP address(s) of the NIC configured for cluster heartbeat.

NOTE: To verify the MAC addresses listed are appropriate, open a command prompt and run the command: getmac -v

Compare the output to the MAC addresses listed in the command output with the values in the llttab.txt and confirm they are correct.

6.. To verify GAB configuration, browse to %VCS_ROOT%\comms\gab and confirm gabtab.txt exists.

7.  Check the file contents to ensure it has the entry for gabconfig -c -n x 

Where x is the number of nodes in the cluster and should match the number of nodes listed in the llthosts.txt file.

From the example above, the llthosts.txt file has 2 nodes (Server1 and Server2), hence the file should be shown as below.

#This is program generated file, please do not edit.
gabconfig -c -n 2

8. If all the above configuration is intact and VCSComm still fails to start, then launch the "Veritas Cluster Configuration Wizard" and reconfigure LLT links using the below steps: 

Launch VCW -> Select Domain-> Add all nodes -> Edit Existing Cluster -> Reconfigure-> Change Private Heartbeat links-> Unselect all LLT links for all nodes and select them again -> Reconfigure