JDBC and ODBC connectons fail with error %s (%s) in SQL from subsystem %s function %s called from %s

SYMPTOM(s):

JDBC and ODBC connectons fail with error %s (%s) in SQL from subsystem %s function %s called from %s on %s for %s. (8933)

Error: [DataDirect][OpenEdge JDBC Driver][OpenEdge] Internal error %s 9%s) in SQL from subsystem %s function %s called from %s on %s for %s. Save log for Progress technical supports.. (8933)

Connect with JDBC gives same error.

Connect with ODBC gives same error.

Error occurs when connecting to the Production database.

Connecting to a sports2000 database works fine.

See sqlexp.log" and "SQLExplorer.exceptions" files for more information. (8950)

java.sql.SQLException
Message (throw): ### Connect stack trace. ###
Message (excp): [DataDirect][OpenEdge JDBC Driver][OpenEdge] Internal error %s (%s) in SQL from subsystem %s function %s called from %s on %s for %s. Save log for Progress technical support.
Stack Trace:
java.sql.SQLException: [DataDirect][OpenEdge JDBC Driver][OpenEdge] Internal error %s (%s) in SQL from subsystem %s function %s called from %s on %s for %s. Save log for Progress technical support.
at com.ddtek.jdbc.openedge.client.OpenEdgeClientLoginRequest.attachToServer(Unknown Source)
at com.ddtek.jdbc.openedge.client.OpenEdgeClientLoginRequest.submitRequest(Unknown Source)
at com.ddtek.jdbc.openedge.OpenEdgeImplConnection.open(Unknown Source)
at com.ddtek.jdbc.openedgebase.BaseConnection.doConnect(Unknown Source)
at com.ddtek.jdbc.openedgebase.BaseConnection.connect(Unknown Source)
at com.ddtek.jdbc.openedgebase.BaseConnection.setupImplConnection(Unknown Source)
at com.ddtek.jdbc.openedgebase.BaseConnection.open(Unknown Source)
at com.ddtek.jdbc.openedgebase.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.progress.sql.explorer.SQLConnectServer.call(SQLConnectServer.java:41)
at com.progress.common.rmiregistry.TryIt.run(TryIt.java:186)


FACT(s) (Environment):

All Supported Operating Systems
Progress 9.1x
OpenEdge 10.x

CHANGE:

Migrating to a New OpenEdge Release and a new Host.

CAUSE:

The script used to start the production database used -T parameter, which was pointing to a directory that did not exist.

FIX:

Create the directory reference by the -T and assign appropriate permissions.