Consultor Eletrônico

VMS Installation Troubleshooting Tips

920219-ctp01
INTRODUCTION:
=============

This Progress Software Technical Support Knowledgebase Entry
provides troubleshooting tips for some of the issues related
to the PROGRESS Installation process on VMS systems.

PROCEDURAL APPROACH:
====================
One common point of confusion on PROGRESS product installation
on VMS is that one meaning of "install" is: "Did the files
get copied from the release media to the machine's disk?"
Another meaning, unique to VMS, is: "Is the program loaded
into shared memory?" Be sure to clarify which "install"
is causing the problem.

The following sections list some possible error messages,
their probable causes, and how to resolve them.

1. "error parsing Version 6" or "%CLI-I-SYNTAX error parsing
ORACLE_VERSION CLI-E-ENTRY specified entity not found in
tables."

Likely cause: A previous version of PROGRESS is already in
use and is installed in memory. Mismatched pieces of
PROGRESS are running and triggering one of these messages.
It is possible to have more than one version of PROGRESS
available for use, as long as the file copy and logicals
set up are completed properly.

Solution: If a previous version of Progress was already
installed when you installed a new one, the new DLC:PROGRESS.CLD
must be loaded into the DCLTABLES. To do this, use the
following variation of the SET COMMAND displayed on Page 44
of the Installation Notes:

SET COMMAND/REPLACE=SYS$LIBRARY:DCLTABLES/OUTPUT=
SYS$LIBRARY:DCLTABLES DLC:PROGRESS.CLD

2. "error activating image PROSRV"

Likely cause: The server command is unable to find the
PROGRESS executable.

Solution: Check that the logical PROSRV was set. It must
point to the _MPROSRV.EXE executable. If the logical was set
properly, then check if it was installed in memory.
To see if the logical was set enter the following:
SHOW LOGICAL PROSRV
It should point to DLC:_MPROSRV.EXE. If the logical
was correct, then perhaps the image was not installed.
To install the image in memory, you must run the INSTALL
utility and install _MPROSRV.EXE as shown on page 45 of
the Installation Notes.

3. "error activating image PROEXE"

Likely cause: The client command is unable to find the
PROGRESS executable.

Solution: Check that the logical PROEXE was set. It must
point to the PROGRES.EXE executable. If the logical was set
properly, then check if it was installed in memory.
To see if the logical was set, enter the following:
SHOW LOGICAL PROEXE
It should point to DLC:PROGRES.EXE. If the logical was
correct, then perhaps the image was not installed. To
install the image in memory, you must run the INSTALL
utility and install _MPROSRV.EXE as shown on page 45 of
the Installation Notes.

4. "The server did not start successfully" error 1554 occurs
when trying to start multi-user PROGRESS.

Likely cause: SET COMMAND was not completed for all the
accounts involved in running PROGRESS.

Solution: Page 44 of the Installation Notes displays
the SET COMMAND that must be done at the system level.
The SET COMMAND must also be in the LOGIN.COM of the
account that is starting the server, AND the account
that starts a client process. The SET COMMAND will
load PROGRESS language definitions into the DCLTABLES.
This is necessary in order for PROGRESS to run. In
most cases, this will resolve the problem, and the
server will start. If the problem still exists,
you may need to reboot the machine in order for the
DLC:PROGRESS.CLD file to be loaded into the DCLTABLES.
See Section 1.

5. "ambiguous command verb - supply more characters"
when trying to start up PROGRESS.

Likely cause: PROGRESS commands are not being recognized
because logicals are not all set or commands haven't been
installed in memory.

Solution: Check for the logicals necessary to run PROGRESS.
If they have not been set, then set them. Confirm that
the DLC:PROGRESS.CLD file has been loaded into the
SYS$LIBBRARY:DCLTABLES with the SET COMMAND. If it
has not, then follow the instructions on Page 44 of
the Installation Notes. Make sure that the LOGIN.COM
that gets executed at login has the SET COMMAND in it,
for the account that starts the server, and the account
that starts a client process.

REFERENCES TO WRITTEN DOCUMENTATION:
====================================
VMS Installation Notes for PROGRESS

Progress Software Technical Support Note # 9779