We have a problem on our BM 3.8.5 server on NW 6.5.6.
Whenever a VPN User from a partition that has no replica on the BM
server logs in, the server abends:
++++++++++
Server XXXXXXX halted Wednesday, 21 February 2007 20.56.05,135
Abend 5 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 = 00800000 EBX = 00000000 ECX = 00000004 EDX = B134DDC0
ESI = B12E82D4 EDI = 00000000 EBP = 0000003A ESP = B134DD48
EIP = 8E393A2F FLAGS = 00010246
8E393A2F 8901 MOV [ECX]=?, EAX
EIP in NMAS.NLM at code start +00031A2Fh
Access Location: 0x00000004

The violation occurred while processing the following instruction:
8E393A2F 8901 MOV [ECX], EAX
8E393A31 8B1A MOV EBX, [EDX]
8E393A33 83C304 ADD EBX, 00000004
8E393A36 31C0 XOR EAX, EAX
8E393A38 891A MOV [EDX], EBX
8E393A3A 5B POP EBX
8E393A3B C3 RET
8E393A3C 8D442000 LEA EAX, [EAX+00]
8E393A40 53 PUSH EBX
8E393A41 8B542408 MOV EDX, [ESP+08]



Running process: AuthGW Server 59 Process
Thread Owned by NLM: AUTHGW.NLM
Stack pointer: B134D904
OS Stack limit: B134A100
Scheduling priority: 67371008
Wait state: 5050030 Blocked on Semaphore
+++++++++++++

Users of partitions that have a replica on the BM server can login
without any problems.
Users of partitions that have no replica on the BM server can never
login. I traced the login with NMASMON, but the log only shows
24: nmasClientWrite: Login continue
24: nmasClientWrite: Login continue
24: nmasClientRead: Login continue
24: nmasClientRead: Login continue
24: nmasClientWrite: Login continue
24: nmasClientWrite: Login continue
24: nmasClientWrite: Login continue
24: nmasClientRead: Login succeeded
so no real help here.

Any suggestion where to go from here?

TIA,
Volker