E2B'S Scheduled/Generated via Periodic Reports are Pending and do not get Transmitted to ESM Out Folder
(Doc ID 2202527.1)
Last updated on DECEMBER 23, 2024
Applies to:
Oracle Life Sciences Argus Safety - Version 7.0.6 and laterInformation in this document applies to any platform.
Symptoms
On Applications Oracle Life Sciences Argus Safety Version : 7.0.6
Ran a periodic report a week ago to generate a set of XML files for a project and since then see 8 reports are pending.
Observed that reports for all problematic cases are generated successfully but transmission status appear as pending and file never created on ESM server.
In the Transmission logs do see some reports were skipped e.g.
15-Sep-2016, 04:10:03 >> Bulk Report Transmit E2b > "C:\Program Files (x86)\Oracle\Argus\Argus Safety\AGProc.exe Bulk Report Transmit E2b Bulk Report Transmit E2B" started.
15-Sep-2016, 04:10:05 >> Bulk Report Transmit E2b > ARGUS 7 PROD: 41 reports processed. 0 success, 0 failed, 41 skipped.
Expectation is that xmls are created in outgoing ESM directory
The original Periodic Report included and generated 1274 ICSRS for cases.
Most of these transmitted just fine to same outbound xml directory only 8 remain 'pending' with no transmission or warnings.
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 |
| References |