Abend in CPU Hog Detected by Timer installing Novell BorderManager 3.9

Installing Novell borderManager 3.9, almost at the end of the installation, server will abend, but the install said it was done. After reboot server and went into IManager to configure my Site-to-Site VPN. It gave an error that I was not logged in as the correct user (I was logged in as admin) or that the schema was not extended.

Server xx_BRD39 halted Friday, xx xx, 2007 1:26:47.699 pm
Abend 1 on P00: Server-5.70.06-1937: CPU Hog Detected by Timer

Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = FBF17BC3 EBX = 944A14E0 ECX = 00000008 EDX = 93EFDC5C
ESI = 953E5BE2 EDI = 9541BF15 EBP = 93EFD17C ESP = 93EFD158
EIP = 00000000 FLAGS = 00000087


Running process: NWConfig Process
Thread Owned by NLM: NWCONFIG.NLM
Stack pointer: 93EFDA5C
OS Stack limit: 93EEDD20
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Stack: --FBF17BC3 ?
0036D853 (SERVER.NLM|ICmpB+12)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--944A14E0 ?
9434818C (NWCONFIG.NLM|ReturnInstallTokenType+3F7)
-953E5BDE (NWCONFIG.NLM|InstallTokenBuffer+1)
--9541BF11 ?
--0000000C (LOADER.NLM|KernelAddressSpace+C)
94357A8E (NWCONFIG.NLM|ParseCommandFileDescriptions+762)
--93EFD398 ?
--944A14E0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--944A14E0 ?
94357426 (NWCONFIG.NLM|ParseCommandFileDescriptions+FA)
-953E5BDE (NWCONFIG.NLM|InstallTokenBuffer+1)
--946F1E20 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--93EFD1F0 ?
--944A14E0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--944A14E0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--945F8040 ?
--93EFD3B4 ?
--944A14E0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--93EFD3B4 ?
--944A14E0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--944A14E0 ?
9434FF28 (NWCONFIG.NLM|InstallGetFileData+DD)
--93EFD214 ?
839D988B (ACPICA.NLM|AcpiExOpcode_2A_1T_1R+19F)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--000036AB (LOADER.NLM|KernelAddressSpace+36AB)
--00006B37 (LOADER.NLM|KernelAddressSpace+6B37)
--00000020 (LOADER.NLM|KernelAddressSpace+20)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--000004C6 (LOADER.NLM|KernelAddressSpace+4C6)
--3A535953 ?
--5359535C ?
--5C4D4554 ?
--45484353 ?
--565C414D ?
--43534E50 ?
--43492E48 ?
--00000053 (LOADER.NLM|KernelAddressSpace+53)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)

Additional Information:
The NetWare OS detected a problem with the system while executing a process owned by SERVER.NLM. It may be the source of the problem or there may have been a memory corruption.

Fixed in bm39sp1 support pack

As a workaround, edit the file sys:system\schema\vpnsch.ics with notepad or wordpad and look at the begging of the file for this values:

SetVar AdName, "adm.novell"
SetVar Password, "test"

Replace then with the right values for your server:

SetVar AdName, "admin name and context"
SetVar Password, "password"

Save the file and at system console run:
sys:system\schema\vpnextnd.ncf

That will extend the schema and will allow to configure the vpn in iManager. No need to reinstall NBM 3.9