My Oracle Support Banner

E1:BSSV: When trying to check-in BSSV Objects getting 'JDB9900436 - Cannot determine database driver name for driver type "E" and "OMW: Business Service checkin/save failure. Could not access temporary details table "error messages. (Doc ID 2748423.1)

Last updated on JUNE 07, 2021

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms


Tools Release: 9.2.5+

When attempting to check-in a BSSV object using OMW on-screen error message 'JDB9900436 - Cannot determine database driver name for driver type "E"' is seen.

 

In the related local jdedebug.log, errors are seen attempting to connect to F986020 in the Local datasoure, i.e. "OpenTable failed for the table F986020, in the data source, Local - DV920, with the JDEDB_ErrMsgType error of, 40".

Jan 12 23:09:27.036000 - 15492/11036 WRK:Starting jdeCallObject JDB9900436 - Cannot determine database driver name for driver type "E"

Jan 12 23:09:29.365000 - 15492/11036 WRK:Starting jdeCallObject JDB9900254 - Failed to initialize driver.

Jan 12 23:09:29.367000 - 15492/11036 WRK:Starting jdeCallObject JDB9909002 - Could not init connect.

Jan 12 23:09:29.370000 - 15492/11036 WRK:Starting jdeCallObject JDB9909100 - Get connect info failed: Transaction ID =

Jan 12 23:09:29.373000 - 15492/11036 WRK:Starting jdeCallObject JDB3100013 - Failed to get connectinfo

Jan 12 23:09:29.376000 - 15492/11036 WRK:Starting jdeCallObject Exiting JDB_OpenTable(Table = F986020) with Failure

Jan 12 23:09:29.376001 - 15492/11036 WRK:Starting jdeCallObject Entering JDB_GetLastDBError (hRequest 00000000)

Jan 12 23:09:29.376002 - 15492/11036 WRK:Starting jdeCallObject JDB9900224 - Failed to validate request handle

Jan 12 23:09:29.390000 - 15492/11036 WRK:Starting jdeCallObject Exiting JDB_GetLastDBError with Failure

Jan 12 23:09:29.390001 - 15492/11036 WRK:Starting jdeCallObject JDB_OpenTable failed for the table F986020, in the data source, Local - DV920, with the JDEDB_ErrMsgType error of, 40.

Jan 12 23:09:29.390002 - 15492/11036 WRK:Starting jdeCallObject OMW: Business Service checkin/save failure. Could not access temporary details table.

Jan 12 23:09:29.390003 - 15492/11036 WRK:Starting jdeCallObject OMWOLObject::ProcessRequest() main switch ended with 1

 

 

Alternatively, the on-screen error message may be related to E1Local, i.e. "Unable to connect to E1Local":

 

 

And, the same error messages are seen in the related local jdedebug.log:

jdedebug_5780_041221.log

Apr 12 15:17:43.201000 - 5780/6872 WRK:Starting jdeCallObject         Exiting JDB_OpenTable(Table = F986020) with Failure
Apr 12 15:17:43.201001 - 5780/6872 WRK:Starting jdeCallObject         Entering JDB_GetLastDBError (hRequest 00000000)
Apr 12 15:17:43.201002 - 5780/6872 WRK:Starting jdeCallObject         JDB9900224 - Failed to validate request handle
Apr 12 15:17:43.205000 - 5780/6872 WRK:Starting jdeCallObject         Exiting JDB_GetLastDBError with Failure
Apr 12 15:17:43.205001 - 5780/6872 WRK:Starting jdeCallObject         JDB_OpenTable failed for the table F986020, in the data source, Local - DV920, with the JDEDB_ErrMsgType error of, 40.
Apr 12 15:17:43.205002 - 5780/6872 WRK:Starting jdeCallObject         OMW: Business Service checkin/save failure. Could not access temporary details table.
Apr 12 15:17:43.205003 - 5780/6872 WRK:Starting jdeCallObject         OMWOLObject::ProcessRequest() main switch ended with 1
Apr 12 15:17:43.216000 - 5780/6872 WRK:Starting jdeCallObject         OMWEnvironmentContext::EndTransaction() - Rolling back transaction because bCommitOrRollback is FALSE and m_bTrxCommit is TRUE




Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.