Exception in Message Monitoring when failed message is cancelled

Hi All,
I need some info regarding this.
In message monitoring a message from Sender A to Sender B fails and gets into "waiting" mode.
When I cancel this message, I immediately recieve an Exception message from Sender B to Sender A. I have not done any specific configuration for this.
This happens as many times as I cancel the message. I receive one exception message from the reciever to sender for one failed and cancelled message.
I am working on PI 7.1 and recently the system was upgraded to Service Pack 09. Has somebody faced this or can throw any light on this?
Thanks,
Rashmi.

The following are the message details.
Time Stamp Type Description
2010-05-21 07:25:06 Information Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2010-05-21 07:25:07 Information Message successfully put into the queue.
2010-05-21 07:25:07 Information The message was successfully retrieved from the receive queue.
2010-05-21 07:25:07 Information The message status was set to DLNG.
2010-05-21 07:25:07 Information The message was successfully delivered to the application using connection File_http://sap.com/xi/XI/System.
2010-05-21 07:25:07 Information The message status was set to DLVD.
Pasted below is the line from message monitoring.
End-to-End Information                  -
Status                                           Successful
Start                                              21.05.2010 07:25:06
End                                                21.05.2010 07:25:07
Sender Party
Sender Component                        SystemB
Receiver Party
Receiver Component                     SystemA
Interface                                        Exception
Message Format                            XI Message
Please, let know if anybody knows anything about this.

Similar Messages

Resending the Mesage in Message Monitoring is failed again & again

H i ! All
In Scenario Idoc to File , the connectivity between XI server & FTP was down , Now is up ,
a message is failed , now again i am re-sending the message from Message Monitoring , showing the belolw error , FTP Connection is UP now , in SXMB_MONI message is processed
Exception caught by adapter framework: An error occurred while connecting to the FTP server '10.10.100.205:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 /STORES/102/sapoutbound: The system cannot find the path specified. '. For details, contact your FTP server vendor.
what can be the reason ???
Thanks
Abhishek

The prolem is stil the same .....
today more than 300 mesages get prossed . I can see on FTP , but 23 messages get failed ....using same communication channel ....
I am putting the details
Sucessed messges
Write to FTP server "10.10.100.205", directory "\STORES\0019\sapoutbound", file "ZINV01_ZINVMSG_001920090705-172939-687.XML"
failed messages
Exception caught by adapter framework: An error occurred while connecting to the FTP server '10.10.100.205:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 /STORES/193/sapoutbound: The system cannot find the path specified. '. For details, contact your FTP server vendor.
Thanks
Abhishek
Edited by: Abhishek Agrahari on Jul 6, 2009 8:00 AM

Monitoring of failed Messages in XI.. Any one place to see them???

Hi All,
Is there any place where we can see all the failed messages for particular week or particular month in XI.
Like in SAP, we can go and see in WE02 transaction where we can see all the failed idocs.
In the same way is there anyway where we can see the failed messages in XI??
I know in SXMB_MONI, we can see only the ones which fails at integration engine and in RWB , we need to select particular selections to go and see the failed ones at Adapter engine level.
As a functional people point of view, if they want to see the all the failed ones in XI.. which one place i can suggest to see them... instead of going 2 places like SXMB_MONI and Runtime Workbench.
Waiting for your answers.
Regards
Deepthi.

From my point of view RWB is best option because you can filter messages there with error, with success and with all differenr options.
But in case of MONI sometimes, messages sometimes have problem on sender side and it may happen it will not be seen in MONI.
So RWB can be used for testing as well as viewing the message status.
but only the concern is functional guy should have knowledge of it, because it is only part of XI system and on other hand MONI is available on both R3 and XI.
BR,
Alok

PI 7.1 SOAP Adapter - Message Payload for Failed Messages - Where to find

