Kbase P158294: Cannot connect to a database using ODBC or JDBC
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/08/2010 |
|
Status: Verified
SYMPTOM(s):
Cannot connect to a database using ODBC
[DataDirect][ODBC Progress Wire Protocol driver][OPENEDGE]Server rejects connection on attach.
JDBC connection just hangs
Database log file does not even show the connection attempt.
JDBC connection to sports2000 database gives errors.
Connecting user ""<username> to URL ""<URL>... (8920)
Error: <command name | SQL Exception message>. (8933)
Error: [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 supports.. (8933)
See ""<filename> and ""<filename> files for more information. (8950)
The database log file in this scenario does give errors.
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.base.BaseConnection.connect(Unknown Source)
at com.ddtek.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
at com.ddtek.jdbc.base.BaseConnection.open(Unknown Source)
at com.ddtek.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.progress.sql.explorer.SQLConnectServer.call(SQLConnectServer.java:37)
at com.progress.common.rmiregistry.TryIt.run(TryIt.java:186)
FACT(s) (Environment):
_sqlsrv2 process does get spawned
Can manually spawn _sqlsrv2 process
Clients installed via NetSetup installation.
Regedit confirms the appropriate entries are in the registry associated with the ODBC Driver.
Registry entries for ODBC drivers were added to the NetSetup client due to know issue where ODBC drivers are not
Windows Server 2003
OpenEdge 10.1B03 Service Pack
CAUSE:
The exact cause is unknown at the time of this writing.
FIX:
Install 10.1C SQL Client Access onto client machine and use these ODBC and JDBC drivers to connect to the 10.1B03 database.