QO33421 and QO33425 Bug Updates Netware 1

[8arcserve]

Has anyone had any joy with QO33421 and QO33425 updates for Arcsh*te 7 Netware.
I've had nothing but problems with these so called updates ,jobs now just freeze when connecting to nwagents,
E3148 failed to begin new session in Arcserve database, also backuser (which as full rights to the tree)conplains it does not have rights to nds. So can not login to nwagent. And all these problems are intermitant!!
I have a good idea that this may be a btrieve problem

http://support.ca.com/techbases/asnw7/asnw7_19108.html.

Have tried this fix but to no avail!

The only way I've found to get the nwagents to work is to load the OLD versions QO28844 (which are no longer on the ca support web site..GREAT). Then everything works fine.???

I'm so tired of this 'hideous bug fest' of a program. Do CA actually know what there doing! I wonder some times

 

[jperleevt]

I am having similar problems w/ my backup. I do not have a copy of the SP that you back rev'd to. Did you stay w/ QO33421 or did you Back Rev that as well? If so to what? Would you mind sending be QO28844?

This is getting really frustrating, I get back-ups maybe 2-3X a week, not good!

Thanks
Jen

 

[8arcserve]

I have noticed that I only seem to have problems with the new nwagent QO33425 running Servers running Netware 5.1 and below. Netware 6 Servers seem to be OK.
So i'm now running new nwagent QO33425 on netware 6 and old nwagent QO28844 on netware 5.1 or below.
Will run this config and see how it goods. fingers crossed

jperleevt if you leave your email address i'll send you the QO28844 patch.

 

[jperleevt]

Well maybe that won't help than but it is worth a shot.
My e-mail address is jen@vbimail.champlain.edu
I have 4 - NW 6 and 1 - NW5 (which I'm upgrading next week) The problem is not specfic to the NW5 server though.
Here is what is happening incase you have any more insight:

Job Starts and formats my tape, connects with Nwagent, than does nothing. ArcServe Mgr. just shows waiting, NWagent shows that it was contaced w. job request. No errors except when I cancel the job (which I can only do by cancelling it from Nwagent) Error in NWagent Log is:


Job cancelled via NWAgent Console.
E16519: Failed to send packet, Connection terminated.
E16519: Failed to send packet, Connection terminated.

Everything will work fine one night but the next night nothing!
Thanks for looking abd sending me the old patch

TIA
Jen

 

[TheLad]

What Service Packs are we all running on NetWare? Also, SMDR & TSA versions. Has SMDR been setup correctly? What network speed/duplex are the servers running at and are they the same on all servers?

At my place, we have around 350 NetWare 5.1 SP5 servers. We run ARCSERVE.NLM Build 263.003 and NWAGENT.NLM Build 178.001. All runs ok bar the odd problemette. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[8arcserve]

SMDR is setup correctly and I'm also running the latest TSA's [TSA5UP11].
Have about 25 Servers running various version of Netware 5, 5.1 and 6.
The only difference from your setup is that I updated arcserve with the latest patchs QO33421 and QO33425. And thats when the problems started.
ARCSERVE.NLM Build 263.004 11/11/02
NWAGENT Build 272.001.000 01/16/03
So it looks like i'll have to re-install to a older version, if this is the case why have CA removed all updates for Arcserve7 netware from there site. The only updates on the support site are QO33421 and QO33425!!! and whats the point of unworking updates.

 

[TheLad]

You also need to check your network speed/duplex settings are the same on all servers (forced on the servers AND the network ports) and you also need to check your NDS replica situation.

CA say that a server running Arcserve should have a replica on - this is bollocks otherwise you could have replicas all over the place! For servers without a replica, you can use the SET NDS BOOTSTRAP ADDRESS command to specify the IP Address of a server where replicas reside. For example:

SET NDS BOOTSTRAP ADDRESS = 192.168.1.1:524

(you must include the :524 bit) -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[8arcserve]

I think you may have a good point, as the servers with out a NDS replica are the ones I'm having problems with.
As I understand it, the host server has to have a NDS replica .But I thought that this did not alppy to servers just running the nwagent. Well it did'nt until this latest update?
When using the SET NDS BOOTSTRAP ADDRESS command do I point to the server with the Master NDS replica.

I'll give your suggestion a try on monday morning, but I think this will turn out to be the problem.

Thanks TheLad

 

[jperleevt]

I'll give that a shot as well. I have got 2 good back-ups after back reving all servers to the previous verions of NWAGENT. Now I'm having a slowness problem, but at least I got a good full back-up!
Does the SET NDS BOOTSTRAP ADDRESS go into Autoexec.ncf? I also have the same questions about which server's IP address you use. Anyone that has a replicia or the master? I do have a replicia on my back-up server (at least I think I still do I recently switched some around).

Jen

 

[TheLad]

CA reckon you should have a replica on every server Arcserve is installed on - this is crap. If a server running Arcserve does not have an NDS replica, you can use the NDS BOOTSTRAP set command to point to a local server containing a replica (note: does not have to be the Master). This stops:

a) Arcserve server disconnecting from NDS causing queue errors and incomplete backups

b) Having an NDS replica nightmare with more replicas than you really need

c) Helps resolve some Arcserve abends.


Note: NWAGENT servers do not need replicas or the NDS BOOTSTRAP command set. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------