From MicroFocusInternationalWiki
Jump to: navigation, search

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

This is a brief guide for installing this particular service pack. As time moves on, additional 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. 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.

The overlay CDs and DVD for SP7 were released on 5 October 2007 as part of the release of OES2 (Open Enterprise Server 2) and the standalone version for updating existing NetWare 6.5 servers was released on 9 October 2007, about 11 months after SP6.

This service pack has been seen to be quite stable. A modest number of updates are listed below. Pending SP8's appearance, using this SP is strongly recommended in the forums (except for some pre-migration server setups, due to eDir version considerations).

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

Warning.gif Warning: To update existing servers, you should not use the overlay CDs or DVD, but only the standalone version NW65SP7.zip. Novell does not officially support upgrading existing servers using the SP7 overlay CDs or DVD.

What's new in SP7

beside the usual patches and fixes, the following changes in functionality or major updates are included in SP7:

  • for new installs, the SP7 overlays will now install eDirectory 8.8 SP2 (previously, the overlays always installed eDirectory 8.7.3.x). A support pack install will not upgrade your eDirectory to 8.8.2 but instead just patch it to the latest 8.7.3.x patch level.
  • The overlay version of SP7 can be installed as a virtual machine under Xen on a SLES 10 SP1 server
  • SP7 includes iManager 2.7. iManager 2.7 includes some significant enhancements like a full tree view and support for browsing the file system and managing files system rights. iManager 2.7 will only be installed automatically if you have been using iManager 2.5 or 2.6 before. If the server is still running iManager 2.02, then iManager will not be upgraded. For more information, see http://www.novell.com/documentation/oes2/inst_oes_nw/data/buymz1k.html#b6xhr3v
  • Support for Windows Vista in iPrint. Vista does not yet support all features that exist for XP workstations. For details, see http://www.novell.com/documentation/oes2/iprint_nw/data/boeyh9p.html#bbn7dyz
  • the overlay CDs are no longer supported for upgrades from previous NetWare versions. If you want to upgrade a NetWare 5.1 or 6.0 server to 6.5 SP7, you will first have to upgrade with an SP6 overlay CD and then install SP7 on top of it. For details, see http://www.novell.com/documentation/oes2/inst_oes_nw/data/buymz1k.html

Installing NW65 SP7

Besides including all the post SP6 patches released prior to SP7, it also includes new functionality for a number of products included with NetWare 6.5.

Downloading SP7

The main download URL for SP7 is http://download.novell.com/Download?buildid=vAIyb4R70b4~ this is the file you need to update existing servers.

If you want to install new servers using the overlay CDs that include SP7, either use the 2 CD images NW65OSSP7.iso and NW65PRODSP7.iso or the DVD image NW65SP7_OVL_DVD.iso available at http://download.novell.com/Download?buildid=GsODlkBPM2g~

Expand the Service Pack

Just like SP6, NW65SP7 is being distributed as a ZIP file called NW65SP7.ZIP. This is very convenient as you can now extract it on any platform that has a tool to unzip files. For instance, you can copy NW65SP7.ZIP to a remote server and then run UNZIP.NLM from the server console to unzip it. It is recommended to unzip 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 NW65SP7.

Verify SERVER.EXE is present

Some Antivirus software is configured to consider any .EXE file to be potential spyware and will not allow it to be written to a directory called STARTUP. McAfee VirusScan is well known for this. Verify that the file is present where it should be, under nw65sp7\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.

Disable Transactions on NSS volumes

Sticky.gif Note: This recommendation was true for SP6. I don't know if the NSS code in SP7 changed to handle the TTS format change more gracefully. Just to be safe, turn off TTS and you are sure to not have any problems.

Warning.gif Warning: Not all volumes have the transactions tracking system enabled!! You should not have the transactions tracking system enabled on both traditional and NSS volumes at the same time!!Read Novell documentation on when and why the transactions tracking system should be enabled or disabled on a volume!! You should verfiy which volumes have the transactions tracking system enabled before using the disable command !!!.

