I started to get this and a few more Dr. Watson errors after I upgraded from
ADSM 3.1 (NT) to TSM 4.1

For some reason there was a SCSI error with the library. I have since tried
to upgrade to 4.1.3 with no luck. I again uninstalled everything involving
TSM and reinstalled including importing my data base, a long dragged out
process. So far so good.

FYI... I also had (for some unknown reason) my drives (3575 - IBM) replaced
due to them going offline and marking most of the tapes read-only. Their
firmware was upgraded on them, but I still believe there were communication
errors being reported back to TSM Server. Ever since this was done I have
had very few problems (on the server side).

I was then experiencing problems with a few clients that are having problems
communicating with TSM Server 4.1.3, their sessions just keep timing out
(currently set to 300 seconds). New client installs have not solved this
problem, however I have installed the old ADSM 3.1 on my test server and
tried to backup, and of course the problem does not exist.


Joe Cascanette