Pathworks 6.1 Problem on Alpha

[Rob Buxton]

Hi All,
I'm in the process of building a mixed architecture VMS Cluster for our DR site. VMS is being would down here. I'm constrained to building the cluster as close as possible to what we're running as a Production.

I'm trying to get Pathworks 6.1 on an Alpha running VMS 7.2-2 to connect to our NT domain to permit authentication.
This works for our Production site.
I'm familiar with the Pathworks config options.
I have got the Server to talk and authenticate to the Domain, but only once.
When I start Pathworks 8 processes fire up. After about 30-60 seconds this has been reduced to 4.
It seems the PWRK$LMSRV Process is dying and taking the others with it.
Anyone encountered similar?
A DMP File has also been created, but I'm not too sure of the best way to review it. It's been too long since I did serious stuff on a VMS System.!
The following is from the Log.
1-JUL-2005 09:13:20.31 208004BC:00753938 PPS_jdb_open: Could not read header!
1-JUL-2005 09:13:20.31 208004BC:00753938 PPS Initialization failure: Cannot read job database!
1-JUL-2005 09:13:20.31 208004BC:00753938 PANIC: aborting from module AS$BLD_ROOT:[AS.SERVER.UTIL.SRC]PPS_UTIL.C;1 at line 105!
%SYSTEM-F-ABORT, abort
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
PWRK$LMSRV PPS_UTIL PPS_die 45640 000000000000010C 000000000019DE6C
PWRK$LMSRV PPS_UTIL PPS_init 45693 00000000000001EC 000000000019DF4C
PWRK$LMSRV MAIN fsp1$main 79253 00000000000008B0 00000000000908B0
PWRK$CSSHR_V7 MTS MTS$CONTEXT_SWITCH
6673 0000000000000104 00000000003FA1C4
PWRK$CSSHR_V7 MTS MTS$MAIN_SCHEDULER
? ?
PWRK$LMSRV MTS$MAIN main 4471 00000000000000BC 0000000000091C4C
PWRK$LMSRV MTS$MAIN __main 0 0000000000000058 0000000000091BE8
0 FFFFFFFF9A059494 FFFFFFFF9A059494

[John Gillings]

Rob,

If you have disk quotas on the system disk, try turning them off and (re?)running PWRK$CONFIG.

If that doesn't work, please log a case.

[Rob Buxton]

John,

Thanks for the reply.
I removed Pathworks 6.1 and installed Advanced Server instead.
That works fine and I've got Authentication working with the AD Domain so that will do me.