We are exposing a webservice through SAP PI. Occassionaly we have customers calling our webservice and some failure occurs. The error is usually the way that the customer is calling the webservice (missing elements, misnamed tags, bad content in the WS payload..). Generally in these cases we can see the error in communication channel monitoring.
Here is an example:
12/12/11 4:39:07 PM com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-complex-type.2.4.b: The content of element 'SupplierInvoice' is not complete. One of '{"":Invoice}' is expected. at line 1, column 227
12/12/11 4:39:06 PM request received for a channel
I understand the issue, but it would be extremely helpful to have the full SOAP Envelope and Payload of a request when it fails. The communication channel will show a SUCESSFUL message payload with a link to it. But it does not show a failed one.
Where can I find the FAILED payload that accompanies this message? These failures occurs before any mapping or being seen in RTWB Adapter Engine message monitoring... I did some searching around, but did not find anything offhand. I would greatly appreciate any pointers from anyone who has crossed this bridge.

Hi,
When the web service is being called by external application, the first point of contact would be the sender communication channel which converts the SOAP message into XML message and pass to integration engine ( In case of success )
But if the web service call fails due to WSDL validation, Authentication issue, Bad content, invalid content type, you would not see the payload in the sender communication channel or in Adapter engine. You can just see error message in the sender communication channel . I have experienced this many times and i always ask the web service team to provide the SOAP message for validation/investigation purpose.

Message monitoring of synchronous messages

Guys,
whenever I check a synchronous message in message monitoring, its audit log is correctly shown but the message (header and payload) are not shown, returning the message "The message was deleted to save memory" or something like that.
Does anyone knows how to enable message monitoring to show the messages from sync messages?
Thanks in advance,
Henrique.

Hi Henrique,
From SP12, the payload of sync messages is cached in memory rather than persisted. These payloads are deleted to prevent them from accumulating in memory.
You just have to set:
messaging.syncMessageRemover.removeBody = false
in the AF messaging service in the visual admin
and you'll be able to trace sync calls
you only need this for sync
if you set this you'll see sync messages in,
http://hostname:portnumber/MessagingSystem/monitor/monitor.jsp
(so in the monitor for adapters)
async are logged there by default so no need to change anything for async calls...
Regards,
Abhy
Message was edited by: Abhy Thomas

Send email to Message Creator when Support Message status is changed

Hi Pradeep,
Have you given the partner function tick in the action?
Have you activated the smartform?
Please check and tell.

Hi Raj,
Thanks for the reply.
I have entered the Partner determination for the the Action.
SLFN002-- Reported by
i have also assigned the Smart Form mail in the Processing type.
Regards,
Pradeep L

Reg : Reprocessing of failed messages in SAP PI 7.3.1 Single Stack

Hi All,
          I am working on FILE to IDOC Interface. I have encountered a new problem today.
          When we started testing this interface, the message were failing at the IDOC Adapter.
          When I debuged the error, I found that, we were passing chars for a Date Field in IDOC.
           I updated the mapping on the same and when I tested the Interface it works fine end to end.
          However when I want reprocess the failed message from monitoring, the failed messages are being reprocessed from the point of failure and not from the beginning of Pipeline
          Since the changes are made at the mapping , none of failed messages are being processed.Did any face the same issue and how did u guys resolve it. Can you please help me on this.
Thanks
Siva

Hi Siva
That is the correct behavior in PI. Reprocessing of failed messages are always restarted from the point of failure and not the beginning of the pipeline.
If you want the messages to start at the beginning of the pipeline, you need to resend them, in your case, put the file in the source directory.
Rgds
Eng Swee

Resend messages in Message monitoring

Due to some DB issues, my message through JDBC adapter (receiver - asynch) could not be delivered (after 3 retries). After the retries were over, I was able to fix the DB issue. But When I try to resend from Message monitor, resend fails with message "Cannot retry message guid (INBOUND); reason: null. " How do I resend this message?

Hi,
Check out this blog by Michal
/people/michal.krawczyk2/blog/2005/11/09/xi-restarting-successfully-processed-messages
also this thread...
Restart Message in SXMB_MONI

Trace level of RWB's Message Monitoring - Detail Message - Tab "Audit log"

