cancel
Showing results for 
Search instead for 
Did you mean: 

No receiver could be determined

former_member192892
Active Contributor
0 Kudos

Hi Guys,

I'm doing a JDBC to RFC scenario. I'm getting a strange error as when the scenario runs for the first time, i get a "<b>No receiver could be determined</b>" error...

But when my JDBC sender polls the secon time onwards it works fine...

Can anyone tell me why this happens and what specific settings should i do to prevent this??

Thanks Guys

Accepted Solutions (1)

Accepted Solutions (1)

former_member614185
Contributor
0 Kudos

Check your RECEIVER DETERMINATION and RECEIVER AGREEMENT in the Configuration side

Answers (1)

Answers (1)

Former Member
0 Kudos

Hey

do u get any stuck up queues?possible areas which might give this error is connection between XI and RFC system(the first time connection fails) or something to do with RFC metadata.

also see ST22 and see if u got any dump

thanx

aamir

former_member192892
Active Contributor
0 Kudos

Hi Amir,

My scenario is that after my sender JDBC is polled, it is directed to a BPM...

So connection failure should not be an issue..

former_member192892
Active Contributor
0 Kudos

HI Prabhu,

Since the scenario is working fine from the second poll onwards, I don't think i'm getting wrong in receiver det and receiver agreement...

former_member614185
Contributor
0 Kudos

IF you are using BPM for ur scenario you need to create two receiver determination

1. JDBC to BPM(use Abstract interface)

2. BPM to RFC

Check your Determination step once again

former_member192892
Active Contributor
0 Kudos

Yes Prabhu,

I'm doing that... Also every thing works perfectly after the second JDBC sender poll.. Its just the first time i get this error..

Thanks

Varun

former_member614185
Contributor
0 Kudos

Varun,

Check your RECEIVER AGREEMENT SENDER SERVICE it should be your BPM