NetWare 6.5 server abends while upgrading to SP7 in ndsinit.

The server was upgraded to eDirectory 8.7.3 SP9 FTF3 in the past.

The server then abends sometime after the product CD is inserted during an upgrade from NetWare SP5 or SP6 to SP7.

Abend log shows the server abends in the NDSInit Process of DS.NLM while running the function GetConfigParm. Below is the sample output from an abend log:

Running process: NDSInit Process
Thread Owned by NLM: DS.NLM
Stack pointer: 88E18C30
OS Stack limit: 88E15000
Scheduling priority: 67371008
Wait state: 5050030 Blocked on Semaphore
Stack: 8BCF9812 (DS.NLM|GetConfigParm+D4)
--0000002D (LOADER.NLM|KernelAddressSpace+2D)
--00000008 (LOADER.NLM|KernelAddressSpace+8)
--88E16EAC ?
--0000002D (LOADER.NLM|KernelAddressSpace+2D)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000008 (LOADER.NLM|KernelAddressSpace+8)
--00000004 (LOADER.NLM|KernelAddressSpace+4)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--33333333 ?
--33333333 ?
--33333333 ?
--33333333 ?
--33333333 ?
--33333333 ?
--33333333 ?
--33333333 ?
--33333333 ?
--33333333 ?

One of the functions of the NDSInit function is to go thru the value chain of the server's permanent configuration parameters. Permanent configuration parameters are set on a server by server basis to either change or implement some of the more esoteric eDirectory features.

The problem here is that there were some permanent configuration parameters introduced in post eDirectory 8.7.3 SP9 DS.NLM modules. When NetWare 6.5 SP7 is applied the original DS.NLM contained in eDirectory 8.7.3 SP9 is laid down thereby backreving the newer module. This older module cannot parse the newer configuration parameters and abends the server.

This has been fixed in eDirectory 8.7.3 SP10.

When the issue occurs:

 

There are two ways to fix this issue if the server is not on the fixed version:

A. One is to create your own overlay by using the SP7 files then overwriting them with whatever 8.7.3 SP9 FTF was applied.

 

However, this is not a formally supported fix as these files were not used during SP7 installation testing..
B. It would be better to resolve this issue using perform the following steps:
1. Start the server with the following command " server -ndb"
2. Copy the DS.NLM from the eDirectory 8.7.3 SP9 FTF previously applied to SYS:\SYSTEM.
3. Reset the server.
4. Load up a browser and log into the server's iMonitor service (https://x.x.x.x:8009/nds)
5. Enable the Advanced Mode.
6. Go to Agent Configuration - Permanent Settings - Current
7. Make a note of all the settings that are optional (that have a red " X " next to them).
8. Delete all settings with a red " X ".

9. Restart the NetWare 6.5 SP7 installation.

10. After SP7 is installed and the server rebooted reapply the 8.7.3 SP9 FTF patch that was on the server prior to the SP7 installation.