In some cases, the server may abend at startup because of incompatibilities in the transaction tracking system between SP6 and earlier versions. This is documented in TID3463889. If you are not yet on SP6, to avoid this problem, you should disable the transaction tracking system prior to installing SP7 by using the console command:

NSS /NoTransaction=ALL

If you want to upgrade from SP6 to SP7, this problem should not affect you.

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 SP7 will be made. You can later back out SP7 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 BACKSP7 directory later if you see that you don't need the backup. If you apply SP7 several times, you should only use the backup option on the first SP7 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 SP7 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 SP7 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 SP7 to update your drivers, but you should also take advantage of the SP install to check your hardware vendor for updated drivers and firmware.

Do you want to install iManager plugins now?

An iManager without plugins is of little use. As such, you really need the plugins to work with iManager 2.7. However, the plugin installation part of the SP7 install is by far the longest part of the whole install. So if you have limited time to install SP7, then you might decide to install SP7 without the iManager plugins and install the plugins later on. In normal cases you should always select the option to install the plugins.

Reboot the server after copying files?

You should install SP7 when users are not working on your server and you should reboot after installing the SP. Enabling the reboot option will cause the server to reboot 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 SP7 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.

If you get any Public Symbol errors, the problem is almost certainly that Server.exe failed to upgrade; or it did not extract from the SP7 .zip file (see "Verify SERVER.EXE is present" section above), or it failed to overwrite the previous version on the server you are upgrading - this can happen if the previous server.exe has somehow acquired a newer file date than the one from SP7

Fix and reenable the transaction tracking system

Warning.gif Warning: Not all volumes have the transaction tracking system enabled!! Only enable the volumes that you disabled before installing SP7!!! You should not have the transaction tracking system enabled on both traditional and NSS volumes at the same time!! Read Novell documentation on when and why the transaction tracking system should be enabled or disabled on a volume!! .

To avoid potential problems with the transaction tracking system causing future abends as described in TID3463889, delete the file UXACTION.LOG from the root of every volume on your server where the file exists. If you need transaction tracking on one of your volumes, you can enable it again using the following command:

NSS /Transaction=volumename

Special considerations for nw65os6a.exe

If you had the nw65os6a.exe patch installed prior to installing SP7 on your server, then it is possible that you get the following error message while the server tries to load portal.nlm:

server-5.70-918 Loader cannot find public symbol: GetMachineOwner for module portal.nlm, error processing external records.

Also, if you type VERSION at the server console, the server will still report SP6. This problem is caused by the fact that the server.exe file from nw65os6a.exe is newer than the one from SP7 but functionally only corresponds to SP6. Given server.exe is not an NLM, the installation program can only replace the file by date and not by version and so it skips updating this file. The solution to the problem is to manually copy the server.exe file from SP7 to c:\nwserver

Post SP7 Patches

The first 4 patches (DNS, NTP, TCPIP and Winsock updates) are considered to be "recommended" patches by Novell, and should be installed no matter what other patches are installed.



Fix for security vulnerability in NetWare DNS

Network Time Protocol (NTPv3) XNTPD.NLM update (RECOMMENDED)


Updated NTP module to address two issues found after NetWare 6.5 SP7 shipped.


  • Novell Remote Manager - Diagnose Server - Health Monitor - NTP Monitoring Service points to an invalid link.

(Nothing displays)

  • Novell Remote Manager - Manage Applications - NTP Configuration - does not show the ntp.conf file edit screen.

TCPIP update (v6.81k) (RECOMMENDED)


This update fixes the 'Bad Resource Tag passed to LSLReturnRcvECB' abend that occurs when using SP7 on a server running BorderManager.

Winsock Suite update (v 6o) (RECOMMENDED)


