Presence of an unknown environment variable in the PROPATH invalidates other environment variables in the same PROPATH

Adding any undefined environment variable in the PROPATH for the AppServer Agent affects the correct resolution of properly set environment variables (such as ${CATALINA_BASE}).

Sep 7, 2020
Knowledge

Title

URL Name

Presence-of-an-unknown-environment-variable-in-the-PROPATH-invalidates-other-environment-variables-in-the-same-PROPATH

Article Number

000143099

Environment

Product: OpenEge Version: 11.7.6, 12.1, 12.2 OS: Windows

Question/Problem Description

Valid variables in the openedge.properties PROPATH are not resolved correctly like ${CATALINA_BASE} resulting in error 293

The PROPATH for the AppServer Agent of the Default application oepas1 [AppServer.Agent.oepas1] using ${CATALINA_BASE} variable, it is not resolved properly

A simple test procedure using APSV Transport from an ABL Client, fails with an error that the test procedure was not found : "HelloWorld.p" was not found. (293)

Steps to Reproduce

1. Take the Default Installation of OE 12.1 with PASOE 2. Copy the attached procedure custom.p to the ${CATALINA_BASE}\webapps\ROOT\WEB-INF\openedge 3. add to the PROPATH of AppServer.Aget.oepas1 in ${CATALINA_BASE}\conf\openedge.properties the following path ${CATALINA_BASE}/webapps/ROOT/WEB-INF/openedge 4. open in procedure Editor the attached procedure "Calloepas1.p" 5. Run the opened procedure.

Clarifying Information

The ${PROPATH} variable is not present in the agent's PROPATH
There are no undefined environment variables in the agent's PROPATH
In both OpenEdge 11.7.5 and 12.0 application code is found with ${CATALINA_BASE} variable in the PROPATH as expected
The openedge.properties contains the correct hexadecimal 0a0d pair (expected by Windows CR) for every line

Error Message

** "<file-name>" was not found. (293)

Defect Number

Defect ADAS-22754

Enhancement Number

Cause

The exact cause is not known at this time.

Usually, there can exist unresolved paths in the PROPATH, but the correct ones should be resolved. In this case it looks like all the paths in the PROPATH are not recognized, although there are valid paths even if they are before the unresolved reference.
Adding any undefined environment variable in the PROPATH for the AppServer agent affects the correct resolution of valid environment variables (such as ${CATALINA_BASE}), so that calling a test procedure using APSV Transport from an ABL Client, error (293) is raised stating that the procedure wasn't found.
Adding the ${PROPATH} variable to the agent PROPATH in PASOE can cause this behavior. Unlike the Classic AppServer, it's expected ${PROPATH} variable cannot be resolved in PASOE environments since there is no such thing as a global PROPATH that will work for all instances.

Resolution

None at this time.

Workaround

Review the current PROPATH for unresolved environment variables and assure the $PROPATH environment variable is not present

Then replace the variables with their (expected) value. For example:

Edit the {CATALINA_BASE}\conf\openedge.properties and replace the ${CATALINA_BASE} variable in the PROPATH, with an absolute path to the PASOE instance. The call from ABL Client works as expected.

Notes

Keyword Phrase

Last Modified Date

10/21/2025 2:06 PM

Presence of an unknown environment variable in the PROPATH invalidates other environment variables in the same PROPATH

Files(0)

Was this article helpful?

Was this article helpful?

Presence of an unknown environment variable in the PROPATH invalidates other environment variables in the same PROPATH

Information

Related Articles