Kbase P144733: Can not start AdminServer from command line when installation path is very long. Getting error The
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/6/2010 |
|
Status: Unverified
SYMPTOM(s):
Can not start AdminServer from command line when installation path is very long. Getting error The input line is too long.
Can not start Progress Explorer when installation path is very long.
Can not start asbman from command line when installation path is very long. Getting error The input line is too long.
Can not start nsman from command line when installation path is very long. Getting error The input line is too long.
Can not start wtbman from command line when installation path is very long. Getting error The input line is too long.
There is no admserv.log file in the working directory, or it's not being updated when starting the adminservice.
FACT(s) (Environment):
Windows
Progress 9.x
OpenEdge 10.x
CHANGE:
Long command lines may encounter problems under Windows.
This is true for AdminServer, Progress Explorer or other tools which add information constructed from variables in scripts or from parameters passed from properties files such as JavaTools.properties.
The command line constructed from the script / property file(s) contain the path to the executable plus the paths to many .jar files necessary to run the code. The combination of all these paths and parameters is exceeding a Windows limit.
The constructed command line exceeds the Windows command-line string limit.
For Windows 2000 or NT4 the maximum length of the string that you can use at the command prompt is 2047 characters.
For Windows XP or later the maximum length of the string that you can use at the command prompt is 8191 characters.
Check Microsoft's command-line string limitation for more details about this issue.
FIX:
The simplest solution to this problem is to re-install Progress / OpenEdge to a different location within the system so that the installation location takes less characters and would thereby shorten the constructed command line string.
If the original installation location were the following:
c:\Program Files\progress\progressversion10.1b
Consider a different shorter installation directory.
Example:
c:\dlc101b