Hello Michael,

I am not sure whether you are saying the NT system hangs when you
log out of it, or whether the ADSM client hangs when you try to quit
out of it. If it is the ADSM client, is it the Admin client or
Backup-Archive client or both? Command line or GUI or both? Does it
happen every time, even if you just start the client and immediately
quit out of it, or is it after you perform a certain operation? Are
there any operations you can perform and then quit successfully? Also,
if possible, have you tried connecting this problem client to the
ADSM server at the other location you mentioned as a test? Does the
client hang in that case, or can you quit successfully? If the
problem does not appear when connecting to the other ADSM server, what
are the differences (if any) between the two server versions? When
the client does hang, what does a QUERY SESSION show for that client?
Do you get any messages in the activity log that pertain to that
client? How much CPU does Task Manager show the client using while it
is hung?

It would also be helpful if you could describe your NT environment
in detail (NT version including service pack level, applications that
run on that system, etc.) as well as the step-by-step process you use
to recreate the problem (i.e. which program is started, what commands
are entered or what mouse clicks are performed, what output you see,
etc.) I do not know whether a successful diagnosis can be made on this
forum, but having the answers to these questions would certainly
improve the chances.

Best regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com

     I am current running an adsm server version 2.1.0.14 on NT and a
     version 3.1.3 backup client on the same machine. I am encountering a
     problem were the client hangs, when the person uses the client and
     tries to log out of the client, the client hangs. I have contacted
     ADSM support on this matter, and they don't have a clue to solving
     this problem. I also know that they will not support a server 2 and
     that is a problem to us. The only solution that adsm support gave me
     was to upgrade the server and client to the lastest version. But that
     is not a solution that can be done right away for us. We have plans to
     upgrade in the future. We are also running the above server and client
     at another location and we are not having this problem there. Is there
     any way I could fix this problem. If you have any suggestions am I
     willing to try them.

     Thanks in advance
     Michael Zive
     Simon and Schuster