Unable to find channel ID at inbound SOAP Adapter

[Former Member]

Hi experts,

I encountered a very puzzling problem:

I have a scenario:

IDOC -> XI -> SOAP

For 2 interfaces of such nature, 1 works fine, 1 doesn't.

The one that does not work is throwing the following error in RWB - Message Display Tool (MDT):

2007-03-22 10:57:05 Success The message was successfully received by the messaging system. Profile: XI URL: http://ootspdbs02:50100/MessagingSystem/receive/AFW/XI

2007-03-22 10:57:05 Success Using connection AFW. Trying to put the message into the receive queue.

2007-03-22 10:57:06 Success Message successfully put into the queue.

2007-03-22 10:57:06 Success The message was successfully retrieved from the receive queue.

2007-03-22 10:57:06 Success The message status set to DLNG.

<b>2007-03-22 10:57:06 Error Unable to find channel ID

2007-03-22 10:57:06 Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: a277e57c-c837-e44f-9ae2-da0d701980c4. </b>

2007-03-22 10:57:06 Success The asynchronous message was successfully scheduled to be delivered at Thu Mar 22 10:58:06 SGT 2007.

2007-03-22 10:57:06 Success The message status set to WAIT.

In SXMB_MONI, it shows the message has been processed successfully - indicating that the mapping is fine. Status = Awaiting acknowledgement.

I've looked up the forums, and the general solution offered is to refresh the SLD cache.

I've tried that, but it doesn't work.

Please help.

Thanks.

Ron

[bhavesh_kantilal · Accepted solution]

Ron,

Look if the Receiver Agreement for the seconds interface is create and it has been activated?

Regards

Bhavesh

[Former Member · Accepted solution]

> Ron,

> Look if the Receiver Agreement for the seconds

> interface is create and it has been activated?

>

> Regards

> Bhavesh

It's there and Status is active.

Is there something I missed?

My other interface is built using the same approach and it works fine.

[bhavesh_kantilal · Accepted solution]

Ron,

Is one of the intreface an asynch and the other a Synch?

Can you just try using a separate communication channel and checking the same?

Regards

Bhavesh

[Former Member · Accepted solution]

> Ron,

> Is one of the intreface an asynch and the other a

> Synch?

>

> Can you just try using a separate communication

> channel and checking the same?

>

> Regards

> Bhavesh

Both scenarios are async.

They are using seperate communication channels, because they are consuming 2 different web services.

I also noticed in Adapter Monitoring, only the first communication channel (The one that is successful) is displayed.

After performing a full CPACache refresh at http://ootspdbs02:50100/CPACache/refresh?mode=full ,

I tried both interfaces, and again, the first one was successful, but the second one failed.

Please help.

Thanks.

[bhavesh_kantilal · Accepted solution]

Looks like some issue with the cache.Can you look into the integration directory --> Cache Notifications and see if the cache refresh is in Green?

Regards

Bhavesh

[Former Member · Accepted solution]

> Looks like some issue with the cache.Can you look

> into the integration directory --> Cache

> Notifications and see if the cache refresh is in

> Green?

>

> Regards

> Bhavesh

In Cache Notification, the cache refreshes are all green.

In SXI_CACHE, I can see that the correct communication channel is tied to the receiver agreement.

[bhavesh_kantilal · Accepted solution]

hmm.. then things not a problem with the cache.

Is the error in MONI? Or is it in the Adapter Engine?

I know it isrepeatitive, but checking if the Objects are all active and correct in the ID is the only solution I can suggest.

Regards

Bhavesh

[Former Member · Accepted solution]

This is so strange, I attempted to change the communication channel to a file receiver, but I still encounter the same error!

[Former Member · Accepted solution]

HI,

to refresh cache ,please see the below links

Cache Contents Are Obsolete

/people/sravya.talanki2/blog/2005/11/03/cache-refresh-errors--new-phenomena

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01...

Regards

Chilla

<i>reward points if it is helpful..</i>

[Former Member · Accepted solution]

> hmm.. then things not a problem with the cache.

> Is the error in MONI? Or is it in the Adapter Engine?

>

>

> I know it isrepeatitive, but checking if the Objects

> are all active and correct in the ID is the only

> solution I can suggest.

>

> Regards

> Bhavesh

In the MONI, the status is successful, awaiting acknowledgement.

After sometime, the ack status will be "Acknowledgement contains System Errors"

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

<SAP:Code area="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>

<SAP:P1>,BS_DEV1_NAUTICUS_OOTS</SAP:P1>

<SAP:P2>,BS_NHGDDBS01,,</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>

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

But I don't think these are related, because the message wasn't sent out, naturally there's an error in the ack.

[Former Member · Accepted solution]

Thanks Guys,

I think I've found the solution:

My message interface length is too long:

Old message Interface: MI_PatientDemographics_Inbound_Async_UpdatePatientDemographic_NEW

I changed the message Interface naming to:

MI_Inbound_Async_UpdatePatDemoInfoToOOTS

There seem to be a restriction on the length of the naming conventions in XI.

If the naming exceeds 60 characters, they'll have problem parsing the message.

I changed the naming, and now the message is going through.

Thank you all for your help.

Cheers.

Ron

[Former Member · Accepted solution]

Hi Wee,

We have the same issue and i dont think so its related to the interface name length because our interface was running fine suddenly we are faced with this error

rgds

aditya