Hi,

I just read the other message about the server crasch. So I thought I
could post my pk_exception here too.

It seems to me that 5.3 is stable and reliable.....

I get the errors (re-creatable!!!) during high workload. Probably a
memory problem and I have forwarded it to level 2.

The fun part is that TSM doesnt generate a dmp- or err-file. Since you
can kill/terminate processes in Taskamanager DrWtsn32 wont do a crasch
dump since that is a quite normal in Windows.... But the error file
would have been nice to have. :-)
TSM 5.3.2.0 on w2k3, sp1 all securty fixes.


11/28/2005 19:33:31      ANR7838S Server operation terminated.
11/28/2005 19:33:31      ANR7837S Internal error PK_EXCEPTION (Refer to
the NT
                          application event log for details) detected.
11/28/2005 19:33:31      ANR9999D ThreadId<18> issued message 7837 from:
11/28/2005 19:33:31      ANR7833I Thread 1 (tid 4660) terminated in
response to
                          program abort.


Event Type: Error
Event Source: ADSMServer
Event Category: None
Event ID: 27
Date:  11/4/2005
Time:  7:33:11 PM
User:  N/A
Computer: 
Description:
TSM Server Diagnostic: ANR9999D: PK_EXCEPTION -- Thread 18 (NT TID
4292): pkBroadcastCondition error, object -1: Unknown error code
encountered - 0
 
+++
Event Type: Error
Event Source: ADSMServer
Event Category: None
Event ID: 27
Date:  11/4/2005
Time:  7:33:11 PM
User:  N/A
Computer: 
Description:
TSM Server Diagnostic: ANR9999D: CONDITION VARIABLE ERROR
Verify_No_Cond_Waiters timeout RC: 0 - Thread (NT TID) (4292)



//Henrik


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.