If the client is just "disappearing", it is probably crashing. You can
confirm this by setting Dr. Watson as your default debugger. From the OS
command prompt issue:

   drwtsn32 -i

Then try to reproduce the crash, and see if you get a pop-up message about
the crash.

There were some bugs in earlier client code that could cause the client to
crash while processing system objects. I would recommend upgrading to the
5.1.6 client, as that fixes these problems.

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.ibm DOT com

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




Kjetil Furnes <kjetil.furnes AT WIDECOMPUTING DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/09/2003 08:26
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Win32 baclient dies when backing up system object
!?


Hi !

I have a problem with some of my clients.
Lately, some of them are unable to backup the systemobject !
When doing a manual backup, I find out that it is the system files that
cause the application to die.
(It doesn't hang, it just terminates and disappears !)

When running as a Scheduler service, this causes the Scheduler service
to stop,
giving the backup a failed status. (I don't know if it actually backs up
ordinary files first, but it discards them due to the failure)
The server reports the following:

09.09.2003 06:00:00   ANR2580E Schedule DAILY_DAP in domain PIPELINE_DAP
for
                                 node OSLDAP01 failed.


09.09.2003 05:59:55   ANR0480W Session 11689 for node OSLDAP01 (WinNT)

                                 terminated - connection with client
severed.


I've tried to reinstall the clients, also to different versions with the
same result.
Currently I have this problem on baclient versions 5.1.0.1 and 4.2.1.20.
(Have also tried various other versions)
My server is a version 4.1.3.0 (WinNT)

The weird thing, is that this problem seems to appear "overnight" for no
specific reason !?
(Same configuration as last 18 months without problems)

The scheduler logfile looks just fine (no errors)
The baclient error log states that the backup of local drives is
finished.
(usually with one or two errors due to a file being in use -> the object
is in use by another process, which is no big deal)


Anyone seen this before ?
Tips ? Workarounds ?


Kjetil Furnes
System Administrator
Wide Computing AS