E2b Bulk Transmit Screen Fails To Update the Status (Doc ID 1340527.1)

Last updated on JUNE 29, 2017

Applies to:

Oracle Argus Safety - Version 5.0.0 to 7.0.0 [Release 5.0.0 to 7.0.0]
Information in this document applies to any platform.
***Checked for relevance on 24-Dec-2012***
***Checked for relevance on 23-Jul-2014***
***Checked for relevance on 29-JUN-2017***

Symptoms


E2b Bulk Transmit screen fails to update the status. It writes the following message in the ESM Status Check log file:

"11-Jul-2011 5:52:40 PM: ========== Start Transmit Process ========== "
"11-Jul-2011 5:52:41 PM: ESM Service Login to 'xxxx101' Database with UserID 'esm_login' Successfully"
"11-Jul-2011 5:52:41 PM: ESM Proc for StatusCheck"
"11-Jul-2011 5:52:41 PM: System unable to delete the E2b report, Report ID = 29. Report is processed by the ESM."
"11-Jul-2011 5:52:41 PM: System error has occurred in Main ESMProc Fn, error number = 53 error desc. = File not found error source = E2bProc"

 

Cause

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