Stopping a "running" job in NWAgent

[ILW]

Greetings!

Running NW51SP6. The servers are backed up from Brightstor/Arcserve 11.1 on Windoze, and thru the NWAgent. Every so often, the 2 loose connection; Windoze says the job failed, NWAgent says it's still running.

At this stage, telling the job to stop from within NWAgent does nothing and the only way out seems to be a reboot (if you try to unload NWAgent the console prompt never comes back)

Any suggestions how I can stop NWAgent running the job / unload it / whatever, without having to reboot every time?

I think this is more a NetWare than Arcserve question, but apologies to anyone who disagrees.

 

[TheLad]

You should be able to cancel the NWAgent job by hitting the Delete key then answering Yes.

I guess the reason your console is hanging when you unload it is because you are actually trying to unload the NLM from the console screen (UNLOAD NWAGENT) - you could try pressing Escape on the NWAgent screen and answering Yes and while this might hang the NWAgent NLM it will not hang the console.

As to why the issue occurs in the first place, I presume it is a disconnect error you get on the Windows server? Are both servers forced to a speed/duplex on both server and switch port? Servers should not use Auto Negotiate and Arcserve in particular can play up as a result. That aside, are you running the latest NIC drivers on both servers?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[ILW]

Should be able to cancel the NWAgent job by hitting Delete - yes should, but it never stops.

If I try to unload from within the agent, it keeps coming back "NWAgent is still running, Retry unload?"

Yes, the initial fault comes from Windows disconnecting (server reboot or whatever) Speed & duplex are forced all the way thru - been caught like that before. NIC drivers are a mix - this is a global (80 sites) problem for us. Going to SP8 sometime this year, but don't really expect it to fix this.

Ian

 

[TheLad]

I think you are looking in the wrong area for a resolution - it appears to me that NetWare is not your issue here, it is your Windows server running Arcserve that is disconnecting so I would concentrate my investigation there. Whilst upgrading to SP8 on NetWare is advised, further checks on your Windows server is also advised too.

What version of Windows Server is it running (including SP)? Are you running the latest Arcserve patches? Is the hardware sufficiently spec'd to run the version of Windows Server?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[marvhuffaker]

I would upgrade to SP8 on NetWare and also apply the latest TSA update. I believe that TSA5UP19 works on NetWare 5.1. It is possible that Netware is at fault here, but I make a living proving that Windows screws up everything.

I understand you have it planeed to update later this year, but you should be able to take one server out of the mix and do the updates now. I gave up trying to troubleshoot servers that don't have latest support pack. It's not worth it. Even if it doesn't fix this exact problem, it brings your server to a baseline where it's much easier to talk about with people.

Marvin Huffaker, MCNE

http://www.redjuju.com