cancel
Showing results for 
Search instead for 
Did you mean: 

message in error NO_RECEIVER_CASE_ASYNC

pradeep_nellore
Participant
0 Kudos

Hi,

i face a problem with NO_RECEIVER_CASE_ASYNC

I followed the blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2748. [original link is broken] [original link is broken] [original link is broken]

I am splitting a file int 2 using transformation step.

File splitted , but both have same content.

Message is in following error.

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>

<SAP:Stack>No receiver could be determined</SAP:Stack>

Any other configuration need to be done??

Thanks

--Pradeep

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Error code NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC

􀃎 Inspect receiver determination area in SXI_CACHE

􀂄 If necessary, adjust the routing information in the Integration Directory

􀂄 If the message is asynchronous, it can be restarted manually, and manual

changes in the SOAP header are permitted

􀂄 Common causes of error are discrepancies between the configuration

and the SOAP header of the incoming message

􀂄 Sender service does not match (case-sensitive!)

􀂄 Sender interface name or namespace does not match (case-sensitive!)

􀂄 Condition for content-based routing has not been met

􀂋 Double-check message content

􀂋 Double-check condition (XPath expression or context object)

AND ALSO CHECK THESE FORUM LINKS

Regards,

Jayasimha Jangam

Answers (3)

Answers (3)

former_member192295
Active Contributor
0 Kudos

Hi,

This error due to improper ID configuration, take two communication channels in ID for receivers and configure accordingly, here one sender agreement and 2 receiver agreement will come. Configure properly

pradeep_nellore
Participant
0 Kudos

Hi,

u r right and they were alreday in place.

with one input file i am getting 3 messages in MONI.

one error message due to the above said reason.

Two messages which are recorded for outbound processing.

what could have happened??

Thanks

--Pradeep

former_member192295
Active Contributor
0 Kudos

Hi,

Check with service pack, some times SP9 and low service pack will give this problem

Check with receiver determination & interface determination configuration, in receiver service under inbound inerface we should add two interfaces

prateek
Active Contributor
0 Kudos

Recheck the ID configurations and make sure every object is activated. If the problem persists, make a full CPACache refresh.

Regards,

Prateek

Former Member
0 Kudos

Hi,

maintain receiver and interface determination in integration directory.

regards mario

pradeep_nellore
Participant
0 Kudos

Hi,

They are already in place.

Any other thing that needs to be done..

Thanks

--Pradeep