GroupWise Messenger Agent Abends when using direct access mode

Frequent abends in the GroupWise Messenger Messaging Agent, when the Messaging Agent is accessing eDirectory, not using LDAP, or in direct access mode.

Symptoms:
Abend: NMMA-TCP-HANDLER_xx Process

Server NW65SERVER halted Monday, July 9, 2007 9:51:53.455 am
Abend 1 on P00: Server-5.70.06: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 9C036120 EBX = 00000000 ECX = 00000000 EDX = 9C03613B
ESI = 00000000 EDI = 9C03613B EBP = 9C03613B ESP = 9C035CF8
EIP = 863E2D14 FLAGS = 00210282
863E2D14 0FB609 MOVZX ECX, byte ptr [ECX]=?
EIP in LIBC.NLM at code start +00095D14h
Access Location: 0x00000000

This abend is fixed in GroupWise Messenger, version 2.0 SP2 HP1 or higher, that can be accessed at the below web site.

Search for updated "GroupWise Messenger 2.0.2 HP1 Win/NLM" code at Novell Downloads, dated at least June 28, 2007

https://download.novell.com/index.jsp?tab=patches&page_num=1&families=2584&product_id=&keywords=&version=&date_range=&y=11&x=23&search_type=&search=Search

( Balance of Abend log information )

The violation occurred while processing the following instruction:
863E2D14 0FB609 MOVZX ECX, byte ptr [ECX]
863E2D17 83C301 ADD EBX, 00000001
863E2D1A 83C501 ADD EBP, 00000001
863E2D1D 880A MOV [EDX], CL
863E2D1F 803A00 CMP [EDX], 00
863E2D22 75EC JNZ 863E2D10
863E2D24 5D POP EBP
863E2D25 5B POP EBX
863E2D26 C3 RET
863E2D27 90 NOP

Running process: NMMA-TCP-HANDLER_22 Process

Thread Owned by NLM: NMMA.NLM
Stack pointer: 9C03644C
OS Stack limit: 9C02B260
Scheduling priority: 67371008
Wait state: 5050190 Blocked on a kernel CV
Stack: --9C0362B0 ?
--9616B180 ?
959524CB ?
--9C036120 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
..........................
..........................
--904CDF98 ?
9048723C (B57.LAN|(Code Start)+D23C)
--904AAF70 ?
--904CDF98 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--904A9C84 ?
--904AA5FC ?
--904A83DC ?
--904A9C84 ?
--904CDF98 ?
90487043 (B57.LAN|(Code Start)+D043)
--904AA5FC ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
.................................
.................................

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 NMMA.NLM.