I'm receiving the same error messages for all Win2K clients, even though most
have only had the 4.1.2.12 client installed.  Our server is AIX 4.3.2 and TSM
3.1 right now.  Please let me know if you find anything else out...  Thanks!

Luke Dahl
NASA-Jet Propulsion Laboratory
818-354-7117

"Gill, Geoffrey L." wrote:

> I have a client that upgraded an NT server to WIN2K without telling me. That
> node had ADSM baclient V3.1 on it. My server is AIX 4.3.3 TSM 4.1.2.0, and
> had begun to show failures of that node in the scheduler. A review of the
> error logs on the node didn't show any real failures, except for some system
> files in use. The backup did complete and reported this in the dsmsched.log.
>
> I previously noted, when my server was at 3.1.2.55, that these would not
> show up as failures in the schedule. I'm not sure if this is related to the
> mixture of codes/OS's of the client and server. I did upgrade the client to
> 4.1.2.12 on Thursday last week and the failure reports have disappeared.
>
> Geoff Gill
> TSM Administrator
> NT Systems Support Engineer
> SAIC
> E-Mail:   gillg AT saic DOT com
> Phone:  (858) 826-4062
> Pager:   (888) 997-9614
>
> >-----Original Message-----
> >From: Joseph Dawes [mailto:jdawes AT CHUBB DOT COM]
> >Sent: Monday, May 14, 2001 7:41 AM
> >To: ADSM-L AT VM.MARIST DOT EDU
> >Subject: TSM 4.1 bug???
> >
> >
> >Does anyone have a problem with tsm reporting events inaccurately i.e.
> >saying it failes when it completed and the reverse??
> >
> >
> >
> >
> >please advise
> >
> >
> >
> >Joe
> >