NO_RECEIVER_CASE_ASYNC

[Former Member]

Hi All

I am using PI 7.1 and working on a JDBC to Proxy scenario. Since both the 2 interfaces involved, does not require a Sender Proxy CC, I have created a single Service Interface with 2 different Operations and a single Service Interface with 2 Operations for Receiver JDBC CC. At Configuration I have created a Receiver Determination using the Interface Service only since Operations cannot be selected here. Similarly I have created a Receiver Agreement for the Service Interface, again we cannot select an Operation here.

After activating all the objects, I tried to test the scenario from RWB -> Integration Engine -> Test Message (using the ServiceName.OperationName) and I get the following error at SXMB_MONI:

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

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

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

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

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

Can anyone help on this issue? This would be of great help since this approach would reduce a substantial amount of work and also this is the right approach to use PI 7.1 multiple Operations of a Service Interface.

Thank you all in advance.

John Jeyaraj

[markangelo_dihiansan · Accepted solution]

Hello,

At Configuration I have created a Receiver Determination using the Interface Service only since Operations cannot be selected here.

It is possible to make the receivers operation specific by clicking the operation-specific radio button. Now as for the error, it is really on your configuration of the receiver determination Try looking for correct service interface name, namespace, configured receivers (party and comm components).

Hope this helps,

Mark

[Former Member · Accepted solution]

Mark

Thanks for your response. I configured the Receiver Determination for each Operation. Also I checked the Sender, Receiver Interface and the Namespace (I copy these from the Enterprise Service Builder). All the details are precise.

Could it be due to some BASIS issue? We have raised an OSS request to solve the communication error from ECC to PI Server. This is yet to be solved.

Thanks

John Jeyaraj

[markangelo_dihiansan · Accepted solution]

Hello,

Can you check if your changes are properly reflected in the cache? Go to ID -> Environment -> Cache Status Overview. Your changes should be green.

Hope this helps,

Mark

[Former Member · Accepted solution]

Mark

Thanks. I checked the Runtime Cache and it's green. Also I executed SXI_CACHE after made the change in the Receiver Determination.

Thanks

John

[Former Member]

Hi John,

In the receiver determination try using 'Test your Configuration' for testing the routing condition.

Regards,

Pranav

[Former Member]

Ram

Thanks.

I tested the configuration from ER. The error is displayed here too. Here is the trace:

Runtime error

No receiver could be determined

+ +

<Trace level="1" type="B">CL_RD_PLSRV-ENTER_PLSRV</Trace> <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace> <Trace level="1" type="T"> Cache Content is up to date </Trace> <Trace level="2" type="T">Start without given receiver </Trace> <Trace level="2" type="T">Using Receiver Determination 00000000000000000000000000000000 </Trace> <Trace level="1" type="T">No Relation found - accept given Receivers. </Trace> <Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace> <Trace level="3" type="T">...create rule engine </Trace> <Trace level="2" type="T">No Receiver found behaviour: 0 </Trace> <Trace level="1" type="E">CL_RD_PLSRV-ENTER_PLSRV</Trace>

Thanks

John

[markangelo_dihiansan]

Hello,

This is probably because you have an * in your sender party. Try recreating the receiver determination like this:

CommParty: leave blank

CommComponent: Your Component

Sender Interface: Your Interface

Sender Namespace: Your namespace.

Hope this helps,

Mark

[samiullah_qureshi]

I agree with Mark. Please try Mark's suggestion.

[Former Member]

Mark

The Sender Party is empty. I faced this issue with Sender RFC Adapter. Once this was removed the issue was solved momentarily. In this case the Sender Party is void.

Thanks

John

[markangelo_dihiansan]

Hello,

In your JDBC sender, go to processing and then look for the Document Name. This should match the name of the message type that you have configured in your service interface. If they are different, you would get the no receiver found error.

Hope this helps,

Mark

Edited by: Mark Dihiansan on Mar 22, 2011 10:06 AM

[Former Member]

Mark

I apologize for giving wrong info at the beginning. It's Proxy to JDBC and JDBC to Proxy

