Check the adsm-l archives at www.adsm.org for my response back on August 9
with regard to this issue.

Regards,

Andy

Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: araibeck 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.





Jeff Bach <jdbach AT WAL-MART DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
08/14/2001 06:00
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: TSM Win2K 4.2.0 client scheduler problems



This sounds like a bad design.  How about a Correction of the Design
process?

Jeff Bach



        -----Original Message-----
        From:   Eliza Lau [SMTP:lau AT VTCAT.CC.VT DOT EDU]
        Sent:   Thursday, August 09, 2001 3:49 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: TSM Win2K 4.2.0 client scheduler problems

        I just got off the phone with TSM level 2 support.  This is a
known
problem
        with the Windows 2000 4.2.0 client.  It is a timing issue.  The
client
        can't get the password from the server and tries 3 times.  A
second
        later it gets it.  The developers have no fixes for this, no APAR
        either.  They may just document it as "working as designed".
Beside
getting
        these erroneous errors in dsmerror.log and the event log,
scheduled
backup
        works just fine.

        Eliza


        >
        > I have the excact same experience - and have found no other
solution than to
        > go back to TSM v4.1 lev. 2.19. Then the problem was gone.
        >
        > Server: TSM v4.1 lev 1.0 on OS/390
        > Client: Windows NT 4.0, SP6
        >
        > Henrik Bach Gravesen
        > Jyske Bank A/S, Denmark
        > gravesen AT jyskebank DOT dk
        >
        > >
        > > A user of mine is using the TSM Win2K 4.2.0 client acceptor
        > > service to manage
        > > the client scheduler.  The acceptor service wakes the
        > > scheduler every 12 hours
        > > and starts the scheduled backup with no problems.  All is well
except
        > > that she is getting the error code 4099 in the application
        > > event log every time
        > > the scheduler wakes up (every 12 hours).  In dsmerrorlog,
        > >    SessOpen: Error 137 from signon authentication   (3 times)
        > >
        > > Password is set to generate.  GUI, command line, and
        > > scheduled backups all
        > > run fine.  The user is not prompted for the password.  So
        > > there must not be
        > > any authenication problems and the password is stored in the
registry.
        > >
        > > Has anyone seen this with their W2K 4.2.0 clients?  Is this
        > > normal behavior?
        > >
        > > server - TSM 4.1.3 on AIX 4.3.3
        > > client - Windows 2000 4.2.0
        > >
        > > Thanks in advance,
        > > Eliza Lau
        > > Virginia Tech Computing Center
        > > lau AT vt DOT edu
        > > 540-231-9399
        > >
        >


**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed.  If you have received this email
in error destroy it immediately.
**********************************************************************