Your second problem might be either the password for the client on the ADSM
server getting out of synch,in which case you would need to reset the password
for the node on the server.

or

you may need a longer Commtimeout setting on the server as the comms are dropped
before the client gets to send any info. commtimeout can go up to 7200.

Denver UNIX Support wrote:

> Hi!
>         I am getting the following error on one of my HP clients and unsure
> about what to do:
>
> 05/25/99   22:48:10 ANS4010E Error processing '/odbackup01': stale NFS
> handle
> 05/25/99   22:48:14 ANS1512E Scheduled event 'DAILY_9PM' failed.  Return
> code = 4.
>
> Any suggestions?  Thanks for your help.
>
> I also have another HP client that hasn't been backing up.  When I check the
> event it always says started from last night, there are no apparent errors
> in the dsmerror log but it's not being backed up.  Nothing is happening and
> I just cancel the session.  Any ideas:  Here are a couple messages from the
> error log from when I cancelled it this morning:
>
> 05/26/99   07:24:45 TcpFlush: Error 32 sending data on Tcp/Ip socket 5.
> 05/26/99   07:24:45 sessSendVerb: Error sending Verb, rc: -50
> 05/26/99   07:24:45 TcpFlush: Error 32 sending data on Tcp/Ip socket 5.
> 05/26/99   07:24:45 ANS1809E Session is lost; initializing session reopen
> proced
> ure.
> 05/26/99   07:24:45 ANS1809E Session is lost; initializing session reopen
> proced
> ure.
> 05/26/99   07:25:00 ANS1811S ADSM session could not be reestablished.
> 05/26/99   07:25:00 ANS1369W Session Rejected: The session was canceled by
> the A
> DSM server administrator.
>
> 05/26/99   07:25:00 ANS1512E Scheduled event 'DAILY_9PM' failed.  Return
> code =
> 4.
>
> Thanks again for your help....
>
> Luanne R. Hancock
> J.D. Edwards
> 303-334-4843 office
> 303-334-4716 fax
> luanne_hancock AT jdedwards DOT com