Troubleshooting EOIO stuck messages

 Sometimes, we get multiple messages stuck in PO in ' To be Delivered' status. 

The culprit here is that one message which is in System error (or in some rare cases Delivering status)

We have to find out that faulty message and resolve the error or we should cancel that message itself only if its a genuine error.

Go to Monitoring -> Adapter engine -> Additional Data -> Queues 

Here, check for any entries in the queue.

 Sometimes, we get multiple messages stuck in PO in ' To be Delivered' status. 

The culprit here is that one message which is in System error (or in some rare cases Delivering status)

We have to find out that faulty message and resolve the error or we should cancel that message itself only if its a genuine error.

Go to Monitoring -> Adapter engine -> Additional Data -> Queues 

Here, check for any entries in the queue.

Check for any entries here, if the message stuck in the file adapter then check the Filesystem queue & for any entries. (likewise for different adapters)

If any entries in the queue, find out the oldest one & resolve/cancel that message.

We can also check via RWB.

http://host:port/rwb/index.jsp

Configure Table columns (the marked icon in the bottom-right)

Select the below-highlighted options:

Apply and then sort as per the sequence number in ascending order.

As per the latest update by SAP dated 25 feb, 2021 

SAP has released a feature to help in monitoring of EOIO queues.

Check out the below note:

http://host:port/MessagingSystem/monitor/sequenceMonitor.jsp

----------------------------------------------AMOR FATI---------------------------------------------------------

Common SFTP channel errors/issues

 

Dangling Meta character issue :

Solution for Dangling Meta character issue :

Follow the below SAPNote.   Basically this issue occurs due to filenaming convention scheme.

Like file adapter, in SFTP * does not mean that it will accept all files.

In SFTP,    .*  is equal to * (as in FTP)

Cannot create target directory: Limit operation failed

Resolution:

This issue too is related to file naming convention in the receiver channel.

By putting a Tilde operator (~) in the beginning we can resolve this issue.

~ operator represents the Home directory for the user used in the channel configuration.

Ideally, without ~ operator too it should work but in some cases, we get the limit operation error.

Faulty path:  /To_FM

Corrected path:  ~/To_FM

--------------------------------------------------AMOR FATI---------------------------------------------------------