'Blank Casebook Report' / 'Patient Data Report' fails with 'RS_SUBMITFAILED' (via RDC Onsite 5.0.x) (Doc ID 1624602.1)

Last updated on FEBRUARY 14, 2014

Applies to:

Oracle Clinical Remote Data Capture Option - Version 5.0.0 and later
Information in this document applies to any platform.

Symptoms

i.

RDC Onsite 5.0.x : The 'Blank Casebook Report' / 'Patient Data Report' fails with the 'RS_SUBMITFAILED' status.

 

ii.

The following error appears in the 'C:\Oracle\Middleware\user_projects\domains\OPADomain\servers\OpaServer1\logs\OpaServer1-diagnostic.log' with RDC debugging enabled :

[ops$sbains@:VJNZS8cQbmQ2yNnyxNwM3jQVjdyh7Q2Xz9rw9vPZYcQLzvx89J6p!929215578!1392303184722] RdcHomeAction: before submitting report job
[2014-02-13T07:54:46.415-07:00] [OpaServer1] [WARNING:17] [] [oracle.pharma.rdc.logging.RdcLogger] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 18035db8bb0f6fa6:-71216e89:1442bbbf7ca:-8000-00000000000000a1,0] [APP: olsardc#5.0.0.0.40-b1] <![CDATA[error in patient report submit![[
java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [Failed to receive message java.net.ConnectException: Tried all: '3' addresses, but could not connect over HTTP to server: 'slc06ewz.us.oracle.com', port: '80'
 -> Tried all: '3' addresses, but could not connect over HTTP to server: 'slc06ewz.us.oracle.com', port: '80'
] FaultActor [null] Detail [<detail><bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.net.ConnectException: Tried all: '3' addresses, but could not connect over HTTP to server: 'slc06ewz.us.oracle.com', port: '80'
    at weblogic.net.http.HttpClient.openServer(HttpClient.java:333)
    at weblogic.net.http.HttpClient.openServer(HttpClient.java:425)
    at weblogic.net.http.HttpClient.New(HttpClient.java:252)
    at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:213)
    at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:398)
    at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:37)
    at weblogic.wsee.connection.transport.TransportUtil.getInputStream(TransportUtil.java:85)
    at weblogic.wsee.connection.transport.http.HTTPClientTransport.receive(HTTPClientTransport.java:270)
    at weblogic.wsee.connection.soap.SoapConnection.receive(SoapConnection.java:485)
    at weblogic.wsee.ws.dispatch.client.ConnectionHandler.handleResponse(ConnectionHandler.java:179)
    at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:287)
    at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:271)
    at weblogic.wsee.ws.dispatch.client.ClientDispatcher.handleResponse(ClientDispatcher.java:213)
    at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:150)
    at weblogic.wsee.ws.WsStub.invoke(WsStub.java:87)
    at weblogic.wsee.jaxrpc.StubImpl._invoke(StubImpl.java:341)
    at oracle.hsgbu.rdc.reports.ws.client.RWWebService_PortType_Stub.runJob(RWWebService_PortType_Stub.java

etc

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