| Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Moderator: | CPEEDY::KENNEDY |
| Created: | Fri Dec 18 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4319 |
| Total number of notes: | 18478 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3356.1 | Reboot needs to be done after upgrade | AROS01::ISACSSON | Jan-Erik "ISAK" Isacsson | Fri Feb 23 1996 05:46 | 5 |
| 3356.2 | Crash after reboot even... | FXODEV::BETTRO | Tue Feb 27 1996 13:18 | 9 | |
| 3356.3 | re .2 | FXODEV::BETTRO | Wed Feb 28 1996 09:19 | 14 | |
| 3356.4 | more info... | FXODEV::BETTRO | Wed Feb 28 1996 10:44 | 4 | |
| 3356.6 | Seems to be VMS backup causing the problem... | FXODEV::BETTRO | Thu Feb 29 1996 11:01 | 7 | |
| 3356.7 | version limits there? | VELI::KORKKO | Veli K�rkk� @FNO, 879-5512, GPS FNO | Sun Mar 03 1996 16:27 | 7 |
| 3356.8 | Back to problem in .0 | VMSNET::ALLERTON | Thu Mar 14 1996 13:21 | 24 | |
| 3356.9 | halt? really? | LJSRV1::MAFFA | Thu Mar 14 1996 15:36 | 15 | |
| 3356.10 | ?06 HLT INST | VMSNET::ALLERTON | Thu Mar 14 1996 17:03 | 19 | |
| 3356.11 | This is truly strange | CPEEDY::VATNE | Peter Vatne, PATHWORKS Server Engineering | Thu Mar 14 1996 18:09 | 13 |
| 3356.12 | Customer is mailing us his... | VMSNET::ALLERTON | Fri Mar 15 1996 09:44 | 24 | |
| 3356.13 | I'm not directly involved... | CPEEDY::VATNE | Peter Vatne, PATHWORKS Server Engineering | Fri Mar 15 1996 13:45 | 6 |
| 3356.14 | VELI::KORKKO | Veli K�rkk� @FNO, 879-5512, GPS FNO | Sun Mar 17 1996 16:49 | 24 | |
| 3356.15 | It's Baaaack | VMSNET::P_NUNEZ | Mon Apr 07 1997 16:24 | 25 | |
FWIW, we're starting to see these PWRK$CONFIG causing system halt
calls again for folks going from v5.0C ECO3 to v5.0E ECO1. Seems to be
a VAX running VMS 6.1 each time.
We're trying to confirm if reboot after the install (before
pwrk$config) avoids the crash, but indications are that even if they
reboot immediately after the install, when they run pwrk$config, it
halts the system. After the subsequent reboot pwrk$config runs w/o
problems.
In the case I worked Saturday and another I'm aware of, it appears it
was PWRK$VERIFY.EXE that caused the halt (the halt occurs right after
the message "Checking SYSGEN parameters" is displayed, which is when
pwrk$verify executes).
I'm trying to reproduce on a uVAX 3400; the customer having the
major problem (he has 12 VAX 6.1 systems that need PATHWORKS upgraded)
has VAX 7000 class systems, so I'm not confident my attempts to
reproduce will be fruitful.
Just thought I'd (re)start this thread in anticipation that others will
be getting calls on it...
Paul
| |||||