Hello,
I believe that the following procedure should do the trick.
Step 2 especially is the key (no pun intended).
WARNING: This procedure involves editing the NT registry.
THE REGISTRY EDITOR IS NOT FORGIVING OF MISTAKES!
Errors in editing the registry have the potential
to render the system unstable or even unbootable.
If you are unfamiliar or uncomfortable with
editing the registry, then either ask someone who
is more experienced do this for you or install
this fixtest (which automatically performs these
operations for you).
1) From an MS-DOS command line prompt, enter the
following commands:
unlodctr "ADSM Client Performance"
unlodctr "TSM Client Performance"
If the performance counters were previously
installed, you should see messages similar to this:
Removing counter names and explain text for
ADSM Client Performance
Updating text for language 009
If the performance counters were not previously
installed, you will see a message similar to this:
Counters for ADSM Client Performance have not
been installed yet
2) Using the registry editor, remove the following
keys (including their values):
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Services\
ADSM Client Performance
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Services\
EventLog\
Application\
ADSM Client Performance
Note: Also check for keys with "TSM" in the name instead
of "ADSM".
The performance counters and registry entries are now
removed.
Regards,
Andy
Andy Raibeck
IBM/Tivoli
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
Hello TSMers,
I have scoured the TSM Knowledge Base at http://www.tivoli.com/asktivoli
on the subject error and found the APAR. However the work around does not
work for us. First, the local fix using the unlodctr doesn't work because
it
is not called "TSM Client Performance", but "ADSM Client Performance".
Then, the "lodctr perfctr.ini" command doesn't work because TSM Client
Performance is hard-coded into the perfctr.ini file when it needs to say
ADSM Client Performance. However, even when you make these modifications,
it still does not get rid of the error messages.
As for the changes to the registry, the registry key they mention doesn't
exist.
Any other options?
