The following can be seen in the wac_A.log located at %VCS_HOME%/log path :
VCS INFO V-16-3-18516 Attempting to connect to VCS engine on
VCS INFO V-16-3-18001 connector connected to VCS on
VCS NOTICE V-16-3-18511 all heartbeats to cluster
VCS ERROR V-16-3-18207 Cannot start WAN Heartbeat agent Icmp
The following can be seen in the Windows Application event logs :
Event ID: 10590
Source: Wac
Description:
Cannot start D:\Program Files\veritas\Cluster Server\bin\hb\WANHBDriver.exe Icmp -server 14155 193
The error code:193 from the Application event can be translated as below as explained at https://learn.microsoft.com/en-US/windows/win32/debug/system-error-codes--0-499-
Error Code: 193 (0xC1)
ERROR_BAD_EXE_FORMAT
%1 is not a valid Win32 application.
Based on that, the issue can occur if there exists a file or another folder with the name Program or Programs or ProgramFile or anything similar in the same location where Veritas is installed.
Example: Assuming Veritas Infoscale is installed at D:\Program Files\Veritas path, when the CreateProcess WIN API tries to launch the WANHBDriver.exe and if there exists a file/folder as D:\Program at D:\ drive, it conflicts with D:\Program Files path and keeps giving priority to D:\Program path resulting in a failure to create any process for WANHBDriver.exe
To address this issue, from an elevated command prompt, run the command below from the Veritas Cluster installation path:
D:\Program Files\veritas\Cluster Server\bin\hb\>WANHBDriver.exe Icmp -server 14155
This would spawn the WANHBDriver.exe manually and allow the Remote Cluster status to be updated to Running state.
NOTE: To fix the folder issue, identify the file or folder with a similar name as Program or Programs or Program File and either rename it OR move it to another location.