| Title: | PATHWORKS for OpenVMS (NetWare) Conf. |
| Notice: | Shipping on OpenVMS/Alpha and OSF/1 - ECOs=314.* - Kits=21.* |
| Moderator: | DELNI::GORCZYCA |
| Created: | Wed Nov 04 1992 |
| Last Modified: | Tue Jun 03 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 805 |
| Total number of notes: | 2930 |
Hello!
I'd liked to know what means the error message find in PWVN$server.log?
ERROR COULD NOT CHANGE PROCESS NAME
The errorlog is has follow:
-----------------------------------------------------------------------
21-MAR-1997 18:37:18.75 PATHWORKS V1.0-430D for OpenVMS (NetWare) built
on 09/0*
21-MAR-1997 18:37:19.40 NetWare print server NETPRINTSERVER2:
Starting...
21-MAR-1997 18:37:19.51 NetWare print server NETPRINTSERVER2:
Configured.
21-MAR-1997 18:37:20.61 NetWare print server NETPRINTSERVER1:
Starting...
21-MAR-1997 18:37:20.72 NetWare print server NETPRINTSERVER1:
Configured.
21-MAR-1997 18:37:21.81 NetWare print server NETPRINTSERVER3:
Starting...
21-MAR-1997 18:37:21.98 NetWare print server NETPRINTSERVER3:
Configured.
21-MAR-1997 18:37:22.09 NetWare print server NETPRINTSERVER3:
ERROR -- Could not change process name.
21-MAR-1997 18:37:22.14 NetWare print server NETPRINTSERVER3:
Shutting down.
21-MAR-1997 18:37:22.20 NetWare print server NETPRINTSERVER3:
Shut down successfully.
------------------------------------------------------------------
THANKS FOR YOURS ANWERS!
Robert.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 795.1 | Process-name already exists? | CPEEDY::COOK | Just say NO to that AccViO! - Java!!! | Wed Mar 26 1997 19:28 | 25 |
>>ERROR -- Could not change process name.
This probably indicates that the process-name was already in use.
Each print-server is given a separate process name, formed by
appending the queue-name to a fixed string. But, if the an
earlier-instantiation of that same print-server didn't get shutdown
all the way to process-deletion, then when the product is restarted
again, it no doubt blindly tries to recreate a process with that
same name and fails due to process name collision.
(You may be able to confirm/deny this hypothesis by examination of
the log files and see if there's any missing msgs of processes
failing to shutdown properly.)
If there are any stuck NetWare-related processes after executing
a shutdown (via @sys$startup:pwvn$shutdown), then try doing stop/id
on them before restarting the product.
Hope this helps...
Dave
| |||||