I posted this thread over iManager's thread, but I'm not sure is the right place... so...
Hi everyone.

We are at 70% of NW6.5 SP6 deployment, migrating from some 25 servers to 50 servers (clusters, single servers, etc). We have found an issue concering iManager+openwbem (owcimomd.nlm). There is a health monitoring link icon on iManager's page (left of the help icon) that everytime one of our network admins click on it, owcimomd.nlm generates an abend. The abending server recovers from the abend and goes into the <1> prompt. It becomes sluggish and of course any openwbem related task is gone. Logger screen shows up a "running process will be suspended" and abend.log saves the below.

I have some lab servers exactly identical to production (lucky me!) where i have been able to reproduce the situation. I have downloaded NW65SP6_CIMOM4, no luck, same issue. I updated portal.nlm, no luck. I back reved cimom down to nw6.5 SP5. No luck. I will try cimom from SP7 later this week, but we commited to working with SP6.

Is there anyone out there seeing the same issues with SP6 and/or SP7

Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.06

Server BINCCS12 halted Tuesday, June 17, 2008 5:51:26.383 pm
Abend 1 on P00: Server-5.70.06: Page Fault Processor Exception (Error code 00000002)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 00000024 EBX = A233F6B8 ECX = A233F0F8 EDX = 00000024
ESI = A233F118 EDI = A1D8E300 EBP = A233F020 ESP = A233F01C
EIP = 99332F8C FLAGS = 00010292
99332F8C F0FF0A (LOCK) DEC dword ptr [EDX]=?
EIP in OWCIMOMD.NLM at code start +00285F8Ch
Access Location: 0x00000024

The violation occurred while processing the following instruction:
99332F8C F0FF0A (LOCK) DEC dword ptr [EDX]
99332F8F 0F9445FF SETZ [EBP-01]
99332F93 807DFF00 CMP [EBP-01], 00
99332F97 0F95C0 SETNZ AL
99332F9A 0FB6C0 MOVZX EAX, AL
99332F9D C9 LEAVE
99332F9E C3 RET
99332F9F 90 NOP
99332FA0 55 PUSH EBP
99332FA1 89E5 MOV EBP, ESP



