ANS2619S using the Tivoli Storage Manager web client on Sun Solaris

ANS2619S using the Tivoli Storage Manager web client on Sun Solaris

Problem(Abstract)
A file restore with the web client on Sun Solaris 64 bit system may produce the following error in the web client java applet window :
ANS2619S The client acceptor Daemon was unable to start the remote client agent
Cause
Incorrect symbolic links and/or environment variables

If the file permission, symbolic links or environment variables are not set up properly for the Tivoli Storage Manager client, one may be able to load the initial web client GUI but would get the following error when trying to do backup/archive/restore or retrieve from the main web gui :

ANS2619S The client acceptor Daemon was unable to start the remote client agent
The user will not be prompted for userid or password but would rather receive the above error in the Tivoli Storage Manager web client java applet window. The Tivoli Storage Manager client dsmerror.log simply shows :

Error starting Remote Client Agent

This can be caused by

a) incorrect permission for the Tivoli Storage Manager files (dsmagent, dsmcad) and others

b) incorrect links for the tsm files from /usr/lib and/or /usr/bin

c) incorrect environment variables

Resolving the problem
To fix this,

a) check directory/file permission for the tsm client install directory. The dsm, dsmc,dsmcad,dsmagent executables should have "-r-xr-xr-x" permissions.

b) Check all the symbolic links

i) check the symbolic links /usr/lib and make sure that
.libApiDS.so points to /opt/tivoli/tsm/client/api/bin/libApiDS.so
.libXApi.so points to /opt/tivoli/tsm/client/api/bin/libXApi.so
.libxerces-c1_6_0.so points to /opt/tivoli/tsm/client/ba/bin/libxerces-c1_6_0.so
.libxmlutil-5.2.0.0.so points to /opt/tivoli/tsm/client/ba/bin/libxmlutil-5.2.0.0.so
ii) check the symbolic links /usr/bin and make sure that

.dsm points to /opt/tivoli/tsm/client/ba/bin/dsm
.dsm.jar points to /opt/tivoli/tsm/client/ba/bin/dsm.jar
.dsmadmc points to /opt/tivoli/tsm/client/ba/bin/dsmadmc
.dsmagent points to /opt/tivoli/tsm/client/ba/bin/dsmagent
.dsmc points to /opt/tivoli/tsm/client/ba/bin/dsmc
.dsmcad points to /opt/tivoli/tsm/client/ba/bin/dsmcad
.dsmj points to /opt/tivoli/tsm/client/ba/bin/dsmj
.dsmswitch points to /opt/tivoli/tsm/client/ba/bin/dsmswitch
.dsmtca points to /opt/tivoli/tsm/client/ba/bin/dsmtca
.dsm.sys points to /opt/tivoli/tsm/client/ba/bin/dsm.sys
.dsm.opt points to /opt/tivoli/tsm/client/ba/bin/dsm.opt
Note : If the Tivoli Storage Manager client is installed in different directory or the installation directory is mounted to another location, make sure to update the symbolic links accordingly.

c) Setup the DSM_DIR & DSM_CONFIG environment variables :

i) For "C" Shell, add these in /etc/.login :
setenv DSM_DIR /export/opt/tivoli/tsm/client/ba/bin
setenv DSM_CONFIG /export/opt/tivoli/tsm/client/ba/bin/dsm.opt

ii) For "Korn" shell, add these in /etc/profile :
DSM_DIR=/export/opt/tivoli/tsm/client/ba/bin
DSM_CONFIG=/export/opt/tivoli/tsm/client/ba/bin/dsm.opt
export DSM_DIR
export DSM_CONFIG
Once the permission, symbolic links and environment variables are set correctly, the web client remote agent should load properly.

About

This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.

Next
« Prev Post
Previous
Next Post »