Error Message

In System Event Log :

The Veritas VCSComm service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

In Application Event Log :

Event Type: Error
Event Source: VCSComm
Event Category: None
Event ID: 1

Description:
VCSCOMM error: VCSComm did not start because GAB or LLT was not configured successfully last time. Reset \registry\machine\system\CurrentControlSet\Services\VCSComm\Parameters\CommStartup value to 1 before starting VCSComm

After setting the registry value of VCSComm to 1, we try to start the service. It fails with the following error in Application Event Log :

The problem is with the path statement in Environment Variables getting longer than 2048 characters.

This was a known problem in version SFHA 5.1 and was fixed in subsequent CPs, but the problem seems to have recurred in version SFHA 6.0 with the latest patch CP14 applied.

Moving the Veritas entries OR VCSComm entries to the beginning of the path statement does not help.

We have to do the following :

1> Edit the environment variables. Create a backup of existing variables. Then edit the entries to make it shorter than 2048 characters. Ensure that Veritas entries are at the beginning.

2> Reboot the node. This will not start the vcscomm as GAB/LLT will not be configured properly.

3> Run the following commands :

net stop llt

net stop gab

net stop vcscomm (VCSComm wont be started anyways)

lltconfig -c

gabconfig -c

gabconfig -c -n x  ---> (x is number of nodes in the cluster)

4> Ensure that we have the llt/gab listings fine :

lltstat -n & lltstat -nvv (should show the node)

gabconfig -a (should show the ports now)

5> Run "net start vcscomm"

The service should startup fine now.