Kbase P142085: asbman fails to run when installation path name too long.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/05/2009 |
|
Status: Verified
SYMPTOM(s):
asbman fails to run when installation path name too long.
nsman fails to run
dbman fails to run
Progress Explorer Tool fails to start
Faulting application jvmStartw.exe, version 0.0.0.0, faulting module jvmStartw.exe, version 0.0.0.0, fault address 0x0000536d.
jvmstart.exe crashes when installation path name too long.
FACT(s) (Environment):
Windows
OpenEdge 10.x
CAUSE:
The jvmstart.exe has limitations to the length of its command line. The command line includes the installation path as well as the references to the parameters which define all variables passed to jvmstart.exe.
Example of a path which fails:
c:\program files (x86)\mydir1\oe101c
When this string is taken in conjunction with all the parameters that are typically needed for the asbman to run correctly the command string becomes:
c:\program files (x86)\mydir1\oe101c\bin\jvmstart.exe -o stderr -s -m silent -a "c:\program files (x86)\mydir1\oe101c\properties\JavaTools.properties"::"SECMANCLI" "c:\program files (x86)\mydir1\oe101c\jre\bin\java" -DInstall.Dir="c:\program files (x86)\mydir1\oe101c" -DWork.Dir="c:\program files (x86)\mydir1\oe101c_wrk" "com.progress.ubroker.tools"::"UBCmdClient" -start -name asbroker1
This is 390 characters.
FIX:
Uninstall and re-install to a directory path which is shorter.
Examples:
c:\dlc101c
c:\program files\dlc101c