Hi,
My flow is: File -> PI -> Transformed File with seeburger module. Everything is good except the trace level in RWB.
Exactly, in our PI production, under RWB -> Message Monitoring, when I select a message (e.g PI -> Outside) and see its Detail, under tab "Audit Log", I have a log with only 2 pages (which corresponds to the sender part "File -> PI")... whereas in our PI pre-production, I have 4 pages for the exact same flow, on which I have also info of the receiver part "PI -> Outside"...
My question is just: do you know which parameter is involved in this trace level of RWB's Message Monitoring Detail log ?
regards.
Mickael
Note: in [Help SAP|http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/frameset.htm], I see only this sentence "Audit Log: The audit log for the selected message is displayed as the default setting.".
Edited by: Mickael Huchet on Oct 18, 2011 1:59 PM

Hi Shabarish,
Thanks that will help to localize my search.
else by hazard, you don't know which parameter in this tree is for the "Audit Log"?
coz I did a quick look in prod and pre-prod, but it seems the severity is the same (e.g "Info" for most of them) whereas the trace level of "Audit log" is different.
Thanks for
Regards.

Failed Message Routing - Generic Error Description - why?

Hi,
I have developed a custom pipeline component but when it throws an exception, it throws a generic exception description, as follows:
"The Message Engine encountered an error during the processing of one of or inbound messages"
I have 'Failed Message Routing' enabled on my port and an orchestration that subscribes to these failed messages.
But I'm creating my own custom error description, with information I use further down the process, this custom description gets overwritten by Biztalk somewhere after been thrown.
Is there a reason for this? And is there a way to work around this?

Thanks for your reply.
I'm trying to get a value from the using XPathReader
Here is a snippet of my code
Stream inboundStream = bodyPart.GetOriginalDataStream();
VirtualStream virtualStream = new VirtualStream(bufferSize, thresholdSize);
ReadOnlySeekableStream readOnlySeekableStream = new ReadOnlySeekableStream(inboundStream, virtualStream, bufferSize);
XmlTextReader xmlTextReader = new XmlTextReader(readOnlySeekableStream);
XPath.XPathCollection xPathCollection = new XPathCollection();
XPathReader xPathReader = new XPathReader(xmlTextReader, xPathCollection);
xPathCollection.Add(XpathValue);
bool ok = false;
string Value = string.Empty;
while (xPathReader.ReadUntilMatch())
if (xPathReader.Match(0) && !ok)
if (xPathReader.NodeType == XmlNodeType.Element)
xpathValue = xPathReader.ReadString();
else
Value = xPathReader.GetAttribute(xPathReader.LocalName);
ok = true;
DateTime.TryParse(Value, out myDate);
readOnlySeekableStream.Position = 0;
bodyPart.Data = readOnlySeekableStream;
if an Exception happens anywhere before this code or even during this code snippet, I get my custom error description but when the code exits the 'while statement' and if an exception happens, I get the generic error description - "The Message Engine
encountered an error during the processing of one of or inbound messages"
Does something happen the stream when it is used in XpathReader?
Thank you

Wrong port in FTP receiver adapter - no errors in message monitoring?

Hello all
We're on XI 3.0 SP16 and have created / configured a HTTP XML -> XI -> FTP Server scenario. In the receiver comm. channel (ftp) we had specified a wrong port number and always wondered, why we never got errors in message monitoring. Everything seemed to be processed correctly... but no file arrived on the FTP server (receiver) side!
After correcting the wrong FTP port number in the receiver FTP comm. channel everything went fine.
We now encountered a similar problem with a RFC receiver adapter. We're using it in another scenario HTTP XML -> XI -> RFC to SAP R/3 (4.7).
For some reason it died (red status in adapter monitor) and it was no more possible to do RFC calls from XI to SAP R/3 (normal RFC adapter, NO proxies).
In XI message monitor everything seemed to be ok but no message arrived till SAP R/3. Nothing in any queue...
After deactivating and reactivation the RFC receiver comm. channel it worked again BUT ALL PREVIOUSLY SENT messages seem to be lost.
Is it really the way it works? Does XI integration engine at runtime NOT catch whether or not a RFC or FTP receiver adapter died, thus is not able to tell somewhere in message monitor that a message could not be delivered at all?
I'm really confused here but hopefully I simply don't understand some easy principles to take into account...
Our SAP R/3 is on rel. 4.70 with Web AS 6.20. The XI 3.0 plugin is not installed. Do we need to go with server proxies there and use QOS = best effort?!?
Thanks for some suggestions.
Best regards,
Renaud

