After successfully completing the installation of Command Central Storage Management Server, connection to the Web server and logging in return the error "CHM: Failed to connect - cannot find cached credentials for [vx:HAL/CCStorage] DM: Host not found AM: Failed to connect".

Article:TECH50704  |  Created: 2007-01-01  |  Updated: 2008-01-02  |  Article URL http://www.symantec.com/docs/TECH50704
Article Type
Technical Solution

Product(s)

Environment

Issue



After successfully completing the installation of Command Central Storage Management Server, connection to the Web server and logging in return the error "CHM: Failed to connect - cannot find cached credentials for [vx:HAL/CCStorage] DM: Host not found AM: Failed to connect".

Error



CHM: Failed to connect-cannot find cached credentials for [vx:HAL/CCStorage]
DM: Host not found
AM: Failed to connect - cannot find cached credentials for [vx:HAL/CCStorage] DM: Host not found AM: Failed to connect

Solution



The issue
After successfully completing the installation of the CommandCentral Storage Management Server connection to the Web server and logging in, this error message is returned CHM: Failed to connect - cannot find cached credentials for [vx:HAL/CCStorage] DM: Host not found AM: Failed to connect.  A license error also appears in the middle of the Managing Summary View.  

Cause:

These errors occur when the Command Central Storage Management Server is not correctly installed on a domain or is a member of a domain. The following is an example of the error seen on either Windows or Solaris CommandCentral Storage Management Server platforms:

 

Workaround

Follow these steps to correct this issue after the software installation is complete and it is determined the issue exists:

Note: This procedure is written for Solaris and Windows operating system platforms only.  The procedure steps assume that CommandCentral Storage is installed on the OS platform in the default locations and that the administrator running the commands is logged in as root for Solaris, or Administrator for Windows.

1.  Run the vssat command to determine what the correct fully qualified domain name (FQDN) should be:

Windows:  

C:\Program Files\VERITAS\Security\Authentication\bin\vssat.exe

Solaris:  /opt/VRTSat/bin/vssat

C:\> Program Files\VERITAS\Security\Authentication\bin\vssat showcred

Many credentials are returned at this point. Following is some of the output.  Of specific interest is the "Domain Name" information returned as follows:

*************************************
User Name:      broker
Domain Name:    root@hotbox
Domain Type:    vx
Issued By:      /CN=root/OU=root@hotbox/O=vx
Issued To:      /CN=broker/OU=root@hotbox/O=vx
Friendly Name:
Serial Number:  00000001
Root Credential:        0
Trusted Credential:     0
Expiry Interval Jan 28 20:36:18 2015 GMT
Group Information:
Group Count:    0
Certificate Hash        8f71f7ad970c9c99737bf4ea3525cd65a8076043

*************************************

Notice that the root broker in the example above thinks the FQDN is "hotbox".  This example is not on a domain so the host Network Interface Card (NIC) name is also the FQDN.

2.  Edit the file DATA_SERVERS.CFG and modify entries to match the FQDN indicated by running vssat as follows:

The file locations and commands are:

Windows:  C:\Program Files\VERITAS\CommandCentral Storage Data\Conf\Web Engine\DATA_SERVERS.CFG

Solaris:      #  /var/VRTSccs/conf/VRTSccstw/DATA_SERVERS.CFG

[hotbox]
config_file_version=1.1
ccstor_db_port=2994
ccstor_db_user=ccstor_RO
ccstor_db_pass=-73_79_-11_31_82_-52_30_-57_:-91_88_-89_86_-53_-48_-112_-52_
ccstor_read_write_user=ccstor
ccstor_read_write_pass=14_-7_15_-103_-90_-29_7_-48_:-23_-56_-102_-23_88_102_87_-90_
am_port=5431
dm_host=hotbox.domain_name.com
dm_db_port=2994
dm_db_user=ccstor
dm_db_pass=120_-72_70_74_93_-84_-76_-32_:-32_34_25_51_-72_38_124_-64_
disabled=false
db_name=ccstor
dm_db_name=ccstorDM
ab_host=hotbox.domain_name.com
ab_port=1556
at_user=CCStorage
at_domain=HAL
at_domain_type=vx

In the example above, the "dm_host" and "ab_host" entries are defined to be "hotbox.domain_name.com".  These entries are incorrect because they do not match the FQDN provided in step 1 (above).  To correct the issue, change these two entries to match the vssat output FQDN in step 1 above which is just "hotbox".  Make the changes to DATA_SERVERS.CFG as follows:

====================
was:  

dm_host=hotbox.domain_name.com
...
ab_host=hotbox.domain_name.com

should be:

dm_host=hotbox
...
ab_host=hotbox

====================

After making the changes in the DATA_SERVERS.CFG file, save these changes and close the file.

3.  Stop and restart all services shown below as done from the specific operating system platform command line:  

These commands include requirements when both the Object Module (OM)  and Data Module (DM) are installed on the Command Central Storage Management Server.

Windows:

To stop all Command Central Storage Services, run the following commands from the command line in order they appear as follows::

C:\  net stop VRTSccsweb
C:\  net stop VRTShal
C:\ net stop vxtrapd
C:\ net stop vxsicld
C:\ net stop vximporterd
C:\ net stop dmexplorer
C:\ net stop vxamccs
C:\ net stop vxasd
C:\ net stop VRTScclogin
C:\ net stop ASANYs_VERITAS_DBMS3_HOTBOX      (where "HOTBOX" is the NIC name of the Management Server Host)

To start the Command Central Storage services , run the following commands in the order that they appear:

C:\ net start ASANYs_VERITAS_DBMS3_HOTBOX      (where "HOTBOX" is the NIC name of the Management Server Host)
C:\ net start VRTScclogin
C:\ net start vxasd
C:\ net start vxamccs
C:\ net start dmexplorer
C:\ net start vximporterd
C:\ net start vxsicld
C:\ net start vxtrapd
C:\  net start VRTShal
C:\  net start VRTSccsweb

Solaris:

#  /opt/VRTS/bin/vxccstorweb stop
#  /opt/VRTS/bin/vxccs stop -force

To restart Command Central Storage, the commands follow in reverse order:

#  /opt/VRTS/bin/vxccs start
#  /opt/VRTS/bin/vxccstorweb start

4.  Using a new browser session, connect to the Management Server and log in as "admin".  The WebGUI should now connect to the other processes without displaying the previous errors.

Note: If stopping and starting all the services does not correct the original issue, reboot the Management Server hardware platform and try to connect with a fresh browser again.




Supplemental Materials

SourceETrack
Value962791
DescriptionSymantec: Installation and configuration failure in a non-existent Domain or hostname incorrectly configured on a valid Domain

Legacy ID



287302


Article URL http://www.symantec.com/docs/TECH50704


Terms of use for this information are found in Legal Notices