I've seen this error with the 5.1.5 client a few times.
I've been able to clear it by one of two methods,
Firstly using the dsmcutil updatepw command to update the password for the
scheduler service, instead of using the GUI to recreate the password.
UPDATEPW - Generate encrypted TSM registry password
Syntax:
dsmcutil UPDATEPW /node:<TSM nodename>
/password:<password>
[options ...]
Required options:
The Node name for which to generate the registry
password
and the password to encrypt into the registry.
In a cluster environment, dsmcutil will attempt to
determine the node's cluster settings by examining
all scheduler services associated with that node.
If dsmcutil can not make this determination, it
will display appropriate diagnostic messages. In
such a case, it is recommended that you fix the
problems reported by the diagnostic messages.
However, if fixing the problems is not immediately
practical, then you can re-run the command and
include the CLUSTERNODE, CLUSTERNAME (if CLUSTERNODE
is YES), and FORCE:YES options.
Normally CLUSTERNODE and CLUSTERNAME can be omitted
because dsmcutil can determine the cluster settings
on its own. In fact, if these options are specified,
they will be ignored unless FORCE:YES is used. In
that case, dsmcutil will use the CLUSTERNODE and
CLUSTERNAME settings that you provide.
If dsmcutil can not determine the node's cluster
settings, it is most likely because there is more
than one scheduler service for the node, but the
cluster settings for these services are inconsistent
with each other. For instance, one service is
defined with CLUSTERNODE:YES and the other service
is defined with CLUSTERNODE:NO; or all services are
defined with CLUSTERNODE:YES but they have different
cluster names.
The password will be validated with the TSM server
if the /VALIDATE:YES option is specified.
The password will be updated on the TSM server if
the /UPDATEONSERVER:YES options is specified. If
this option is specified the current TSM password
must be specified with the /OLDPASSWORD option.
Secondly, You may need to disable the original Scheduler service and
recreate it using the DSMCUTIL command to create the new service, using the
correct nodename/password/option file location. DO NOT use the gui!
For more information, see IBM Tivoli Storage Manager for Windows
Backup-Archive Clients Installation and User's Guide, Appendix C. Using the
Client Service Configuration Utility (Windows NT, 2000, XP)
DSMCUTIL has lots of options available to show you what is contained within
the registry. I suggest you follow the links within the appendix...
Hope this helps
Levon Litster
Avnet Computer Marketing
-----Original Message-----
From: tsmadmin account for Excaliber Business Solutions
[mailto:tsmadmin AT VODACOM.CO DOT ZA]
Sent: 25 July 2003 07:18
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Error Initializing TSM Api on Windows
Importance: High
Hi
I have the same error with windows 2003 server running TSM 5.1.6 client.
This problem has also given us problems trying to create the Scheduler
Service for TSM.
Is there a problem with TSM client 5.1.6.
Thks
Sean
-----Original Message-----
From: Lawrence Clark [mailto:Larry_Clark AT THRUWAY.STATE.NY DOT US]
Sent: Thursday, July 24, 2003 7:16 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Error Initializing TSM Api on Windows
Our NT people have upgraded thier BA client from 5.1 to 5.1.5 and have
been getting the error below. It does not appear to intefere with
backups or interrupt the schedular, but reoccurs on rebooting the
system. Anyone seen this?
================================================
Windows application Event Log warning when starting the TSM 5.1.5
Scheduler Service....
Source: AdsmClientService
Type : Warning
EventID : 4098
Error Initializing TSM Api, Unable to verify Registry Password, see
dsierror.log
"This e-mail is sent on the Terms and Conditions that can be accessed by
Clicking on this link http://www.vodacom.net/legal/email.asp "
|
