E2B Report Generation And Transmission Not Working For Active Enterprise
(Doc ID 2016910.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Argus Interchange - Version 7.0.5 and laterInformation in this document applies to any platform.
Symptoms
issue with E2B report generation and transmission. The Status of the transmitted E2B report is stuck in Transmit and the bulb was either green or yellow.
The AG and ESM logs do not show entries for the enterprise from where the reports are scheduled.
Found Below Error in Bulk Report Transmit E2B and Batch Report generation service logs when Verbose is enabled for AGProc.config located in C:\Program Files (x86)\Oracle\Argus\Argus Safety\ folder.
[EnterpiseID: GOLD SVT1 Formal] 19-May-2015, 08:36:21:237, [1], UserId: yage2b, Exit ADBObject::DirectSQL, Return Value: 1, Execution Time: 00:00:00:005
[EnterpiseID: GOLD SVT1 Formal] 19-May-2015, 08:36:21:257, [1], UserId: yage2b, Exception DetailsMessage
Error:1; Line: 7418: ERROR: Padding is invalid and cannot be removed.
Stack Trace
Changes
Enabled Data Lock Point in Argus Console -> system configuration -> system management ( common profile switches) , Modify Data Lock point Section.
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 |