Netware 5.1 SP4 Warning

[8arcserve]

I have read in another forum and also personally fallen foul of Netware 5.1 SP4 on a server running Arcserve 7.

"We've had reported from customer who have applied SP4 ARCserve 7 backup
server. ARCserve 7 - even with the latest available patches - seems to
have serious problems with this service pack. These include abends in
the ASDB.NLM (possibly caused by some problem with NWSNUT)"

I personally had serious problems with Sp4, endless sms errors when backing up.
Back to SP3 ,fingers crossed.

 

[yvfwc]

Thanks for the info, even though it probably hurt...

Cheers,

Mark ;-)

 

[wwwscottcouk]

YES - DON'T DO IT

Had exactly the same problem....CA have admitted nothing (typical!)

Do not run nwagent 7 with nw5.1 sp4, IT WILL send your server into abend. You have been warned

 

[8arcserve]

http://Wwwscottcouk

so your saying that a Netware 5.1 SP4 server just running the NWAgent Client 7 will abend.
If that’s right ,I’m in trouble...
As all are Netware servers are running the NWAgent client 7 and all have been up dated to SP4.
This darn hateful little piece of software is getting close to the point of being utterly useless.
I’m currently re-building 4 Arcserve7 host servers as the network enginneer who did the upgrades to SP4 did not do the service pack backups, hence no roll-back.

 

[PezZ]

Hmm ... strange, for my 2 NW5.1 serves with nwagent 7, SP4 solved a long lasting problem of having to use way old SP1 nlm's that nwagent uses. I use nwagent.nlm dated 23.10.2001. The other version dated 30.04.2000 indeed does abend with SP4 but the newer one is just fine (except license errors & its ignoring the global file filter cause it thinks its invalid).

 

[LanAdminGeek]

Has anyone gotten Arcserve 2000 sp4 to restore to the Netware client agent by IPX? I worked fine at sp3.

 

[rmv]

If you do the restore through the client agent setup it does not work but if you drill down to the Network level and then select the server, right click the server tell it to use Client agent it works like a charm.

 

[lpphiggp]

There are patches available for NW5.1 SP4 and AS7.
The main thing however, is to disable the use of NWASPI from the startup.ncf, and let AS7 automatically use CANWPABD instead. Otherwise you'll run into a memory leak problem.

From CAI's website:
TO CONFIGURE CANWPABD (for use with .ham drivers only):

Edit the following line in the asconfig.ini (usually CSNLM6):

CSNLM6=SYS:\ARCSERVE.6\NLM\ASPIBD HOST=0 NAME=BOARD0
Change the line to read as follows:

CSNLM6=SYS:\ARCSERVE.6\NLM\canwpabd CLEAR
Save and close
Edit the astop6.ncf as follows:
Locate the line that says UNLOAD ASPIBD.
Go to the end of the line, hit enter to make room to enter a new line below.
Type in UNLOAD CANWPABD, save, and close.
Rename nwaspi so that it will no longer load and remove it from startup or autoexec.ncf.
After the next reboot of server, nwaspi will no longer load and we will use the new .cdm driver.

Give that a shot. Worked for us.