Corba communication failure

Hi everyone,
we have installed BOXI R2 SP2 in a windows machineA (all services and without clustering).
There is an application developed using BO SDK (java) deployed in Tomcat (machine B), than doesn’t work (it uses the RAS to load a Crystal report and export it in PDF format).
Viewing the log of the RAS server the error is :
“CORBA communication failure: reason[error number WSAENETUNREACH] minor[1330577418] reqType[154] agentId=[”"]"
Its sound like network configuration problem.

From BOXI Server (machineA):
we have ping machineB and nslookup machineB (FQDN) and nslookup IP-machineB.
There is no firewall configuration.
Do you have any idea?

thanks a lot.


spawn :es: (BOB member since 2007-07-12)

did you test the RAS and functionality outside of SDK app?


sfaridi :pakistan: (BOB member since 2002-08-29)

Hi.
Could you try to deployed the application in the same Tomcat where is deployed the BOE?
With this you can see if it’s a network problem or other thing.
Good luck!


Jaimepe :es: (BOB member since 2006-12-10)

Hi,
thanks for replies.
Yes, I have deployed the application developed against SDK in the BOXI enviroment machine and works fine! (all the components in machineA).

Bye


spawn :es: (BOB member since 2007-07-12)

Hi,

have you already found a solutions to the problem?

I am facing the same issue and don’t know how to solve it.

regards, reinhart


rherzog (BOB member since 2010-09-01)

Did you enable and configure a RAS server?


sfaridi :pakistan: (BOB member since 2002-08-29)

Whenever I hear corba errors, I go back to our worst problems - servers with multiple network cards. Do you have more than one nic in your server(s)?

If you do, you need to set the binding order so that your primary nic is the first - if corba tries to communicate “the long way”, going across subnets, it has all kinds of problems.

Just a thought,
B


bdouglas :switzerland: (BOB member since 2002-08-29)

Brent good to see you, how is everything still in Dayton?


sfaridi :pakistan: (BOB member since 2002-08-29)