Re: frequently server performs abend error

--------------------------------------------------------------------------------

I suggest you apply nw65sp5 and nw65sp5upd1.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
'NOVELL: Product Support Forums' (http://support.novell.com/forums)
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.

Thanks Mr. Andrew C Taubman for your timely help.
But my other location servers are in the same confiquration running
without any errors. Today morning also this abend error happened, my
server console is in the format of server<2>:
the abend error is
Novell Netware, V6.5 Support Pack 3 - CPR Release
PVER: 6.50.03

Server halted Tuesday, December 12, 2006 2:42:37.311 am
Abend 2 on P00: Server-5.70.03: Page Fault Processor Exception (Error
code 00000000)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 00000000 EBX = B006F214 ECX = 00000063 EDX = 00000073
ESI = B006F214 EDI = 0000000F EBP = 00000000 ESP = 427EA45C
EIP = 46F4FD3D FLAGS = 00000086
46F4FD3D 8BB8D8020000 MOV EDI, [EAX+000002D8]=?
EIP in UNKNOWN memory area
Access Location: 0x000002D8

The violation occurred while processing the following instruction:
46F4FD3D 8BB8D8020000 MOV EDI, [EAX+000002D8]
46F4FD43 29C9 SUB ECX, ECX
46F4FD45 49 DEC ECX
46F4FD46 31C0 XOR EAX, EAX
46F4FD48 F2AE REPNE SCASB
46F4FD4A F7D1 NOT ECX
46F4FD4C 49 DEC ECX
46F4FD4D 51 PUSH ECX
46F4FD4E A1C031B546 MOV EAX, [46B531C0]=00000000
46F4FD53 53 PUSH EBX



Running process: Server 00:11 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 427EAF80
OS Stack limit: 427E3040
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: --469F8E00 ?
-00433E98 (SERVER.NLM|systemConsoleScreenStructure+0)
--46B88080 (CIFSPROX.NLM|NASN1_getNextField+E0C4)
--427EA4AC ?
43AE6FCC (THREADS.NLM|_DestroyCallBackBlock+260)
-00433E98 (SERVER.NLM|systemConsoleScreenStructure+0)
--B006F214 ?
--000000F7 ?
--427EAECE ?
--46A27160 ?
--427EA4DA ?
--B006F214 ?
43AE5591 (THREADS.NLM|__CHK+21)
--46B88080 (CIFSPROX.NLM|NASN1_getNextField+E0C4)
--427EA498 ?
--46A27160 ?
--427EA4DA ?
--B006F214 ?
--427EAECE ?
002751DA (SERVER.NLM|NWParseCommandEx+AF2)
-00433E98 (SERVER.NLM|systemConsoleScreenStructure+0)
--B006F214 ?
--3A535953 ?
--5359532F ?
--2F4D4554 ?
--4F435049 ?
--482F464E ?
--53505454 ?
--502F4B54 ?
434C4C55 (PMLODR.NLM|PMLodrCheckUpdateResponse+4D65)
--4E2E4746 ?
--00004643 ?
--0000004D ?
--B7C991C0 ?
--B7D773AC (FILESYS.NLM|lDOSFirstByteBitMap+D73C)
--00000004 ?
--427EA520 ?
401A38B0 (COMN.NSS|NAME_CheckCacheAscii+30)
--B7D773AC (FILESYS.NLM|lDOSFirstByteBitMap+D73C)
--00000084 ?
--00000000 ?
--00000000 ?
--00000004 ?
--00000009 ?
--427EA764 ?
--B7CB6448 (MALHLP.NLM|consolescreen+2428)
--B7D773AC (FILESYS.NLM|lDOSFirstByteBitMap+D73C)
--00000084 ?
--00000000 ?
--427EA554 ?
401A3C0C (COMN.NSS|NAME_GetNameFromCacheAscii+9C)
--B7D773AC (FILESYS.NLM|lDOSFirstByteBitMap+D73C)
--00000084 ?
--00000000 ?
--B7C991C0 ?
--00000000 ?
--00000009 ?
--427EA764 ?
--00000000 ?
--00000084 ?
--B7F0F220 ?
--427EA708 ?
--427EA598 ?
401A50B0 (COMN.NSS|NAME_FindNameInAsciiNameCache+40)
--B7D773AC (FILESYS.NLM|lDOSFirstByteBitMap+D73C)
--B7F54E00 (NSS.NLM|LB_wGetDimensions+C450)
--B7CA9060 (MANAGE.NSS|MNSS_MasterFreezeLatch+460)
--427EA708 ?
--3F0C9200 ?
--00000100 ?
--427EA5A4 ?
401EC69F (COMN.NSS|LONGNS_asciiLenToUnicode+2F)
--00000001 ?
--3F0C9200 ?
--00000000 ?
--00000000 ?
--000000FF ?
--427EA6BC ?
--00002000 ?
--427EA708 ?
--427EA6BC ?
--427EA62C ?
--427EA5F0 ?
4016BEC0 (COMN.NSS|COMN_Lookup+B60)
--427EA708 ?
--427EA62C ?
--427EA5C8 ?
--00000001 ?
--00000000 ?
--427EA5C4 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000004 ?
-00437620 (SERVER.NLM|xAllocSizeTable+0)
--B7D77060 (FILESYS.NLM|lDOSFirstByteBitMap+D3F0)
--00000000 ?
--00000000 ?
--427EA974 ?
--427EA720 ?

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


--
sivas_in