Running process: OWCIMOMD.NLM:991460f6 Process
Thread Owned by NLM: OWCIMOMD.NLM
Stack pointer: A233EA98
OS Stack limit: A2241D00
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Stack: 0033F078 (SERVER.NLM|DumpStackRange+50)
--A233F030 ?
99332305 (OWCIMOMD.NLM|_ZN8OpenWBEM8RefCount10decAndTestEv+ 11)
--00000024 (LOADER.NLM|KernelAddressSpace+24)
00240900 (SERVER.NLM|UpdateAddressSpaceInfo+2C)
--A233F040 ?
993DBEEE (OWCIMOMD.NLM|_ZN8OpenWBEM28COWIntrusiveReferenceR eleaseEPNS_25COWIntrusiveCountableBaseE+14)
--00000024 (LOADER.NLM|KernelAddressSpace+24)
--A233F050 ?
--A233F050 ?
99466689 (OWCIMOMD.NLM|_ZN8OpenWBEM21COWIntrusiveReferenceI NS_6String7ByteBufEED1Ev+1B)
--00000020 (LOADER.NLM|KernelAddressSpace+20)
--A1C49960 ?
--A233F090 ?
99466867 (OWCIMOMD.NLM|_ZN8OpenWBEM21COWIntrusiveReferenceI NS_6String7ByteBufEEaSERKS3_+57)
--A233F078 ?
--A233F6C8 ?
--A233F080 ?
9928EB46 (OWCIMOMD.NLM|_ZNK8OpenWBEM11XMLNodeImpl7getTextEv +1C)
--A233F0F8 ?
--A1D8E320 (NPKIJNI.NLM|Java_com_novell_security_japi_pki_NPK IAPI_NPKIKMOExportWrite+7C47)
--A233F080 ?
99331142 (OWCIMOMD.NLM|_ZN8OpenWBEM25IntrusiveReferenceRele aseEPNS_22IntrusiveCountableBaseE+14)
--00000020 (LOADER.NLM|KernelAddressSpace+20)
--A233F0F8 ?
--A233F0A0 ?
99290ABD (OWCIMOMD.NLM|_ZNK8OpenWBEM7XMLNode7getTextEv+21)
--A233F0F8 ?
--A233F6B8 ?
--A233F0A0 ?
99140A1C (OWCIMOMD.NLM|_ZN8OpenWBEM6StringaSERKS0_+18)
--A233F6C8 ?
--A233F0F8 ?
--A233F170 ?
9929EC4A (OWCIMOMD.NLM|_ZN9NRMHealthC1Ev+7DA)
--A233F6C8 ?
--A233F0F8 ?
9964C234 (OWCIMOMD.NLM|fmt2_1+C2D)
993D7127 (OWCIMOMD.NLM|_ZN8OpenWBEM12StringBuffer13releaseS tringEv+3D)
--A2340098 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--A21DF280 ?
--A233F2C8 ?
--A21DF280 ?
--00000053 (LOADER.NLM|KernelAddressSpace+53)
--00000072 (LOADER.NLM|KernelAddressSpace+72)
99108DE5 (OWCIMOMD.NLM|_ZNK8OpenWBEM8CIMValue12CIMValueImpl 8toStringEb+EFB)
--A233F128 ?
--0000006F (LOADER.NLM|KernelAddressSpace+6F)
--0000004E (LOADER.NLM|KernelAddressSpace+4E)
--0000006D (LOADER.NLM|KernelAddressSpace+6D)
--A1D8E2C0 (NPKIJNI.NLM|Java_com_novell_security_japi_pki_NPK IAPI_NPKIKMOExportWrite+7BE7)
--A233F0F4 ?
--A233F100 ?
99334E25 (OWCIMOMD.NLM|_ZN8OpenWBEM8RefCount3incEv+11)
--A1C49960 ?
--A23400D8 ?
--A233F110 ?
--00000065 (LOADER.NLM|KernelAddressSpace+65)
--A1D8E300 (NPKIJNI.NLM|Java_com_novell_security_japi_pki_NPK IAPI_NPKIKMOExportWrite+7C27)
--A23400D8 ?
--A233F120 ?
994666B1 (OWCIMOMD.NLM|_ZN8OpenWBEM21COWIntrusiveReferenceI NS_6String7ByteBufEEC1ERKS3_+25)
--A1D8E300 (NPKIJNI.NLM|Java_com_novell_security_japi_pki_NPK IAPI_NPKIKMOExportWrite+7C27)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--A1D8E280 (NPKIJNI.NLM|Java_com_novell_security_japi_pki_NPK IAPI_NPKIKMOExportWrite+7BA7)
--003D786C ?
--A233F140 ?
99332305 (OWCIMOMD.NLM|_ZN8OpenWBEM8RefCount10decAndTestEv+ 11)
--A23D60C0 ?
9964CC7C (OWCIMOMD.NLM|fmt2_1+1675)
--A233F150 ?
993DBEEE (OWCIMOMD.NLM|_ZN8OpenWBEM28COWIntrusiveReferenceR eleaseEPNS_25COWIntrusiveCountableBaseE+14)
--A1E02000 ?
--A23D7860 ?
--A233F160 ?
99466689 (OWCIMOMD.NLM|_ZN8OpenWBEM21COWIntrusiveReferenceI NS_6String7ByteBufEED1Ev+1B)
--A23D7920 ?
9964CC7C (OWCIMOMD.NLM|fmt2_1+1675)
--A233F170 ?
--A233F201 ?
--A233F208 ?
--A233F228 ?
--A23401C0 ?
9957AB43 (OWCIMOMD.NLM|_ZN43_GLOBAL__N__Z22GetSwapFilesStat isticsRyS_S_30NetwareOperatingSystemProvider11getI nstanceERKN8OpenWBEM18IntrusiveReferenceINS1_22Pro viderEnvironmentIFCEEERKNS1_6StringERKNS1_13CIMObj ectPathENS1_9WBEMFlags14ELocalOnlyFlagENSD_22EIncl udeQualifiersFlagEN+40D3)
--A233F2C8 ?
9964CC7C (OWCIMOMD.NLM|fmt2_1+1675)
--A23400E8 ?
--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)
--0000F1E0 (LOADER.NLM|KernelAddressSpace+F1E0)
9A8DBEAE (NETSHLD.NLM|WatchPostClose+E)

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