DUMP: Bean <name of the RFC> not found on host <host>" exception

[former_member910257]

Hi,

I created an Interface RFC --> PI --> SOAP.

I created a report to call the RFC function module using an RFC Destination type  "T"  TCP / IP to start the interface

When calling the function it gives the following dump:

ECC does not leave the message to the PI

My RFC Destination is set in SM59 and the test was successfully.

And my Adapter RFC Sender is configured with the same program ID

someone there can help?

tks

[former_member314770]

Hi Adilson,

Can you please do a quick test here? Asuming you haven't registered your program in PI side explictly (which is not required anyways), please stop the sender RFC channel and try doing the connection test from SM59 (ECC) side one more time. Ideally, it should fail with Progam ID not registered error. If you see any other error, you may need to revisit your RFC connection settings.

At this time , I am also assuming below points are already taken care of.

1. Firewall between ECC and PI is up and running with out any issues.

2. RFC destination name is same as Program ID (check out for invisible space(s)

3. Host name, gateway details (as mentioned in SM59) are correct and exactly matches that in RFC sender channel.

Also, can I please request you to knidly share more dump details? One shared above is very high level.

Thanks,

Anir.

[former_member910257]

ANIRBAN,

I stopped the CC RFC Sender, but gave the same error, because the error occurs before calling the CC RFC Sender.

So I put a progam different ID in SM59 that is not registered in the JCo and he returned the error below:

"Transaction program not registered"

Then it is correctly recognizing the ID Program.

One thing I noticed is that the error is intermittent, because there are times that works perfectly, correctly returns the search on SOAP, just need to do 15 attempts to run. without changing anything.

[former_member314770]

Hello Adilson,

You might have encountered "Transaction program not registered" error this time because CC might have been stopped when you executed the RFC or SM59 connection test from ECC. This is extactly what we wanted to test here, just to make sure there is no other connection error causing the issue.

For T type RFC connection there is no need for JCO settings in NWA seperately. Only SM59 configuration is enough, also CChannel should be running of course when the RFC is invoked else you will get '"Transaction program not registered" error. Please try now and let us know the results.

Also please make sure your ECC hostname and gateway infomration is correct in SM59 settings.

Thanks.

Anir.

[former_member910257]

Hi Anirban,

The name of the host ECC and gateway information is correct in SM59 yes, I checked again.

Even if I insist for 10 or 15 times one often ends up running at full inteface correctly, but then I run again and already back to give error.

An intermittent error that could not identify because it does not work at all times, and I'm not changing anything.

[former_member314770]

Adilson,

Sorry was out of SCN for past few days, hence the delay to answer.

Can I please request you to shate the error in details ?

If I undertsand, you are getting this error intermittently in ECC side ( messages does not post in PI)?

Also, 1 out of 10(or 15) attempts are successful.

Thanks,

Anirban.

[former_member186851]

Hello Adison,

Did you register the program Id in the PI and use the Same in SM59 connections?

[former_member910257]

Raghuramadid you mean the JCo RFC Destinations?

In the SAP PI is so: