From MicroFocusInternationalWiki
Revision as of 21:15, 1 November 2007 by Snidelydev (Talk | contribs) (Fixed an mdash)

Jump to: navigation, search

Sticky.gif Note: SP5 has now been superceded by SP6.

Sticky.gif Note: SP6 has now been superceded by SP7.

NW6.5 SP5 is now quite out-of-date, but because a properly patched SP5 is quite stable for most customers, and because many customers have a requirement of "all deliberate speed" in moving to new service packs, it seems appropriate to capture the folklore of this version in the wiki format SP6 (and now SP7) have found so useful.

This is a brief guide for installing this particular service-pack. Certain post-SP patches have been added to this document. The information here is gleaned from Novell-provided information, and the collective wisdom of the Support Forums. Feel free to edit this page if you find errors or if you have additional information to provide. However if you have questions or comments, please post them on the discussion page.

Since the Service Pack was released, new patches have come out. The Service Pack as first shipped had a few major bugs in it.

Sticky.gif Note: While this article talks about applying SP5 to an existing servers, the patches and known issues sections do also apply to new servers installed with the SP5 overlay CDs or DVD.

Installing NW65 SP5

Besides including all the post-SP4 patches released prior to SP5, it may also include new functionality for a number of products included with NetWare 6.5.

Downloading SP5

The main download URL for SP5 is http://download.novell.com/tbd — this is the file you need to update existing servers.

If you want to install new servers using the overlay CDs that include SP5, use the 2 CD images.

Expand the Service Pack

Like previous support packs which were distributed as DOS/Windows executable files, NW65SP5 is expanded by running a DOS window on a workstation, usually using a mapped network drive (otherwise you have to copy the expanded files to the server). It is recommended to expand the support pack to the root of one of the server's volumes - it does not have to be SYS. All the support pack files except for the readme will then be in a subdirectory called NW65SP5.

If you choose to expand the files on a workstation and transfer them to CD for use in multiple server locations, note that you will need 2 CDs. As with the bootable ISO CDs, it works out well to put the PROD subdirectory on the 2nd CD. If you really need to use just 1 CD, some operators have removed language files that they don't expect to need.

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 nw65sp6\STARTUP\SERVER.EXE. With some unzip utilities, the symptom of the problem is that you get asked for a password to unzip the file. However the zip file is not password protected.

For details on this problem go here.

Load NWCONFIG and apply the service pack

The method for installing a service pack through NWCONFIG is well documented in the README. Here are just some comments on the questions asked during the SP install

Backup files replaced by NetWare Support Pack?

If you reply "yes" to this question, a backup of all the files replaced by SP6 will be made. You can later back out SP5 if you did the backup. I would strongly recommend always selecting the backup option unless you really have too little space left on your SYS volume. You can always delete the BACKSP6 directory later if you see that you don't need the backup. If you apply SP5 several times, you should only use the backup option on the first SP5 install and disable it on later installs.

Do you want to Update the Storage/LAN/PSM/WAN drivers currently in use?

It is highly recommended that you always enable the option to update drivers. People are often reluctant to enable this option because they are not sure the drivers included with SP5 do really work with their hardware. This however leads to many people having subtle problems later on because of outdated drivers. While it sometimes happens that drivers included with SP5 are incompatible with the hardware being used, the failure is generally immediate and you can manually backrev the specific driver that failed. If you don't use the driver update option, you will also miss out the important updates on Novell drivers like IDEATA.HAM, IDECD.CDM and SCSIHD.CDM. Generally, you should not just allow SP5 to update your drivers, but you should also take advantage of the SP install to check your hardware vendor for updated drivers and firmware.

Reboot the server after copying files?

You should install SP5 when users are not working on your server and you should reboot after installing the SP. Enabling the reboot option will cause the reboot to occur automatically after the SP install. Note however that open files can force you to confirm the reboot on the server console.

Login prompt

The main purpose of the login prompt is to extend the schema of your tree. That means the user you specify at the login prompt should not just have supervisor rights to this server, but it needs supervisor access to the root of the tree, at least for the first SP6 you install into your tree.

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 SP5 Patches

  • NW65SP5UPD1.EXE (url tbd)

This contains both an important server.exe update ("CPR") and an important NSS update. If you don't install any other patches, INSTALL this pair.


nw65os6a.zip addresses an abend issue in _SchedGetReadyThread (below) and includes a server.exe for both SP5 and SP6.

Post SP5 known issues

SP5 has a few very annoying but easy to fix issues.

The most famous, shared with SP3 and SP4, is the short term memory issue. This involves automatic tuning gone awry, and while many people never saw the issue for some people it had major impact. Systems with 3G or 4G of main memory seemed to be the most affected.

Abend issues

At this time, there are at least n common abend issues in SP5.

Page Fault abend in _SchedGetReadyThread

See TID 3200596 and the above nw65os6a.zip.

Universal Password considerations

The following applies mainly to people who initially installed their server as NetWare 6.5 before OES was released (i.e. before SP3) and implemented Universal Password at that time. With the initial release Universal Password was managed with a couple of default password policies and iManager had a Universal Password option in the NMAS menu. Starting with OES and the inclusion of IDM2 components, Novell switched to the more elaborate password policy management found in the Password menu in iManager. However many people are not aware of these changes and continue to use the old method. It's only with the release of SP6 where Novell includes new iManager plugins that people suddenly see their Universal Password menu option disappear and they are wondering how to manage Universal Password now.

The proper way to proceed is now documented in the Novell Password Management 3.1 documentation and especially in section 3.3.1.

Driver issues

See the NBI patch above if you have a Perc 5/RAID controller.

DST Java issues

  • NW65SP5 does not contain any Java updates that fix the Java DST issues. Furthermore, the various java update methods for making it DST ready do not leave a version stamp in the product database. As such, if you applied any Java patches before SP5, install SP5 will overwrite those Java patches and will revert your Java to a non DST ready version. This applies both to the server and the ConsoleOne versions of Java.

See The wiki page [DSTshift] for more details about DST updates.

SixFive Documentation

Browse to


(this applies to all versions after SP3)

Room for Corrections

Looking forward to the sysops' notes on this page.