My Oracle Support Banner

E1: OMW: Random Error 'Bad Handle' Appears while Working in OMW (Doc ID 1312596.1)

Last updated on JUNE 22, 2017

Applies to:

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

Symptoms

While performing different actions in OMW, users sometimes see error message "Error: Bad Handle". The error appears at random and Windows client might become unresponsive. Usually logging out the EnterpriseOne client and logging back in resolves the issue until the error appears again.



The respective jde log file will usually contain the following error messages:

3972/1400 WRK:Free Remote Env Fri Mar 25 15:18:25.605000 Jdekfree.c185
KNT0000014 - JDENET Error = 8

3972/1400 WRK:Free Remote Env Fri Mar 25 15:18:25.605001 Jdb_ctl.c6823
JDB4200003 - OPEN TABLE NOT CLOSED = F98210, opened from File=OMWRDBAccess.cpp, Function=OMWRDBAccess::OpenRDB, Line=129.

3972/1400 WRK:Free Remote Env Fri Mar 25 15:18:25.855000 Jdb_ctl.c6823
JDB4200003 - OPEN TABLE NOT CLOSED = F98211, opened from File=OMWRDBAccess.cpp, Function=OMWRDBAccess::OpenRDB, Line=129.

3972/1624 WRK:Starting jdeCallObject Fri Mar 25 15:29:36.238000 Jdedebug.c4275
PSTHREAD_MTX: psthread_mutex_lock() invalid handle

3972/1624 WRK:Starting jdeCallObject Fri Mar 25 15:29:36.238001 Jdb_exet.c5501
JDB3400004 - Failed to validate Request handle
...
3972/1624 WRK:Starting jdeCallObject Fri Mar 25 15:58:03.016000 OMWEntry.cpp311
OMWMethod : eDESIGN -- OMWExceptionError caught. Error : Attempting to get NULL Manual hUser.

3972/1624 WRK:Starting jdeCallObject Fri Mar 25 15:58:04.001000 Jdb_ctl.c6709
JDB4200001 - Failed to validate User handle
...

Changes

 

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
Changes
Cause
Solution


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