Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unsuccessful save set

Status
Not open for further replies.

ars52

MIS
Apr 5, 2002
1
US
I am running Networker 5.5.1 on a Solaris 2.5.1 server with the following error;

*client:c:\ has been inactive for 33minutes since Tue Apr 2 03:39:19 2002.
*client:c:\ is being abandoned by nsrexec.

The client is a WindowsNT4.0 server sp5. This backup has been running OK for sometime until now.

Thankful for help given.
Brian
 
There're a lot of inactivity problemsin old LEGATO versions,
(version 5.5.1 has been patched to (5.5.2, 5.5.3 and 5.7).
If it is not a bug then it must be a network communication problem (network overload ?).

Sometimes, to resolve this problem you only have to change a parameter called "inactivity timeout" on the group ressource that controls this client (it must be 30 by default, change it to 0 and try again).
You'll perhaps need to change display settings to view "hidden attributes".

Bye.
 
Why Would you change this to 0 than increasing the time out to say 60 to keep the connection longer.

Regards
Simon Simon Peter Wickham
Email: s.wickham@zoom.co.uk
 
Hi!

If you set the inactivity time to 0 you will get no timeout.
in other words the session will never timeoute.
 
However, if you have a connectivity problem, it will still be trying in the morning! Mike davison
mike.davison@avon.com
 
We use Networker 5.5.1 and have had the same problem (amongst many others) and have found that you have to stop/start the "Networker Remote Exec" service on the NT client.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top