E2b Bulk Transmit Screen Fails To Update the Status
(Doc ID 1340527.1)
Last updated on DECEMBER 31, 2024
Applies to:
Oracle Life Sciences 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 29-JUN-2017***
***Checked for relevance on 27-SEP-2020***
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"
"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
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 |