Crystal Reports CORBA communication failure - WSAETIMEDOUT

[Former Member]

The java client SDK blocks and ulimately times out when trying to retrieve the ReportClientDocument object from report server (XI)

ReportClientDocument clientDoc = reportAppFactory.openDocument(reportInfo.getID(), 0, java.util.Locale.getDefault());

On the client side get the following error message

com.crystaldecisions.sdk.occa.managedreports.ras.internal.a: Cannot initialize report application session. --- The request timed out because there has been no reply from the server for 600,000 milliseconds.

cause:com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: The request timed out because there has been no reply from the server for 600,000 milliseconds.---- Error code:-2147217385 Error code name:requestTimeout

detail:Cannot initialize report application session. --- The request timed out because there has been no reply from the server for 600,000 milliseconds.

The exception originally thrown was com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: The request timed out because there has been no reply from the server for 600,000 milliseconds.---- Error code:-2147217385 Error code name:requestTimeout

at com.crystaldecisions.sdk.occa.managedreports.ras.internal.RASReportAppFactory.a(Unknown Source)

On the RAS server log file

ErrorLog 2010 4 16 15:48:52.766 2316 4760 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]

[Fri Apr 16 19:48:53 2010] 2316 4760 (.\dts\dts.cpp:1794): trace message:

The firewall between client and server have been deactivate. The server does not create socket connection to the client SDK listener port but some port that is not open on client and thus the server netstat displays the connection in TIME_WAIT since it is trying to establish connection to the client on a port that is not open on client. My understanding is that the client listen port is specified by

System.setProperty("ooc.iiop.port", "6402");

The client is listening on this port but the server is not connecting back to this port.

The server is running on a VM.

Edited by: rawal1 on Apr 19, 2010 4:12 PM

[Former Member]

Hi,

I am too getting such error .

com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: The request timed out because there has been no reply from the server for 600,000 milliseconds.---- Error code:-2147217385 Error code name:requestTimeout

at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)

Some times report generates.As time goes on , this error msg started coming.Then we need to restart the report application server.After this it works fine .

Please advice .

[Former Member]

This was a network issue

[Adam_Stone]

You will also need to make sure that you are configuring the RAS service on the Enterprise machine. This is covered in the document discussing the SDK and firewalls available [here|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/0047e5f4-3140-2b10-1bae-de175e4c741c]

[Former Member]

Thanks for the feedback.

Problem persists. I don't have firewall on the client side or the server side. Still, I have set up requestport on the CMS server and RAS server for sake of trying all options. The client listens on explicit port for GIOP communication but the server attempts to establish TCP/IP connection back to client using a client port that is not opened on the client. I expect the server to do a call back on port specified by System.setProperty("ooc.iiop.port", "6402");

[Former Member]

Hi everyone -

I'm having the same exact issue. Do you guys know of any resolution to this?

Thanks!

Mas

[Former Member]

Problem : Windows localhost (jboss) to dev boe server - it works fine.

QA linux jboss to qa boe server (windows) works fine

UAT also works fine.

BUT DEV JBOSS to DEV BOE SERVER fails

I did get exactlty the same problem. there was a corba time out error in jboss. based on suggestion to use the trace, we requested the linux engineers to do the trace and they figured out after an analysis that the host file contains a 127.0.0.1( a loop back address) - BO SDK uses this file probably to tell the Crystal report server which server to connect back to give the response back to and when it encountered this loop back address (127.0.0.1) mapped to the host name it tries to send back the reply to it self as this is a loop back address.

SOLUTION:

So the solution finally is go to ur server ( linux server where ur jboss is running) and do a "cat /etc/hosts" ( with out brackets) It will show u the server name mapped to the ip address. If the IP adress shows as 127.0.0.1 please remove the address and give the correct ip address) (tell the n/w or linux people othewise if you are not sure )as they can give the appropriate address. This resolved our problem after days of struggle.