Hello,
We have just updated our server to Netware 6.5 SP3 from SP2. All seemed
to be going well. The server was up for about 10 hours before we had our
first abend, related to NCPL.NLM. I installed the NSS and Server.EXE
updates after the SP3 install. We are using this as a web server, print
server, file server. We are also running CIFS and NetStorage. Here is
the abend:
Novell Netware, V6.5 Support Pack 3 - CPR Release
PVER: 6.50.03

Server <name> halted Tuesday, July 26, 2005 9:59:26.775 am
Abend 1 on P00: Server-5.70.03: Page Fault Processor Exception (Error
code 00000000)

Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = 61417500 EBX = 65258B00 ECX = 65258B00 EDX = 6D6CD5E0
ESI = 0A0D3E22 EDI = 7B6728F8 EBP = 7B6728C4 ESP = 7B6728A0
EIP = 00209F3F FLAGS = 00010206
00209F3F 8B16 MOV EDX, [ESI]=?
EIP in SERVER.NLM at code start +000051DFh
Access Location: 0x0A0D3E22

The violation occurred while processing the following instruction:
00209F3F 8B16 MOV EDX, [ESI]
00209F41 89F3 MOV EBX, ESI
00209F43 81FA1E071515 CMP EDX, 1515071E
00209F49 753A JNZ 00209F85
00209F4B 8B0D04F00300 MOV ECX, [LOADER.NLM|RunningProcess]=61417160
00209F51 3B8E80000000 CMP ECX, [ESI+00000080]
00209F57 7566 JNZ 00209FBF
00209F59 83BE9000000001 CMP [ESI+00000090], 00000001
00209F60 7539 JNZ 00209F9B
00209F62 B834100000 MOV EAX, 00001034



Running process: NcplSysThread Process
Thread Owned by NLM: NCPL.NLM
Stack pointer: 7B672688
OS Stack limit: 7B6630E0
Scheduling priority: 67371008
Wait state: 5050190 Blocked on a kernel CV
Stack: B4B0F560 (WS2_32.NLM|WS2_32_setsockopt+28)
--000000E5 ?
--7B6728C4 ?
--7B6728F8 ?
--7B67292C ?
--65258B00 ?
B0192236 (LIBC.NLM|NXLock+36)
--0A0D3E22 ?
--7B6728EC ?
--00000050 ?
6E84EA0A (NIFIF.NLM|NIFIO_WaitMutex+A)
--65258B00 ?
6E84E592 (NIFIF.NLM|asyncConnect+12)
--65258B00 ?
--00000050 ?
--7B6728F0 ?
6E84E769 (NIFIF.NLM|NIFIO_OpenSocket+109)
--7B6728EC ?
--6DC78DB0 ?
--000000E5 ?
--50000002 ?
--56F3C086 ?
--00000000 ?
--00000000 ?
--CCCCCCCC ?
--00000000 ?
--00030001 ?
--00008400 ?
--00008400 ?
--00000001 ?
--751A9630 (NSSMNGR.NLM|__NLM_BSS_End+39F1)
--690B4900 ?
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
6E85031E (NIFIF.NLM|NIFIF_SendAndReceive+4E)
--56F3C086 ?
--00000050 ?
--00000001 ?
--751A9860 (NSSMNGR.NLM|__NLM_BSS_End+3C21)
6E84E45F (NIFIF.NLM|NIFIO_GetHostAddrPort+9F)
--7B672940 ?
--2E343331 ?
--2E323931 ?
--2E333432 ?
--FFFFFF95 (LOADER.NLM|KernelTempAliasesEnd+F95)
--CCCC0030 ?
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
--0000001A ?
--7B6729D0 ?
--721198E0 ?
6E8507DE (NIFIF.NLM|NIFIF_SendBuffer+2E)
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
--721198E0 ?
--00000008 ?
--690B4900 ?
--000083E8 ?
--751A9524 (NSSMNGR.NLM|__NLM_BSS_End+38E5)
--751A9528 (NSSMNGR.NLM|__NLM_BSS_End+38E9)
--00000000 ?
--751A9630 (NSSMNGR.NLM|__NLM_BSS_End+39F1)
--00000000 ?
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
6E85092E (NIFIF.NLM|NIFIF_sendMessageToServer+E)
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
--721198E0 ?
6E8509A6 (NIFIF.NLM|NIFIF_sendToServer+66)
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
--7B672A24 ?
--61417160 (XTLOG.NLM|GetGlobalConfiguration+FB25)
--00000000 ?
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
6E850808 (NIFIF.NLM|NIFIF_ping+18)
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
--0000001A ?
--7B6729D0 ?
--00000001 ?
--751A9630 (NSSMNGR.NLM|__NLM_BSS_End+39F1)
--751A9860 (NSSMNGR.NLM|__NLM_BSS_End+3C21)
--7B672A24 ?
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
6E84D890 (NIFIF.NLM|nif_initServerConnection+60)
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
--00000006 ?
--61417100 (XTLOG.NLM|GetGlobalConfiguration+FAC5)
6E84CB7E (NIFIF.NLM|NifCreateContextAndLogin+1A6)
--751A9500 (NSSMNGR.NLM|__NLM_BSS_End+38C1)
-61DEDAE0 (NIFIF.NLM|g_iFolderServerIP+0)
--00000000 ?
--CCCCCCCC ?
--00000000 ?
--CCCCCC00 ?
--CCCCCCCC ?
--CCCCCC00 ?
--00000006 ?
--69CDAE18 ?
--00000006 ?
-6502CD8C (NCPL.NLM|vtNcpl+0)
--61417160 (XTLOG.NLM|GetGlobalConfiguration+FB25)
--7B672A84 ?
6E84C7F4 (NIFIF.NLM|NifLoginThread+2B9)
--65449000 ?

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