NetWare 6.5 Support Pack 4 file mixup

  • 10098928
  • NOVL103490
  • 19-Sep-2005
  • 19-Oct-2005

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Goal

NetWare 6.5 Support Pack 4 file mixup

Fact

Novell NetWare 6.5 Support Pack 4

Note

While the abstract for NW65SP4A does not specifically state this, installing NW65SP4A over the top of an existing install of NW65SP4 will fix the issues indicated below as resolved. 

Fix

There was an inadvertent mixup in the build process for some of the files that are included in post-NW65SP3 patches and the current shipping NW65SP4.  Here is a list of those files and how to make sure the most current ones are being loaded on the server:

Issue 1 -  DSEVENT.NLM  has a file date of 11/18/2004 in the NWLIB6D.EXE patch.  In NW65SP4 it has a file date of 1/15/2005 however the version is lower than that of the NWLIB6D patch.  This is a build issue and the one in SP4 is the most current one.  Because the SP4 installer performs date and version checking and the build engineer didn't correctly bump the version number, the correct file may not be installed during the SP4 install process.  You will need to manually copy this file to your server if this is the case.  The file can be found in the nw65sp4\SYS\SYSTEM directory.

This has been resolved in NW65SP4a  - see the abstract later in this document

Issue 2 - DSAPI.NLM also has a newer file date in NW65SP4 but a lower version than that in NWLIB6D.EXE.  Again this is a build mixup and the file in SP4 is the most current.  Again, because the SP4 installer performs date and version checking and the build engineer didn't correctly bump the version number, the correct file may not be installed during the SP4 install process.  

While the dates are different, the code is exactly the same.  There is no need to do any file copy for this file.  The date / version issue will be resolved in NW65SP5

Issue 3  - TSA5UP18 had significant customer fixes which simply carried forward into SP4.  However support for backing up hard links on Linux was added which should have caused a version bump to be done.  The current files are those included in SP4.  If you have applied TSA5UP18 to your server, you will need to examine the files between your server and the SP4 installer and make sure that the SP4 files are installed since those are the current ones.  This applies to QMAN.NLM, SBCON.NLM, SMDR.NLM, SME.NLM, SMSUT.NLM, TSAFS.NLM (in SYS:SYSTEM) and their accompanying *.MSG files (in SYS:SYSTEM\NLS\4).  If you use the TSAFSGW.NLM, it too should be checked.  Also, NWTAPE.CDM (in c:\nwserver\drivers) should be checked as well.

While the file versions and/or dates did not change for the files included in TSA5UP18, those files installed with SP4 and SP4A are the correct code.

Issue 4 - PORTAL.NLM has a version number of 4.00.01 in NW65OS3A and 3B.  In SP4 it has a version number of 4.00 causing the support pack install script to skip installing the SP4 file as it thinks it is older.  However, the portal.nlm from the SP4 really is the newer one (it has the cascading menu).  You will need to manually copy the version from sp4 manually from nw65sp4\SYS\SYSTEM to your server.

This has been resolved in NW65SP4a  - see the abstract later in this document

Issue 5 - The FILESYS.NLM file in FLSYSFT12.EXE has a version of 5.12 and a date of August 10, 2005.  It also has a CPR designation.  In SP4 it has the same version but a date of August 15, 2005.  Again a version bump should have occurred and was overlooked.  The current file is the one included in SP4.  Again, because the SP4 installer performs date and version checking and the build engineer didn't correctly bump the version number, the correct file may not be installed during the SP4 install process.  You will need to manually copy this file to your server if this is the case.  The file can be found in the nw65sp4\STARTUP directory.

This has been resolved in NW65SP4a  - see the abstract later in this document

Issue 6 - The NCP.NLM from NW65SP3NCP.EXE has a version of 5.60 and a date of May 13,2005.  In SP4 it has the same version but a date of May 9, 2005.  This file should have had both a version bump and a time and date stamp reset.  The file in SP4 is the most current.  Again, because the SP4 installer performs date and version checking and the build engineer didn't correctly bump the version number, the correct file may not be installed during the SP4 install process.  You will need to manually copy this file to your server if this is the case.  The file can be found in the nw65sp4\STARTUP directory.

This has been resolved in NW65SP4a  - see the abstract later in this document 

Issue 7 - There was also an inadvertent mixup in the build process for some of the files between  eDir 873 SP7 and NW65SP4.

NW65SP4 includes an older version of NILE.NLM (6.05.03 9/20/04).  eDir 873 SP7 has a newer one ( 6.08.05 4/08/05).  While NW65SP4 installs eDir 8.7.3.7, the edir8737.exe patch should be downloaded and NILE.NLM manually copied to the file server to complete the upgrade process.  Be sure to copy security\secupd\NW\startup\nile.nlm,  not security\secupd\nw\NW56\startup\nile.nlm as they are different files (the ..NW56..  version is for NW5.x and 6.0).

This has been resolved in NW65SP4a  - see the abstract later in this document

Issue 8 - In addition, DSLOADER.NLM has different build numbers and dates;  NW65SP4 contains 10551.69  (1/11/05) and 873 SP7 contains 10552.66 (5/9/05).  This file should also be manually copied over from the edir8737.exe patch in order to have the most recent and up-to-date file on the server.  Note that this file is in the EDIRCORE\SYS\SYSTEM subdirectory in the patch file but is copied to the C:\NWSERVER directory on the file server.  Do not copy this file to SYS:\SYSTEM as it will not be read from there.

This has been resolved in NW65SP4A - see the abstract later in this document 

.

NW65SP4a Abstract

NetWare 6.5 Support Pack 4a was released to resolve the following:

 - Resolved Abend when using Salvage.
 - Resolved a data corruption issue when doing a rebuild on NSS pools.
 - Updated print driver so Nterprise Branch Office can upload printer drivers.
 - Resolved Nessus scan abend.
 - Corrected file version inconsistencies for eDirectory 8.7.3, NCP.NLM,     FILESYS.NLM, PORTAL.NLM, and DSEVENT.NLM.

If nw65sp4.exe or the Overlay version was used to update a server, do the following:

 - Apply n65nss4b.exe "2972385" or most current version of n65nss4*.exe.
 - To correct the module inconsistence, see TID: 10098928.
 - Download btcpcom.exe 2966492 and copy BTCPCOM.NLM from the v7.9 folder to  sys:\system