A customer has just started to get the above abend for no apparent reason.
The server was working fine, and it has now abended 3 time in the last 2
days. No changes have been made, and it is running Groupwise 7 with the
latest (non beta) service patch.

I will try updating the system to nw65sp6 to see if it makes any
difference. The only thing which is automatically updated is the Symantec
Anti-Virus Corportate Edition 10.1.5.5000 and I wonder if the new pattern
file is causing this problem (or has it got corrupted?)

Any other suggestions would be most welcome.

Regards,

ChasR.


Novell Netware, V6.5 Support Pack 5 - CPR Release
PVER: 6.50.05

Server CRAMLINGTON halted Friday, 17 November 2006 1:49:44.838 pm
Abend 2 on P00: Server-5.70.05-4348: Kernel detected an attempted context
switch when it was not allowed


Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0068
EAX = 00000000 EBX = 00000001 ECX = 00000000 EDX = FBF24E13
ESI = 00000000 EDI = 00000046 EBP = 00000000 ESP = 8A50FF6C
EIP = 00223228 FLAGS = 00000002
00223228 83C404 ADD ESP, 00000004
EIP in SERVER.NLM at code start +00019368h

The violation occurred while processing the following instruction:
00223228 83C404 ADD ESP, 00000004
0022322B 5D POP EBP
0022322C 5E POP ESI
0022322D 5B POP EBX
0022322E C3 RET
0022322F A19447F0FB MOV EAX, [FBF04794]=FBF26C68
00223234 50 PUSH EAX
00223235 E89C8FEEFF CALL LOADER.NLM|Abend
0022323A 83C404 ADD ESP, 00000004
0022323D 5D POP EBP



Running process: Server 16 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 8A50FF80
OS Stack limit: 8A508040
CPU 0 (Thread 8A5073C0) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Stack: --FBF24E13 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
00220A7B (SERVER.NLM|SchedThreadYield+63)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
00219C1D (SERVER.NLM|WorkerThread+579)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8A5073C0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8A5073C0 ?
00226B38 (SERVER.NLM|TcoNewSystemThreadEntryPoint+40)
--8A5073C0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--5D18C483 ?
--C35B5E5F ?
--00AA860F ?
--448B0000 ?
--408B3824 ?
--2444894F ?
--FFF88304 ?
--34343434 ?
--00062444 ?
--2474FF00 ?
--E8535704 ?
--00000F70 (LOADER.NLM|KernelAddressSpace+F70)
--830CC483 ?
-5F5D18C4 ?
--0FC35B5E ?
--0005C486 ?
5C8B5653
(OWCIMOMD.NLM|_ZSt38__copy_backward_output_normal_ iteratorIPN8OpenWBEM6Stri
ngEN9__gnu_cxx17__normal_iteratorIS2_St6vectorIS1_ SaIS1_EEEEET0_T_SA_S9_11_
_true_type+23)
--FFBE1424 ?
--8BFFFFFF ?
--A3102444 ?
-8A51ECD0 (KEYB.NLM|(Data Start)+BCD0)
--0C24448B ?
--51ECC4A3 ?
--021EE88A ?
--8EE80000 ?
--6A000002 ?
--30006801 ?
--016A8A51 ?
--3CE8006A ?
--83000003 ?
--026A10C4 ?
--51300E68 ?
--6A036A8A ?
--0329E802 ?
--C4830000 ?
--68036A10 ?
-8A513016 (KEYB.NLM|(Data Start)+16)
--046A056A ?
--000316E8 ?
--10C48300 ?
--1D68046A ?
--6A8A5130 ?
--E8066A07 ?
--00000303 (LOADER.NLM|KernelAddressSpace+303)
--6A10C483 ?
--30236805 ?
--096A8A51 ?
--F0E8086A ?
--83000002 ?
--066A10C4 ?
--51302968 ?
--6A0B6A8A ?
--02DDE80A ?
--C4830000 ?
--68076A10 ?
-8A51302F (KEYB.NLM|(Data Start)+2F)
--0C6A0D6A ?
--0002CAE8 (LOADER.NLM|XENSharedInfo+BAE8)
--10C48300 ?
--3E68086A ?
--6A8A5130 ?
--E80E6A0F ?
--000002B7 (LOADER.NLM|KernelAddressSpace+2B7)
--6A10C483 ?
--30476809 ?
--116A8A51 ?
--A4E8106A ?
--83000002 ?
--0A6A10C4 ?
--51304F68 ?
--6A136A8A ?
--0291E812 ?
--C4830000 ?
--680B6A10 ?
-8A51305F (KEYB.NLM|(Data Start)+5F)
--146A156A ?
--00027EE8 (LOADER.NLM|XENSharedInfo+6EE8)
--10C48300 ?
--67680C6A ?

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.