Updated Winsock suite may be used with minimum NetWare 5.1 SP8, Netware 6.0 SP5, and Netware 6.5 SP6. Patch includes updated NILE.NLM based on OpenSSL which requires updates in WSPSSL to work correctly. The NILE update is for NetWare 6.5 SP6 only.

Several ABENDS fixed

Note: If applying this patch to a server that has SP7 applied, you may get an error saying that it cannot be applied to this version. (This Patch needs minimum Netware 6.5 SP6. Please apply the necessary Support Pack and re-start this install). This refers to the NILE update which is already in SP7, not the Winsock patch.

COMN.NSS update for OFM


This patch fixes an abend that occurs when using Symantec's BackupExec with St. Bernard's Open File Manager (OFMCDM.CDM).



scsihd-sp7b.zip contains a further updated SCSIHD.CDM to address a few issues post NetWare 6.5 SP7. Most importantly, a workaround for SCSI bus issues encountered in VMWare ESX 3.x when using the LSI driver, and a separate issue with Emulex LightPulse Fibre Channel (LPFC) Host Bus Adapters in a cluster. See the above link for details.

USB driver update


This patch contains updated USB drivers that fix the problem of Dell Poweredge x9xx servers with a version 2.x BIOS hanging upon shutdown. The problem is described in the following TID: https://secure-support.novell.com/KanisaPlatform/Publishing/577/3197913_f.SAL_Public.html

Note that the problem is not specific to SP7 but has only been discovered after the release of SP7.

iPrint update (iprntnw65sp7b)


Updated iPrint modules (NDPSM.NLM, NDPSGW.NLM, and IPPSRVR.NLM) for NetWare 6.5 Support Pack 7.

This update is intended for servers running NDPS or iPrint on NetWare 6.5 Support Pack 7. This update is also recommended for servers running Support Pack 6 and encountering the problem documented in TID 3842033.

This fixes an ABEND issue when attempting to install iPrint printers to or printing to iPrint printers from openSUSE 11.1 and SLED11.

Fixes issue with Macs running 10.5.2 and Security Update 2008-02 abending the server.


CLIB and DSAPI Libraries (nwlib6L)


This new L version of this patch fixes two communications-related abends.

NSS update (n65nss7a)


This file contains updated NSS modules for NetWare 6.5 Support Pack 7.

For servers running Novell's NFS Gateway product, this NSS update will necessitate an update to the module NFSGY.NLM. Before applying the NSS update, make sure to download and apply NFSGY657A.ZIP.

NSS issues fixed after the release of NW65SP7:

1. Fixed an issue where a DFS split of a volume (SYS in this case) would hang at 100%.

2. Fixed an issue where directory create events were not being reported or logged correctly.

3. Fixed an abend in COMN.NSS|VAUTH_UnpackAuthBeast+3E9.

4. Fixed an abend while reactivating a pool.

5. Fixed possible abend issues where data sizes were incorrect.

6. Fixed an abend in COMN.NSS|POOL_BstNew for a BCC cluster.

7. Fixed an abend in COMN.NSS|VAUTH_MayIDoThis+1D5 for a BCC cluster.

CIFS issues fixed after the release of NW65SP7:

1. Fixed an issue where customers were unable to logon to a NetWare CIFS domain as a user from a Windows 2003 server.

2. Fixed an issue where CIFS would abend while freeing TCP sessions.

3. Fixed a CIFS PDC user search that appeared to never end.

4. Fixed an issue where an NBNS Name Query failure causes a CIFS clustered resource to be unavailable by name for drive mapping.

5. Fixed a CIFS security issue with the DCERPC stack relating to a buffer overflow allowing code execution.

6. Fixed an issue where a NetWare CIFS PDC is searched from a Windows server and only returns 10 domain groups.

7. Fixed an issue where copying files did not update the file's Last Accessed time attribute.

Post SP7 known issues

Plugins incompatible with iManager 2.7 (Bordermanager)

