E1: KER: E1 Service on Enterprise Server Fails to Start Due to ODB0000164 and ODB0000155 Errors
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
When attempting to start EnterpriseOne (network) service on Windows 2008 Enterprise Server with SQL Server 2008, the following errors appear in the Security kernel JDE.LOG:
The full package was successfully built and deployed to the Enterprise Server.
INITIALIZING SECURITY SERVER KERNEL
3940/616 MAIN_THREAD Sun Jul 29 05:24:30.224001 ODBC_U1.C902
ODB0000163 - wSQLNumResultCols failure. rc=-1
3940/616 MAIN_THREAD Sun Jul 29 05:24:30.225001 ODBC_U1.C902
ODB0000164 - STMT:00 [42S02] [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name 'JDE_PD910.F98710PD910FE'.
3940/616 MAIN_THREAD Sun Jul 29 05:24:30.227001 ODBC_U1.C902
ODB0000164 - STMT:01  [Microsoft][SQL Server Native Client 10.0][SQL Server]Statement(s) could not be prepared.
3940/616 MAIN_THREAD Sun Jul 29 05:24:30.229001 ODBC_U1.C910
ODB0000155 - SQLNumResultsCols failed. Table F98710PD910FE, ODBC DSN Central Objects - PD910.
3940/616 MAIN_THREAD Sun Jul 29 05:24:30.232001 jdbodbc.C3264
ODB0000027 - JDBODBC_DescribeTable failed. Table F98710PD910FE.
3940/616 MAIN_THREAD Sun Jul 29 05:24:30.234001 JDB_DRVM.C932
JDB9900168 - Failed to initialize db request
On newly installed Windows 2008 Enterprise server, all the Kernels are failing to connect to SQL Server 2008 database and showing below errors -
ODB0000164 - DBC:00 [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
1412/3340 MAIN_THREAD Mon Dec 01 20:43:27.082002 jdbodbc.C1354
ODB0000010 - SQLDriverConnect failed. ODBC DSN: JDESERVER.
1412/3340 MAIN_THREAD Mon Dec 01 20:43:27.082003 JDB_DRVM.C798
JDB9900164 - Failed to connect to JDESERVER
Scenario 1 : In this case System Data source was moved from a non-production database server to a production database server and the datasources pointing locations were also changed to point to the new database server.
Scenario 2 : Incorrect ODBC data source defination.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms