ADSM-L

TSM 3.7 Web BA-Client under WIN2000 - the solution

2000-02-08 08:46:25
Subject: TSM 3.7 Web BA-Client under WIN2000 - the solution
From: Gerd Becker <Gerd.Becker AT EMPRISE DOT DE>
Date: Tue, 8 Feb 2000 14:46:25 +0100
under special circumstances the TSM-Services Cleint acceptor and Remote
client agent were wrong installed. So it is necessary to deinstall the
services and reinstall it with the Utility dsmcutils. Here I have a little
documentation, what to do:
Tivoli Storage Manger 3.7                                       How to
install the Client-Services in WIN/NT

C:\Programme\tivoli\tsm\baclient>dsmcutil showpw /node:aptiva2000

TSM Windows NT Client Service Configuration Utility
Command Line Interface Version 3.00.a
Last Updated Sep 20 1999
TSM Api Verison 4.1.0

Command: Display Registry Password
Machine: APTIVA (Local Machine)



Registry password for node APTIVA2000 = 'START' .

Authenticating password with TSM for node APTIVA2000 ....


Connecting to TSM Server via client options file 'C:
\Programme\tivoli\tsm\baclie
nt\dsm.opt' ...

Password authentication successful.


C:\Programme\tivoli\tsm\baclient>dsmcutil list

TSM Windows NT Client Service Configuration Utility
Command Line Interface Version 3.00.a
Last Updated Sep 20 1999
TSM Api Verison 4.1.0

Command: List Installed TSM Client Services
Machine: APTIVA (Local Machine)


Installed TSM Scheduler Services:

   1. ADSM Client Acceptor
   2. ADSM Remote Client Agent
   3. TSM CAD
   4. TSM Scheduler

4 TSM Client Services were located.

C:\Programme\tivoli\tsm\baclient>dsmcutil remove /name:"TSM Client
Acceptor"

TSM Windows NT Client Service Configuration Utility
Command Line Interface Version 3.00.a
Last Updated Sep 20 1999
TSM Api Verison 4.1.0

Command: Remove TSM Client Service
Machine: APTIVA (Local Machine)



Removing TSM Client Service 'TSM Client Acceptor' ...

The service was successfully removed.


C:\Programme\tivoli\tsm\baclient>dsmcutil install cad /name:"TSM Client
Acceptor" /node:aptiva2000 /password:start

TSM Windows NT Client Service Configuration Utility
Command Line Interface Version 3.00.a
Last Updated Sep 20 1999
TSM Api Verison 4.1.0

Command: Install TSM Client Service
Machine: APTIVA (Local Machine)



Installing TSM Client Service:

       Machine          : APTIVA
       Service Name     : TSM Client Acceptor
       Client Directory : C:\Programme\tivoli\tsm\baclient
       Automatic Start  : No
       Logon Account    : LocalSystem

The service was successfully installed.


Creating Registry Keys ...

Updated registry value 'ImagePath' .
Updated registry value 'EventMessageFile' .
Updated registry value 'TypesSupported' .
Updated registry value 'OptionsFile' .
Updated registry value 'EventLogging' .
Updated registry value 'ClientNodeName' .
Updated registry value 'ADSMClientKey' .
Updated registry value 'HttpPort' .
Updated registry value 'HttpsPort' .

Generating registry password ...
Authenticating password with TSM for node APTIVA2000 ....


Connecting to TSM Server via client options file 'C:
\Programme\tivoli\tsm\baclie
nt\dsm.opt' ...

Password authentication successful.

The Registry password for node APTIVA2000 has been updated .



C:\Programme\tivoli\tsm\baclient>dsmcutil install remoteagent /name:"TSM
Remote Agent" /node:aptiva2000 /password:start

TSM Windows NT Client Service Configuration Utility
Command Line Interface Version 3.00.a
Last Updated Sep 20 1999
TSM Api Verison 4.1.0

Command: Install TSM Client Service
Machine: APTIVA (Local Machine)


Locating partner client acceptor service 'TSM Client Acceptor' ...



Installing TSM Client Service:

       Machine          : APTIVA
       Service Name     : TSM Remote Agent
       Client Directory : C:\Programme\tivoli\tsm\baclient
       Automatic Start  : No
       Logon Account    : LocalSystem

The service was successfully installed.


Creating Registry Keys ...

Updated registry value 'ImagePath' .
Updated registry value 'EventMessageFile' .
Updated registry value 'TypesSupported' .
Updated registry value 'OptionsFile' .
Updated registry value 'EventLogging' .
Updated registry value 'ClientNodeName' .
Updated registry value 'ADSMClientKey' .
Updated registry value 'PartnerName' .
Updated Partner Client Acceptor registry value 'PartnerName' .

Generating registry password ...
Authenticating password with TSM for node APTIVA2000 ....


Connecting to TSM Server via client options file 'C:
\Programme\tivoli\tsm\baclie
nt\dsm.opt' ...

Password authentication successful.

The Registry password for node APTIVA2000 has been updated .


C:\Programme\tivoli\tsm\baclient>

Mit freundlichen Grüßen / best regards

Gerd Becker

EMPRISE NETWORK Consulting GmbH
Albstr. 14
70597 Stuttgart

Tel.: 0711/990083-0 oder Mobil: 0172/4036581
Fax: 0711/990083-9
mailto:gerd.becker AT emprise DOT de

http://www.emprise.de

Under WIN2000 i have running an TSM 3.7 Server and Client. The server and
the Client Acceptor are started without errors. When I tried to connect to
the BA-Client through the Web, I got the error ANS2619S The Client Acceptor
Daemon was unable to start the Remote Client Agent. In the dsmerror.log I
found the message  Error starting agent service: The service 'ADSM Remote
Client Agent' does not exist.  Error starting Remote Client Agent.
I thougt that the Remote Client agent automatically was started by the
Client Acceptor. What's wrong?


Mit freundlichen Grüßen / best regards

Gerd Becker

EMPRISE NETWORK Consulting GmbH
Albstr. 14
70597 Stuttgart

Tel.: 0711/990083-0 oder Mobil: 0172/4036581
Fax: 0711/990083-9
mailto:gerd.becker AT emprise DOT de

http://www.emprise.de
<Prev in Thread] Current Thread [Next in Thread>
  • TSM 3.7 Web BA-Client under WIN2000 - the solution, Gerd Becker <=