Re: TDP for MS Exch

Joel,

This shouldn't be related to anything with TDP for Microsoft Exchange.

I don't work on the base client code, so I am not sure of the current
issues with the performance counters under 3.7.

I did find APARs IC24370 and IC25335, that address performance
counter issues.  IC25335 says in its conclusion:

  COMMENTS: Please see the closing remarks for V3.1 IC24370.
  In TSM Version 3.7, the performance monitor function is still
  inactivated, pending a redesign (if it is possible) so
  that other performance monitoring tools such as Netfinity
  do not cause TSM to have this problem. The remarks for IC24370
  apply in V3.7 as well.
  It is a suggestion for a future release to try to redesign
  and reimplement the function so that it will work when
  outside performance monitors are also in use.

(By the way, the TDP for Exchange level you should be using is 1.1.1.01.
That is IC25816...so I think you just misquoted the level number.)

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com


Joel Cooper <jocooper AT DTTUS DOT COM>@VM.MARIST.EDU> on 03/15/2000 06:01:41 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  TDP for MS Exch



Hi:
Has anyone ever seen Exchange DS fallover with a Dr. Watson related to TSM?

I have the latest b/a client code (3.7.1 IP 21806_3) and the latest TDP for
Exchange code (1.1.0.0 IP25816).

But this morning, my event log shows me a message by source: ADSM Client
"Create
failed for the ADSM client performance counter thread list mutex. The mutex
name
is in the attached data. "

Next, I get the message from source: perflib "The Open Procedure for
service
"ADSM Client Performance" in DLL "dsmcperf.dll" failed.  Performance data
for
this service will not be available. Status code  returned is DWORD 0. ".

Then within ONE SECOND, DSAMAIN.EXE dumps w/a Dr. Watson log.

Points I know of: I thought the TSM errors were an earlier bug in the b/a
client
and the latest 3.7 and 3.1 client packages corrected them.

The clients I used to see these messages on before never had anything
crash,
just saturation of my event logs.

Any ideas?
Thanks in advance,

Joel Cooper
Deloitte & Touche LLP
jocooper AT dttus DOT com