Re: TSM crash with: ANR9999D

Hi Andy,

There is a stack back trace for each thread.  Since the list is pretty long
I am not sure which one to show you.  Debugging is NOT my forte`!  I could
zip and attach the log.  Its not very big when zipped.

Chris



-----Original Message-----
From: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
Sent: Monday, March 10, 2003 12:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM crash with: ANR9999D


Is Dr. Watson configured as the Windows 2000 default debugger (most likely
it is)? If so, look in the Dr. Watson log file (drwtsn32.log) and find the
exception that corresponds to the date and time stamp shown the Windows
event log record. There should be a stack trace; what does it look like?

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Chris Murphy <cmurphy AT IDL.STATE.ID DOT US>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> 03/10/2003 
12:12
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        TSM crash with: ANR9999D



Greetings all!

Environment: TSM V 5.1.1.0 on Win2k SP3

While check on this AM's processes and such, one of our ITSM boxes crashed.
This was the only error I saw that showed up in the NT event log:

Event Type:     Error
Event Source:   ADSMServer
Event Category: None
Event ID:       27
Date:           3/10/2003
Time:           10:46:55 AM
User:           N/A
Computer:       xxxxxxxxx
Description:
TSM Server Diagnostic: ANR9999D: ADSM Exception Information: file =
pkthread.c, line = 2061,Code = c0000005, Address = 1042ecdc Attempt to read
data at address ceaa000~

Searched ADSM.ORG and found one other person having this error back in the
ADSM 3.7 days, but noone replied back apparently.  Time to call support?
Other ideas?

This box has been rock-stable for months and has never crashed before.  No
majors changes have been made to it in several weeks.  I *think* migration
was running when it crashed.

TIA!

Chris Murphy
IT Network Analyst
Idaho Dept. of Lands
Office: (208) 334-0293
cmurphy AT idl.state.id DOT us