RFC Adpater Issue

[macds]

Hi,

I've created a process in XI that is a synchronous process to an SAP backend (4.6c system) using the RFC adapter.

The flow is HTTP call inbound -> RFC call outbound

It was working fine until a couple of days ago.

In the message flow (and in test configuration) I can see the flow going all the way through to the reciever determination. However, the RFC call to SAP timesout with no response.

I've checked the logon to the back end system, this is ok.

I can ping the system from the XI box.

I've de-activated and re-activated the RFC receiver.

I've created a new RFC reciever and activated it.

Nothing fixes the problem and I have no idea where else to look.

Can anyone assist me please ?

Cheers

James

[Former Member]

Hi,

If possible restart the server and then try.

Regards,

Sarvesh

[macds]

The server has been restarted a few times.

[Former Member]

Hi James,

Do you really need gateway host n gateway service?

Could you try just putting host name, system no and logon details.

Regds

Pushkar

[macds]

Hi Pushkar,

no but they were a couple of things we did to try and get connection.

Just the host name, system number is not working.

Cheers

James

[Former Member]

Hi,

I alos have the same issue . How was it resolved ?

Thanks,

Suman

[Former Member]

Hi James,

perhaps its a timeout because of the mass of data. I had a similar case where my RFC timed out and i did not know why. Then i saw that he had to process about 200.000 lines with one select statement, i reduced this and now the rfc worked and did not time out any more.

perhaps it helps

Regards Christian

[macds]

Hi Christian,

No, I don't believe that is the problem. It is a 1 record in 1 record out call that takes less than 1 second to execute.

I don't think the RFC call is even getting to the R/3 box.

No idea why at the moment.

[macds]

Just to add, this is the error I see in the message log;

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Inbound Message

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: No response available.</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

I get this even if I disable the RFC service in the J2EE visual administrator

[Former Member]

>

. However, the RFC call to SAP timesout with no response.
> James

James,

Copule of things here....

One... did you execute the function module on the backend r/3 system with the same data which is being passed from xi to check if it is generating any excpetion?

Also check how long does the FM/BAPI take for execution...

Also I would say... increase the RFC Adapter timeout parameter on XI J2EE. using the Visual Admin

Award points if helpful.

Cheers!!

Sidharth

[macds]

Hi Sidharth,

Yes, I can test the RFC in the backend system with the same data. It works with no problems.

It takes less than one second to run ! Also, it has no exceptions, just a return table.

I have just found out there was an issue with the system XI is on and a system restore happened last week (still 2 weeks after everything was working).

I've tried clearing the cache and de-activating/activating everything but still no luck.

Cheers

James

[Former Member]

Just a try..

Could you please create an RFC destination in XI using the same user id and check if you are able to do a remote log on to the target sap system.

regds

Pushkar

[macds]

Hi Pushkar,

Created an RFC destination in SM59 to the R/3 system. Add the user ID and the connection test was successfull

Cheers

James

[Former Member]

Hi James,

Connection test is successful even if you provide the wrong user id or pwd.

Did you try doing remote logon?

Regds

Pushkar

[macds]

OK, this is odd.

I tried remote logon and it failed.

I spoke with basis and they set up a new connection, they told me it worked. I asked them to show me and it failed !!!!

They entered a gateway in the SM59 connection and it worked on the first clisk of remote connection. Second try failed. Every try afterwards failed.

Entered a application server, first try works every other attempt fails ????

On the R/3 server there is a gateway error appearing;

Thu Apr 10 10:37:51 2008

***LOG Q0I=> NiPServToNo: getservbyname [niuxi.c 552]

***LOG Q0A=> NiIServToNo, service_unkown ( sapgw10) [nixxi.c 2337]

• ERROR => GwIConnectToGw: NiConnect to 10.2.0.190 / sapgw10 failed (rc=NIESERV_UNKNOWN) [gwxx.c 528]

***LOG S0T=> GwIConnectToGw, NiConnect (-0003) [gwxx.c 534]

***LOG S0R=> GwIConnectToGw, NiConnect () [gwxx.c 539]

***LOG S0S=> GwIConnectToGw, NiConnect (sapgw10) [gwxx.c 543]

• ERROR => R3IConnectWithRemGw: GwIAsyncConnSend failed (665) [gwr3cpic.c 6567]

Basis say sapgw10 does exist.

However, when I run the flow on XI, I don't see this error appearing on the R/3 server.

[Former Member]

James,

Check with the Basis if the connection is reaching the backend system. The ususally monitor the gatway and can tell whether a session/connection was innitiated.

This will help us locate the actual error (whether in XI or in R/3)

Also I would recomed a full cache refresh.

Ensure you delete the adapter engine cache in sxi_cache transaction before you execute the message.

Regards,

Sidharth

[macds]

HIi Sidharth,

Refreshed the cache and deleted the adapter engine entry. No difference.

Basis tell me there is no connection being established to the R/3 server.

Cheers

James

[Former Member]

Hi,

Check the user which is used in RFC is not locked. May be password has expired and it get locked.

Check it by using transaction code SU01.

Regards,

Sarvesh

[macds]

Hi Sarvesh

First thing I checked, and the user ID is unlocked and the password has not been changed.

James

[Former Member]

Seems like a firewall or network problem...especially if everything was working before and you didn't change anything. Are both systems behind firewall? Maybe somebody blocked incoming packets from your ERP system on ports RFC is using?

Regards,

Elvis

[macds]

Hi Elvis,

Thanks for responding so quickly.

I don't believe it is a firewall or network problem. In the designer, I can still connect to the same R/3 backend to import other RFC functions.

Both the systems are on the same network.

I've had basis check this and they can't see an issue with the network.

Cheers

James