topic Re: OpenVMS Alpha 7.3-2 Advanced Server 7.3B startup problem with PWRK$LMMCP in Operating System - OpenVMS

OpenVMS Alpha 7.3-2 Advanced Server 7.3B startup problem with PWRK$LMMCP

Brian Fairweather — Sun, 14 Nov 2010 14:19:21 GMT

I've upgraded from Pathworks Server 6.1 to Advanced Server 7.3B.

Upgrade didn't display any errors.
I did auto reboots on both Alphaserver ES40s.

I then did the pwrk$config on both servers and did not see errors.

When I try and do the PWSTART, it seems to start OK, but after about 30-45 seconds, I see that
28400249 PWRK$LMMCP CUR 3 3 11577497

seems to never complete.

I did a pwstop and tried on 2nd ES40 with same results.

samcheck -r says OK.

I searched and see an ECO listed, but I am not finding it to see if that is a valid fix.

Please advise on what I can try and expand upon?

Thank you,
Brian

Re: OpenVMS Alpha 7.3-2 Advanced Server 7.3B startup problem with PWRK$LMMCP

Paul Jerrom — Sun, 14 Nov 2010 23:46:10 GMT

Long time since I used this, but I seem to recall this is the license manager process, which is a permanent detached process.
So you don't want the process to end!
Licensing changes big time from 6.1 to 7.3.

Can you still conect to shares/print etc?

Have fun

PJ

Re: OpenVMS Alpha 7.3-2 Advanced Server 7.3B startup problem with PWRK$LMMCP

Brian Fairweather — Mon, 15 Nov 2010 00:10:57 GMT

Hello Paul,

I have license PWLMXXXCA07.03 loaded (25000 units).

No ADMIN commands work, you can just see that process running tight (like in a loop).

I found a 7.3-B ECO patch for OpenVMS 8.x

I made another backup and upgraded to 8.3 (planned for next couple of weeks anyway) applied current 8.3 patches and tried again with same results). Problem stays with Pathworks 7.3B ECO 1

I upgraded a Standalone 7.3-2 system using smae KIT to Adcance Server 7.3-B and had no problems, so something specific to this VMScluster.

Thank you,
Brian

Re: OpenVMS Alpha 7.3-2 Advanced Server 7.3B startup problem with PWRK$LMMCP

Brian Fairweather — Mon, 15 Nov 2010 02:12:35 GMT

Hello,

Hp called and we figured out the problem was caused by corrupted event log files (*.evt) We also deleted the pwrk$section:*.section;1 files also, but pretty sure it was the *.evt;* causing the problem.

Fyi,
Brian