Hi Michal
Thanks... works great for normal XML based messages!
Now, what if I wanted to pass binary files from one ftp server via BPM to another ftp server in order to enable the transport acknowledgment?
The files polled from ftp server using the ftp sender adapter are all in binary format (ARJ). No xml data in there. How should the message format look like in BPM for the receiving step? Or: how to make sure not to loose the binary content when passing through BPMs?
I need this sort of scenario because of the tansport acknowledgment and because I need to have some sort of message splitting (send the binary file over to a second ftp server and additionally send some kind of info message to SAP R/3 regarding thin binary file).
BTW: in the MessagingSystem/monitor/monitor.jsp I do not see sender / receiver information. Is this normal? It's quite of a bad thing to look inside each message in order to find out what message I'm having in front of me...
Thanks a lot for your support and patience!
Kind regards,
Renaud

Activating Message Overview Message Monitoring

Hello,
We recently moved our XI system (3.0) towards SP21. Now we want to activate new way of message monitoring using the message overview. As stated in http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
note 1031773 describes how to activate the message status overview. However when i search for that note. The note is not (anymore) available.
An SAP note with the number requested could not be found.
Somebody a clue where the note has gone? Or can somebody tell me what are the steps to take to activate message-overview monitoring?
Thanks in advance,
Emile

Hi,
It is better to raise a new OSS. Sometimes, with a new solution or incorrect solution , some of the OSS notes actually gets cleaned up or deleted.
Regards
Krish

Basic Authentication in RWB's Message Monitoring

Hello,
we have XI 3.0 SP11. When I try in the RWB:
Message Monitoring -> IE -> Details -> Message Content
I can't login over the Basic Authentication menu. The user has all XI-roles and the SAP_ALL profile but it doesn't work.
What's wrong?
thanks for help
André

Add role "SAP_J2EE_ADMIN" and try it again.

Details button does not work in RWB Message Monitoring

Hi,
I am getting
'Runtime error - details is null or not an object'
client-side javascript error message, when I select a message and press the 'Details' button in the runtime workbench message monitoring. The message details do not show up. I am using XI 3.0 SP12.
Any idea how we can fix this javascript error?
Thanks in advance,
Suresh.

There is an issue where messages are visible at ABAP Stack(SXMB_MONI).But same messages are not visible at RWB Message monitoring Integration server(IE and AE) Level.
Check if you have chosen the Status filter as ALL and not "Error".
If you are loking for old messages, then you will not be able to see succesful messages beyond a particular period in the past, since all the succesful messages would have been archived.
To see such messages, you have to choose, the option, show message from "Archive" and not "Database".

BPM: PI Message Monitor

Hi guys,
Have anyone configured Delta Message Monitor and Total Message Monitor in BPM?
I have followed document "Interface Monitoring with SAP Solution Manager Release ST 400, STSER
700_2008_2 and STA/PI 01L.
In spite of the fact I do have errors in PI trx. SXMB_MONI, BPM appears as everything ok. All the filters are correct and alert configuration was sucessfully generated.
Any tips?
Thanks,
Renato

Just as feedback: The only way it worked properly was implementing ST-SER 701_2008_2 SAPKITLOQ4.
In other words, we implemented EhP1 in our Solution Manager,
Renato

Exception in Message Monitoring when failed message is cancelled

Similar Messages

Maybe you are looking for