AERS 4.6.1.291 Fails Periodically In Running A Report Job; AERS Reports Unable To Connect (Doc ID 1456375.1)

Last updated on APRIL 04, 2016

Applies to:

Adverse Event Reporting System - Version 4.6.1 to 4.6.2 [Release 4.6.0]
Information in this document applies to any platform.
***Checked for relevance on 03-NOV-2014***

Goal

Recently patched Development environment from 4.6.1.19 to 4.6.1.291.

Report server was booted at some point in time.
At some time AERS started failing generating a report; message:

 

############
Run Report Failed
FRM-41213 Unable to connect to the report server AERSrepxxxx
#############




AERS failed consistently. It was realised that Windows Firewall was running.
Firewall service was stopped and disabled.


Running reports worked again for some hours; then periodically it fails again.

It fails more than it succeeds.



No errors or logging at all around the times where report generation fails.


There is however a 'org.omg.CORBA.COMM_FAILURE' around the where report run succeeded?

e.g.

 

 

[2012/3/1 11:22:45:610] Exception 50125 (org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 208 completed: Maybe
at com.sun.corba.se.internal.iiop.IIOPConnection.purge_calls(IIOPConnection.java:438)
at com.sun.corba.se.internal.iiop.ReaderThread.run(ReaderThread.java:70)
): Internal error org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 208 completed: Maybe
[2012/3/1 11:22:45:610] Debug 50103

Solution

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