Thanks for this useful info. Currently I am using a Proxy to JDBC scenario. So there is no Sender CC involved here. Also for Sender JDBC CC, I cannot use multiple Operations for a single Service Interface. Here each Sender CC should have a different Select and Update Statement.

Once I am through I have to configure JDBC to Proxy scenarios. I am surely going to use your information.

Thanks

John

Edited by: John jeyaraj on Mar 22, 2011 10:26 AM

Edited by: John jeyaraj on Mar 22, 2011 10:28 AM

Edited by: John jeyaraj on Mar 22, 2011 10:40 AM

[markangelo_dihiansan]

Hello,

Can you check if the namespace of the message type that is declared on the proxy matches the declared message type namespace? When you double-click your message type, you will see a field there called XML Namespace, the namespace value there should match the value in your proxy.

Regards,

Mark

[samiullah_qureshi]

Are you still facing the problem "NO_RECEIVER_CASE_ASYNC" for ur proxy sender interface?

Scenarios in which, we dont need sender agreement(Proxy/Idoc Sender), sender business system name will be derived from the Logical System Name.

Open business system for ur ECC system in ID. Go to menu Communication Component -> Adapter Specific Identifiers.

Please check whether Logical System Name is appearing for ur business system for ECC.

[Former Member]

Mark

I am sorry to go off the track now...

I am executing a client proxy on the ECC system and able to see it using SXMB_MONI at the business system. There is no error thrown here. But this message is not to be seen at the Integration Server SXMB_MONI.

Could you please let me know what could be the reason?

Thanks

John Jeyaraj

[markangelo_dihiansan]

Hello,

Make sure you turn on sync logging. Goto sxmb_adm -> integration engine configuration -> change configuration (f9) -> set LOGGING_SYNC to 1.

Hope this helps,

Mark

[Former Member]

Mark

I tried with the config you had mentioned. Still I am not able to see the messages on the Integration Server.

Thanks

John

[baskar_gopalakrishnan2]

Just Few cents... Check your abap business system in PI and see that is configured for proxy between ECC and PI. . Also in your receiver determination, what you mentioned as sender system is not configured for proxy communication at ECC side.

Example PI's abap business system DS1CLNT140 vs client 140 in ecc

[Former Member]

Hi Mark

I have made a progress on sending data from client proxy to PI. But one last glitch; I am getting this error at SXMB_MONI:

<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>3: Unable to find URL for Adapter Engine af.xd1.blr-xdev-xxx</SAP:AdditionalText>

<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine</SAP:Stack>

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

</SAP:Error>

Could you please let me know what is this due to? What privileges do I have to have to prevent this error?

Thanks

John

Edited by: John jeyaraj on Mar 23, 2011 5:35 AM

[Former Member]

Thanks Baskar.

Currently the business system is configured to send data from ECC using a client proxy, but I am getting the following error at SXMB_MONI:

<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>3: Unable to find URL for Adapter Engine af.xd1.blr-xdev-xXX</SAP:AdditionalText>

<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine</SAP:Stack>

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

</SAP:Error>

Thanks

John

Edited by: John jeyaraj on Mar 23, 2011 5:33 AM

Edited by: John jeyaraj on Mar 23, 2011 5:34 AM

[markangelo_dihiansan]

Hello,

The error you have encountered is similar to this thread

