need help with nwagent

[hywaydave]

Hello,

I have ArcServe 9 running on Windows 2000 server. I'm trying to back up my two Novell servers remotely. We have the nwagent installed and loaded on the Novell servers. The backups have been working fine until we rebooted them just before my boss took off on vacation, now when you go to click on the server in the "modify job" within ArcServe it just tells me that it lost connection, would you like to reconnect? If you hit yes it just loops again. From the security option I have the correct distinguished name and password.

On the Novell server itself, the NWAgent has a log that reads:
"Agent is busy, reject job request from <servername>"

I need some help please. Thanks.

 

[sandyboy]

Hi,

Can you delete the netware object and readd it using FQDN
and check,if fails then do the following:

Perform a dsrepair to make sure there are no errors in
the NDS. Perform local + full repair and ensure 0 errors.
Also, reconfigure SMDR on the server and have the SMS services restarted once before you perform a backup.

Also check this Document:

http://supportconnect.ca.com/sc/kb/...&docid=364265&bypass=yes&fromscreen=kbresults

Good Luck!!!

Cheers

 

[hywaydave]

I saw that article, but we don't have a vulnerability scanner running. I ran Nessus once a couple weeks ago and that was it. I'll see what the boss thinks about doing a DSRepair today.

 

[vschumpy]

Either there is another connection either from a manager workstation to the NWAgent or a previous connection has not been cleaned down correctly. Part of the problem is that the NWAgent can only deal with one connection at a time, and if that connection is being used elsewhere it will not allow another one. You may like to try unloading and reloading the nwagent at the console, that should clear down the existing or ghost connection and allow you to connect again.

 

[hywaydave]

We did reboot both Novell servers last Monday and I think the backup worked that one night, but then failed the next night.

 

[hywaydave]

BTW... I didn't run Nessus on the Novell servers either

 

[davidmichel]

any updates installed just prior to the problem?
Have you checked the agent log?