Kbase P161942: Ending backslash in the install path causes installation corruption
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/04/2010 |
|
Status: Unverified
SYMPTOM(s):
Ending backslash in the install path causes installation corruption
Getting error 8271 when running the wtbman command from a proenv
option = unknown or invalid <option name> (8271)
option = unknown or invalid query (8271)
Similar error occurs if using any other parameter that is valid for this command.
Similar commands like asbman exhibit the same behavior
Displaying the environment variables in proenv shows that the path assigned to LIB contains a double-backslash. (eg LIB=C:\DLC\\LIB)
Displaying the environment variables in proenv shows that the path assigned to DLC contains an ending backslash. (eg DLC=C:\DLC\)
If you modify the script or the command line environment on the failing machine to contain the following environment variables, the problem no longer occurs: DLC, PATH and LIB.
set DLC=<directory where Progress is installed, without ending backslash>
set PATH=%DLC%\BIN;%PATH%
set LIB=%DLC%\LIB;%LIB%
OS-COMMAND fails to execute
Windows registry contains the same corruption on the LIB variable (double backslash)
FACT(s) (Environment):
Command being executed from proenv:
wtbman -help
wtbman command when issued without parameters returns help as expected.
WebSpeed broker is running and servicing users.
AppServer broker is running and servicing users.
Windows
OpenEdge 10.x
OpenEdge Category: Installation
CHANGE:
Set a custom installation target path during the setup
CAUSE:
Bug# OE00196196
FIX:
Reinstall OpenEdge, removing the ending backslash in the customer installation target path.
Editing the registry and the OpenEdge batch files manually is not a recommended approach.