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
> [EMAIL PROTECTED]
>
> >
> > 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
> > [EMAIL PROTECTED]
> > 540-231-9399
> >
>
