Kbase P151141: _sqlsrv2 crash immediately upon connection
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  4/4/2011 |
|
Status: Verified
SYMPTOM(s):
_sqlsrv2 crash immediately upon connection
Error: <command name | SQL Exception message>. (8933)
Error: [DataDirect][OpenEdge JDBC Driver]A server crash is likely.. (8933)
See ""<filename> and ""<filename> files for more information. (8950)
See "/data/db/openacc/sqlexp.log" and "/data/db/openacc/SQLExplorer.exceptions" files for more information. (8950)
Errors 2526 and 2525 in database log immediately after connection:
Disconnecting client <number> of dead server <number>. (2526)
Disconnecting dead server <number>. (2525)
Configuration uses a separate secondary SQL broker with the primary broker allowing both 4GL and SQL connections.
Wrk directory permissions are rwxr-xr-x
FACT(s) (Environment):
SQL Explorer is running on the same machine as the database.
Another server set up the same way works correctly.
Java 6 exists on server, but Java environment variables point to Java 5.
SELinux not enabled.
Large files enabled.
Red Hat Enterprise Linux 5.0
OpenEdge 10.1C
CAUSE:
Unable to write to the wrkdir that was set up during the Progress install (/usr/wrk).
FIX:
As root, run chmod 777 wrk from within /usr