How many licensed connections is your server configured for? Does it reach it's limit? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
We are running 6.1 on an NT4 box, but that does not reflect our issue. We do run TSA500 and there are no problems running scheduled backups from the Legato server.
What we get from time to time are dropped connections and frequently this eror message shows up when that occurs. We then lose on of the save sets and have to restart it because Legato is not coded well enough o recognize the dropped connection.
I recently ran across an error similar to this when I was trying to configure my ArcServe v7.0 NetWare Agents on remote NetWare Servers.
Basically, I had incorrect TCPIP Addressing command line statements that caused the messages to come up when the Agent would launch. Once I corrected the TCPIP Addressing command lines in the ASCONFIG.INI file, all was good.
My first question to you is when are you receiving the error message? Is it when Legato launches and attempts to backup the NetWare Server?
Other than TSA500, are you running any kind of Legato Backup Agent on the NetWare Server?
The message you are getting is due to you are starting too many sessions on the legato server.
Basically the NW server can only open a certain amount of RPC sockets. We have this issue, we just start our nightly jobs at a staggered time, like 8 per hour to get around this issue.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.