If you have products like Bordermanager for which there are no iManager 2.7 plugins available yet, the fact that SP7 installs iManager 2.7 can create the bad situation that you can no longer manage your product. Fortunately however, the SP7 install does not touch your previous iManager installation. iManager 2.7 is just installed in parallel and the Apache2 httpd.conf file is updated to disable the old iManager and enable the new iManager installation. You can very easily revert to your previous iManager installation as follows: Edit the file httpd.conf in sys:apache2 and towards the end of the file, comment out the line:

Include sys:/tomcat/5.0/conf/nps-Apache.conf

and re-enable the line:

Include sys:/tomcat/4/conf/nps-Apache.conf

Now, from the server console, reset your Apache2 using the command AP2WEBRS and now your iManager link will again bring up your previous iManager installation. If later on, you want to switch to iManager 2.7 again, just reverse the operation again.

This will only work if you updated an existing NetWare 6.5 server to SP7. When installing a new server using the SP7 overlay CDs, there is no old iManager installation which you can go back to. To work around this, you can install iManager 2.6 on a Windows PC and then authenticate it to the NetWare server.

NOTE: When switching back to iManager 2.6 you may need to clear your IE browser history/cache and off-line files - especially if you logged into the 2.7 instance. If you switch back to 2.6 and receive "System Error - The system encountered an unknown error. Please contact Novell Support." when you attempt to login, clear your browser cache, including offline files and try again.

NOTE: There seem to be Bordermanager 3.9 plugins for iManager 2.7 available now BM39_IMAN27

Tomcat doesn't work as a standalone server

Broken CoyoteConnector. The fix will be included in SP8. To work around this, you can use HttpConnector TID3017232.

Protected memory space console commands

The "RESTART" and "ADDRESS SPACE=" options can no longer be used together with the LOAD command. E.g. a command like the following are no longer recognized:


This change in behaviour was the result of fixing a bug in the command line decoder for the load command. Instead of the line above, you should now use one of the following 2 possibilities:

  • Omit the "ADDRESS SPACE=" option.

This of course has the disadvantage that you no longer control the name of the address space, but it gets a name automatically generated by the OS

  • Use 2 separate commands to load the NLM and to make it restartable

Note that the syntax "LOAD RESTART ADDRESS SPACE" was never an [officially documented] syntax and just happened to work by chance before SP7. According to the documentation, the options "PROTECTED", "RESTART" and "ADDRESS SPACE" are mutually exclusive. The "wrong" usage is very common among Groupwise installations, probably because of TID2953603.

BorderManager transparent proxy no longer works

BorderManager Site-to-Site VPN connections to SKIP Slaves will fail

There's no known workaround for this currently, and it's likely the best idea to get rid of any leftover SKIP slaves in a Bordermanager S2S setup.

Bad Resource Tag passed to LSLReturnRcvECB abend

This bug related to the TCPIP protocol stack mostly happens on BorderManager servers, but might hit non BorderManager servers as well. The bug is documented in TID3754180. The TCPIP update mentioned above fixes this abend.

Public symbol errors in PORTAL.NLM

On some servers, after installing SP7, PORTAL.NLM fails to load with public symbol errors. This is caused by SP7 not having installed the updated server.exe. This problem has been seen sporadically and independently of the McAfee issue. The exact circumstances that lead to the issue have not been found yet, but the issue is easy to fix: Either install SP7 again (do not use the backup option on the second install), or manually copy the server.exe file from SP7 to the server's c:\nwserver directory.

BackupExec OFM does not work with SP7

The open file manager from BackupExec is not compatible with SP7 and causes page fault abends during backup. The COMN.NSS update mentioned above will fix this abend.

DNS Name resolution problems after applying SP7