(look for Michal's answer)

hope this helps,

Mark

[Former Member]

Hi Mark

Thanks for your response. I checked and the following values are already set.

com.sap.aii.adapterframework.serviceuser.name = PIAFUSER

com.sap.aii.adapterframework.serviceuser.pwd = *********

com.sap.aii.adapterframework.serviceuser.language = EN

I am providing the error message from sxmb_moni Trace XML. This could provide a lead, to solve this issue:

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

- <!--

Call Adapter

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Determining the sender agreement</Trace>

<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

- <!--

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>

<Trace level="1" type="T">User = PIAPPLUSER</Trace>

<Trace level="1" type="T">Message ID = 4D83C24C529D00F9E100</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">

<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>

<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

<Trace level="1" type="T">system-ID = XD1</Trace>

<Trace level="1" type="T">client = 230</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAPPLUSER</Trace>

<Trace level="1" type="Timestamp">2011-03-23T13:09:47Z CET</Trace>

<Trace level="1" type="T">ACL Check is performed</Trace>

<Trace level="1" type="T">XML validation is executed</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />

- <!--

-->

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

<Trace level="1" type="T">QOS = EO</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">

<Trace level="1" type="T">Queue name : XBTI0005</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

</Trace>

<Trace level="1" type="T">Generated prefixed queue name =</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!--

-->

<Trace level="1" type="T">--start determination of sender interface action</Trace>

<Trace level="1" type="T">select interface SI_Customer_Proxy_Send</Trace>

<Trace level="1" type="T">select interface namespace http://xxx.com/xxx/customer</Trace>;

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace>

<Trace level="1" type="T">Continue single processing</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = XD1</Trace>

<Trace level="1" type="T">client = 222</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAPPLUSER</Trace>

<Trace level="1" type="Timestamp">2011-03-23T13:09:49Z CET</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!--

-->

<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>

- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">

<Trace level="1" type="T">Reading sender agreement</Trace>

<Trace level="1" type="T">Message does not contain a sender agreement</Trace>

<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />

- <!--

-->

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT2->ENTER_PLSRV" />

- <!--

-->

<Trace level="1" type="T">number of receivers: 1</Trace>

<Trace level="1" type="T">Single-receiver split case</Trace>

<Trace level="1" type="T">Post-split internal queue name = XBTO2___0000</Trace>

<Trace level="1" type="T">Generated prefixed queue name =</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!--

-->

<Trace level="1" type="T">--start determination of sender interface action</Trace>

<Trace level="1" type="T">select interface SI_Customer_Proxy_Send</Trace>

<Trace level="1" type="T">select interface namespace http://xxx.com/xxx/customer</Trace>;

<Trace level="1" type="T">--start determination of receiver interface action</Trace>

<Trace level="1" type="T">Loop 0000000001</Trace>

<Trace level="1" type="T">select interface SI_Customer_JDBC_RCV</Trace>

<Trace level="1" type="T">select interface namespace http://xxx.com/xxx/customer</Trace>;

<Trace level="1" type="T">--no interface action for sender or receiver found</Trace>

<Trace level="1" type="T">Hence set action to DEL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace>

<Trace level="1" type="T">Continue single processing</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = XD1</Trace>

<Trace level="1" type="T">client = 222</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAPPLUSER</Trace>

<Trace level="1" type="Timestamp">2011-03-23T13:09:51Z CET</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!--

-->

<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>

<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>

- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">

<Trace level="1" type="T">Interface Mapping http://xxx.com/xxx/customer IM_Customer_Proxy</Trace>

<Trace level="1" type="T">ContentType application/xml</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_OUT">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!--

-->

- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">

<Trace level="1" type="T">Reading receiver agreement</Trace>

<Trace level="1" type="T">Outbound validation does not take place</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />

- <!--

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />

- <!--

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!--

-->

- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">

<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />

- <!--

-->

<Trace level="1" type="T">*error reading from exchange profile:Error when reading Exchange Profile*</Trace>

<Trace level="1" type="System_Error">Error while reading access data (URL, user, password) for the Adapter Engine</Trace>

</Trace>

</Trace>

<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!--

-->

</SAP:Trace>

I suppose the message is sent from the ECC system to PI server and after pipe line activities, it's not able to locate the receiver Adapter due to Exchange Profile error.

Can you please let me know if you could arrive at a solution for this issue.

Thank you so much in advance.

John Jeyaraj

[Former Member]

Hi,

We solved this problem two ways:

- By deleting Adapter Engine Cache (Short Term Solution) SXI_CACHE->Goto->Adapter Engine

- By restarting Java if first step doesn't solved it, but beware problem will re-appear very soon (max 1-2 days).

Another solution is to check if your SLD is consistent and apply latest Java SP.

Regards,

Gourav

[Former Member]

Hi Gourav

Thanks for your response. This issue is now solved just by stopping the JCO Provider at Java stack.

However the messages are still getting queued up in the ECC IE. Have to rectify this issue now.

Thanks once again.

John Jeyaraj