- 1 Installing NW65 SP4a / OES-NW SP1a
- 2 Post SP4a Patches
- 3 Post SP4a Known Issues
Installing NW65 SP4a / OES-NW SP1a
This is a brief guide for installing this particular service-pack. As time moves on, post-SP patches will be added to this document. The information here is gleaned from Novell provided information, and the collective wisdom of the Support Forums.
Expand the Service Pack
Expand it somewhere you have space. Like the README says, this should be done at the root-level of whichever volume you use since path-lengths can get long.
Verify SERVER.EXE is present
Some Antivirus software is configured to consider SERVER.EXE to be spyware and will not allow it to hit disk. McAfee VirusScan is well known for this. Verify that the file is present where it should be, under nw65sp4a\STARTUP\SERVER.EXE. For details on this problem go here.
Unload java on your target server
Since the SP updates java, it needs to unload it. Java has a tendancy to not want to unload, so it will make your life easier if it is unloaded before you start. This may require a reboot to make happen. In extreme cases, AUTOEXEC.NCF may need to be modified so that JAVA doesn't start at all (Tomcat, Zen Agents, power monitors, and such).
Load NWCONFIG and apply the service pack
The method for installing a service pack through NWCONFIG is well documented in the README.
Reboot & fix missed files
SP4a didn't fix all of the known problems with SP4. There are still a few things that need to be hand fixed. Most of this is from TID10098928
If you applied NWLIB6D, Copy w65sp4a\SYS\SYSTEM\DSAPI.NLM to SYS:SYSTEM\DSAPI.NLM
If you applied edir8737, copy the DSLOADER from that patch over the one installed in the service pack. This file is located in C:\NWSERVER, not SYS:SYSTEM
Like SP3, the version that comes with the service-pack doesn't work quite right. It performs fine, but it doesn't report to SLP the way it should. If that is important to you, use the SP2 version of RCONAG6.NLM. Unlike the SP3 version, if you've already loaded this, you can unload it and reload it with the SP2 version and things will turn up in SLP.
If you applied TSA5UP18, verify that the files are the SP versions and not the TSA5UP18 versions. For details, see the TID
Reboot & Verify services
Reboot like you should and make sure things are working. If you had to uncomment things to get java unloaded, put them back here. If you've made any hand-edits to files such as httpd.conf verify their state before putting the server back into production.
Post SP4a Patches
So far, none are recommended.
Post SP4a Known Issues
There are known issues with memory tuning and a new SERVER.EXE patch is expected at some time. The SERVR.EXE file from SP5 can help in some cases. Look for a patch addressing this. In the mean time, check out the memcalc tool to help minimize the problem.