I have not been able to launch NSMAdmin.exe without an abend in HTTPSTK
and LIBC on the server.
The server is running NW6.5 sp6 and EDIR 87.3.7.9 (same problem on sp5 and
EDIR 87.3.7.8). I am able to run NIRMAN ok on port 8008 and 8009.
I have unloaded a number of other NLM's that use HTTPSTK eg, IPMCFG,
NIRMAN, XVESA, TCPSTATS and NDSIMON in an attempt to isolate a conflict or
change the resultant abend log but the log is basically the same.

Since I don't see anybody else having this type of problem in the forum it
must be a configuration issue at my end. The reason I think that could be
possible is due to a non default NetStorage setup found when fixing
NetStorage 403 errors when running servlets. Strangly the NetStorage was
supposed to be a vanilla install of NetStorage but directories were not
where they were supposed to be.

My question is how is the NMSAdmin login different from NIRMAN and what
config files does it use on the server to interface with the FSFENGIN.NLM
so I can chase down what else is wrong.

Abend log added for reference.

Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.06

Server BACKUP halted Tuesday, 14 November 2006 10:28:42.296 am
Abend 1 on P00: Server-5.70.06: Page Fault Processor Exception (Error code
00000000)

Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = 00000000 EBX = 00000000 ECX = 00000000 EDX = 94CD1A60
ESI = 9C57D000 EDI = 9C57D121 EBP = 94CD1A4C ESP = 94CD171C
EIP = 80895D30 FLAGS = 00010046
80895D30 0FB601 MOVZX EAX, byte ptr [ECX]=?
EIP in LIBC.NLM at code start +00095D30h
Access Location: 0x00000000

The violation occurred while processing the following instruction:
80895D30 0FB601 MOVZX EAX, byte ptr [ECX]
80895D33 3C41 CMP AL, 41
80895D35 0FB61A MOVZX EBX, byte ptr [EDX]
80895D38 7206 JB 80895D40
80895D3A 3C5A CMP AL, 5A
80895D3C 7702 JA 80895D40
80895D3E 0420 ADD AL, 20
80895D40 80FB41 CMP BL, 41
80895D43 7208 JB 80895D4D
80895D45 80FB5A CMP BL, 5A



Running process: httpexpThread8 Process
Thread Owned by NLM: HTTPSTK.NLM
Stack pointer: 94CD10A0
OS Stack limit: 94CCA980
Scheduling priority: 67371008
Wait state: 5050090 Wait for interrupt
Stack: --00000000 (LOADER.NLM|KernelAddressSpace+0)
98127440 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--94CD1A60 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--696D6441 ?
--74492E6E ?
--94CD1900 ?
00361932 (SERVER.NLM|FunnelingWrapperReturnsHere+25)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--FFFFFFFF ?
--00000092 (LOADER.NLM|KernelAddressSpace+92)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
8F22358E (CLNNLM32.NLM|NWCImportSymbol+3E)
--8F15AD20 ?
--94CD175C ?
--5F4D4109 ?
--65764550 ?
--0000746E (LOADER.NLM|KernelAddressSpace+746E)
--95D86640 ?
--00001B2F (LOADER.NLM|KernelAddressSpace+1B2F)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--42CFB8B0 ?
--3A0ABCD8 ?
-00576EE6 ?
--13BD510E ?
--970F7C6D ?
--86CE94B7 ?
--2371E93C ?
--DF978E65 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000063 (LOADER.NLM|KernelAddressSpace+63)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--961B8420 (NIRMAN.NLM|SUCCESS_PAGE+A454)
--00000046 (LOADER.NLM|KernelAddressSpace+46)
00108FA6 (LOADER.NLM|kSpinUnlockRestore+26)
--00000046 (LOADER.NLM|KernelAddressSpace+46)
0020C01F (SERVER.NLM|kSemaphoreSignal+11F)
--95F173A0 ?
--00000046 (LOADER.NLM|KernelAddressSpace+46)
--00000046 (LOADER.NLM|KernelAddressSpace+46)
--97CB42A0 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--961B8420 (NIRMAN.NLM|SUCCESS_PAGE+A454)
8F9F4C93 (THREADS.NLM|_SignalSemaphore+B)
--95F173A0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--961B8420 (NIRMAN.NLM|SUCCESS_PAGE+A454)
8FA2123F (REQUESTR.NLM|NCPRequest+C3)
--961B8420 (NIRMAN.NLM|SUCCESS_PAGE+A454)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000003 (LOADER.NLM|KernelAddressSpace+3)
--94CD1898 ?
--961B8420 (NIRMAN.NLM|SUCCESS_PAGE+A454)
--9A8398A0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--94CD15B8 ?
-8F230B38 (NETNLM32.NLM|(Data Start)+B38)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--976CCE40 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--72657355 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
-8F230B38 (NETNLM32.NLM|(Data Start)+B38)
002C6E31 (SERVER.NLM|LoadModule+1D)
--94CD19EC ?
00361932 (SERVER.NLM|FunnelingWrapperReturnsHere+25)
--001D3DD0 ?
--0000001C (LOADER.NLM|KernelAddressSpace+1C)
--00000286 (LOADER.NLM|KernelAddressSpace+286)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
8FB53294 (NETNLM32.NLM|NWDSMutateObject+2AD4)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
-8F230B38 (NETNLM32.NLM|(Data Start)+B38)
--00000080 (LOADER.NLM|KernelAddressSpace+80)
--94CD1C60 ?
--94CD19E4 ?
8FB5323C (NETNLM32.NLM|NWDSMutateObject+2A7C)
--983CA8E0 ?
8FB53369 (NETNLM32.NLM|NWDSMutateObject+2BA9)
--94CD19E8 ?
--94CD19EC ?
--00000003 (LOADER.NLM|KernelAddressSpace+3)
--94CD1898 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--94CD18C8 ?
--94CD1930 ?
--94CD18F8 ?
--00000019 (LOADER.NLM|KernelAddressSpace+19)
--94CD197C ?
--0000000C (LOADER.NLM|KernelAddressSpace+C)
--9796D700 ?

Additional Information:
The CPU encountered a problem executing code in LIBC.NLM. The problem
may be in that module or in data passed to that module by a process owned
by HTTPSTK.NLM.

Regards
Michael Murray