Error Message

V-16-1-53006 Unable to connect to VCS engine securely

Unable to authenticate logged in user %USERNAME% of domain %DOMAIN% for host %HOSTNAME%


Problem Statement:


Resolution :

There are two approaches to resolve this issue.

=========================
APPROACH 1
=========================

Run the below commands to re-establish the trust to the root broker.

Note: To complete this procedure, you must be able to provide the name of the root broker. If you do not know the name of the root broker, run this command from another node in the cluster that is still able to authenticate successfully:

# cd "C:\Program Files\Veritas\cluster server\eat\bin"
# vssat showrootbroker

1. Run this command to re-establish the trust with the Root Broker:

# cd "C:\Program Files\Veritas\cluster server\eat\bin"
# vssat setuptrust --broker --securitylevel high

Press "y" when prompted for "y/n."

2. Save and close the cluster configuration with the following command:

# haconf -dump -makero

Note: You may receive a message stating the cluster is not writeable. This indicates the configuration was already closed.

3. Stop and restart the cluster engine (had.exe) on all nodes with the following command:

# hastop -all -force

4. Restart the cluster engine with the following command:

# hastart -all

5. Run the following command to check whether vssat is able to return credentials:

# vssat showalltrustedcreds

=========================
APPROACH 2
=========================

1) Unconfigure SSO using Unconfigure SSO for VCS on Windows platform 

2) Run the Veritas Cluster Configuration Wizard and configure SSO again to rebuild the authentication configuration.

V-16-1-53006 "Unable to connect to VCS engine securely" or "Unable to authenticate logged in user %USERNAME% of domain %DOMAIN% for host %HOSTNAME%" appears when trying to connect to Veritas Cluster Console for Windows

UMI: V-16-1-53006 ETrack: 1989616