| Update:
We were finally able to get the process to stay up by manually
starting it after the pwrk$startup has completed starting all
of the other processes. In all cases the customer is using
the SYSTEM account for starting PATHWORKS and for manually
starting PWRK$LICENSE_R process. He was also able to write
a COM procedure to run the PWRK$LICENSE_REGISTRAR.EXE and
he is able to submit the comprocedure to batch to start it.
So the Big Question is: What is PWRK$STARTUP doing ie, symbols,
logicals or whatever that is different. We have checked rms
protection on the PATHWORKS logs directories and so forth.
We have check the SYSTEM account in authorize and cant see
any reason for the failure. The customer has currently downgraded
to V5.0D ECO3 and is still having the same problem.
JOHNNY D. (PATHWORKS AFTERHOURS)
|
| .0> The PWRK$LOGS:PWRK$LICENSE_R_node.LOG files reports the error message
.0>
.0> Error opening primary input file SYS$INPUT
.0> File not found
.0>
.0> What file is being referring to???
Do you have a PWRK$Common:PWRK.Ini file on your system?
If yes, is there a [AltStart] section?
If yes, is there anything which refers to the "License_R"?
If so, remove it.
When you say it the registrar isn't able to start - does it run at all?
If so, how log does it actually stay up? Are the Registrar log files
created? (you said yes, just checking) Is there anything in either the
PWRK$LICENSE_R_node.Log or PWRK$LICENSE_REGISTRAR_node.Log log files
(in directory PWRK$Logs), other than what you already posted?
Is there a PWRK$LICENSE_REGISTRAR.DMP dump file in PWRK$Logs?
If the log files are being created, please be sure to turn on verbose
logging for the license registrar ($ Define/system PWRK$LrLogVerbose 1).
\steve
|