There is at least one confirmed issue regarding Name resolution in SP7, where ping commands to known good DNS names will fail, claiming that the name cannot be resolved. An nslookup for the same name will be succesful though, and oddly, also an iptrace to the same name will work fine. Another affected piece is timesync, which will fail to resolve DNS names suddenly. The reason for this seems to lie in winsock. LAN traces show that the server will always attempt to resolve every name with it's configured local DNS name (as configured in sys:\etc\resolv.cfg) appended first. Only if the nameserver responds with an error on that request, the server will then attempt to resolve the correct name without it's own domain appended. Some nameservers however do not respond with an error if the local domain is valid, but will simply respond with an empty resource record. In that case, the server will never attempt to resolve the proper name, and resolution will ultimately fail.

After more than a year uptime iManager 2.7 causes Cluster Server Abend

Warning.gif Warning: Do not use iManager 2.7 Volume browse feature on NW6.5 cluster nodes which have an relatively old patch level. In our case SP3

Very enthusiastic about the new tree view feature of iManager 2.7 i've started browsing some of our NW6.5SP3 Servers NSS Volumes. On a single Server it wasn't a problem but trying to view the directory structure of our cluster volumes causes the following abend on the cluster node which held the resource and the cluster volume went to comatose state.

  Novell Netware, V6.5 Support Pack 3 - CPR Release
  PVER: 6.50.03
  Server XXXXX36 halted Tuesday,  4 December 2007 
  Abend 1 on P00: Server-5.70.03-0: NCPIP: ReplyDisgard overflowed reply buffer!!
  EIP in NCPIP.NLM at code start +000032F8h
  Running process: Server 00:51 Process
  Thread Owned by NLM: SERVER.NLM

I assume that the cause of the abend may be because of the patch level of our NetWare 6.5 Cluster Servers. It's still SP3 at the moment.

NetWare module GAMS.NLM will be backrev'ed

Installing either NetWare 6.5 Support Pack 6, NetWare 6.5 Support Pack 7 or Novell eDirectory 8.8 on a Novell Netware 6.5 Server with Service Pack 5 will backrev module GAMS.NLM ver. 1.30 Tuesday, 5 July 2005 to GAMS.NLM ver. 1.20 October 8, 2004.

NetWare Remote Monitor IP Restrictions cannot be modified after SP7

NRM will not allow changes in the "Access IP Address Access Control Page". Clicking "Save" or "Remove" simply returns to the configuration page without saving the modifications.

==ZENworks Server Management 7 may hang on cleanup process after startup and cause shutdown of the ZSM process.

Common questions

Here are a collection of questions related to SP7 that have been asked in the forums, and the current answers to them. See The Netware Forum Directory

Can I use the SP7 overlay CDs to install eDirectory 8.8.2?

Answer: No!
To install eDirectory 8.8.2 on an existing server, you have to use one of the 2 download versions of eDirectory 8.8.2. Either the ISO version at http://download.novell.com/Download?buildid=7hvDT3VNzNw~ or the regular version at http://download.novell.com/Download?buildid=Hy6G7XZcNXg~

Can I apply TCP680B.EXE.ZIP on top of SP7?
The TCP680B patch appears to be newer than the TCPIP files from SP7. Can I apply this patch on top of SP7?

Answer: No longer!
The TCP680B patch is based on the v6.80x TCPIP code base from SP6. SP7 contains a newer v6.81x code base. As such, the TCP680N patch has never been intended to be used on SP7 servers. This update was temporarily recommended as fix to the abend issue described in the previous section. However by now, there is the TCP681j.exe update at http://download.novell.com/Download?buildid=aRl9LgVUbTw~ which should be used instead.

Will Novell fix LOAD RESTART ADDRESS SPACE issue? when? Have SP5 servers waiting for update..

Answer: The fix will be included in SP8.
However given that you just need to change your load commands, this problem should not prevent you from using SP7 now.

Additional Information

Novell has a very interesting but little know piece of documentation on NetWare called the Server Operating System for NetWare Administration Guide. This does not just include the new features Novell added in each support pack, but it also gives a lot of background information on NetWare and documents little known aspects of NetWare.