Outgoing messages failing in adapter engine

Hi,
I would like to know the cause of the following error which I frequently encounter in my Seeburger AS2 adapter engine for outgoing messages
MIC not verified # MIC values not verified: QRP65LlObLvoGwZmMdIFpuXsvzA=-yqCovOQUkVWawfNVfSrXXaRRt8c=
It appears only in the adapter engine and doesnt reflect as an error in RWB.
We have already checked the certificate being used and found it to be valid.
Would like to know the root cause of this.
Thanks in advance

MIC is the message digest sent by the receiver AS2 system as a part of MDN to acknowledge the status of sent message. This is used by sender for non-repudiation of sent message. This message indicates some problem in the message sent. The point of this verification is the at sender system. This is not exactly XI related problem.
Found a similar problem in Seeburger guides but this is related to authentication failure
Outbound: MIC not verified # authentication-failed, processing continued
Cause:
An incorrect signing certificate is being was used, but the trading partner continued with the
processing, because it doesnu2019t matter, if the message is authenticated, or not.
Solution:
Check the signing certificate configuration.
Regards,
Prateek

Similar Messages

Auto restart of messages failed in Adapter Engine PI 7.0 and 7.1

Hi,
I am trying to figure out a way to automatically restart the messages failed with in the adapter engine (because of the target system not available etc.). These messages are in System Error status and I can restart them from RWB. But I am looking for any report or something available either on Java or ABAP engines so that I can automate the process.
Thanks for the help.
VJ

I have come across the web service AdapterMessageMonitoring in PI 7.0 (Found it in Web service navigator) with possibly useful methods. But I could not find the same service on PI 7.1. Any clue on this?
Also, the getMessageList methods works perfectly as expected but the resendMessages mehtod fails with the exception -
com.sap.engine.services.ejb.exceptions.BaseEJBException xmlns:ns1="http://sap-j2ee-engine/client-runtime-error">Exception in method resendMessages.</ns1:com.sap.engine.services.ejb.exceptions.BaseEJBException>
Will post more if move forward.
VJ

Message failed on adapter engine

I have cofigured the IDOC-XI-JDBC scinario. Everything works except the adapter's status is 'holding' for a long time when trying to send to JDBC. Wish to help me.
[email protected]
Thanks and Regards
Amanda

Hi Amanda,
       JDBC adapter tends to hit the database every x secs(polling interval) .So either increase the polling interval or change Quality of Service to (QOS) to Exactly Once (EO).
       if your values are getting updated in the database on the receiver side and yet your adapter status is 'holding' for a long time , above mentioned should be the problem.
       If your values are not getting updated in the receiver database and u r landing up with the message, then the problem should be in JDBC driver , username and password informations that you gave in the JDBC adapter configuration.
       Try entering into the receiver database manually with the exactly log on parameters u gave while configuring JDBC receiver adapter .If you are not able to log in , then this is the problem. If u r able to log in then have a sharp look at the driver type you specified.
       Hop this helps you in locating the root cause.
regards,
Aravindh.

Message split on adapter engine for the java based IDoc adapter

Hi Guys,
Do you know if message split on adapter engine is available for the java based IDoc adapter on the single stack (PI 7.31)?
I'm getting such exception when I try to post 3 IDocs
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: Invalid XML 1.0 character encountered within IDocXML for type <ns0:Messages>:
state=EXPECTING_IMMEDIATE_TAG_END, charPosition=68, lineNumber=1, columnNumber=69, invalidChar=U+0078,
sourceSnippet=...UTF-8" standalone="no"?><ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1><...
^
Mapping is one to many.
Each IDoc content has been compared manually against the xsd schema and it was fine.
I know that old way of modifying xsd is still possible.
Best regards,
Wojciech

Did you find a solution to this? Having a similar error right now.
Thanks and kind regards
Jens

Message struck in adapter engine with status Hold

Hi,
In intergaration engine all messages are processed, I have checked SMQ1, SMQ2 (no message is struck in queue)
where as messages struck in adapter engine with status Hold, I have checked this in RWB. How to resolve this?
Regards,
Krishna

Hello,
Below is some information on how to resolve this type of issue:
1 - In the RWB, expand the tray for "Configure Table Columns" - by clicking on a square at the right end of this heading.
2 - Check the checkboxes for "Serialization Context" and "Sequence Number". These should then appear in the table columns as well.
3 - Add the Serialization Context to the Extended Filter Criteria. Search the messages in status HOLD based on this new additional criteria.
4 - Sort the messages in ascending order based on the Sequence no.
5 - Check the predecessor message of the first message in status "HOLD"
Based on the following status for this predecessor messages, the actions that can be taken for the HOLD messages are:
a - Predecessor is in Failed State/System Error : Cancel/Resend the
first message in status HOLD after this. Then the remaining messages
can be cancelled/resent.
b - Predecessor is in DLVD state(delivered state) : First Holding
message can be resent/cancelled followed by the others.
c - Predecessor is in NDLV(Non-Delivered Status) : Check why the
predecessor message failed and correct the reason for the failure.
Then resend the predecessor message and then cancel/resend the
remaining HOLD messages. Alternatively, you can directly try
resending this NDLV predecessor message and see if it goes. If it
goes, then the remaining HOLD messages can be resent/cancelled.
Another option could be to cancel this NDLV predecessor message so
that it goes to FAILED state and then cancel/resend remaining HOLD
messages.
Regards,
Sarah

XI message status at Adapter engine level using a table (SAP table)

Hello Experts,
XI message status at Adapter engine level using a table (SAP table).
We want to write a custom report using ABAP so Pls tell why the status u2018Holdingu2019 and u2018To be deliveredu2019 are present in message monitoring of RWB but not in the status (MSGSTATE) field of SXMSPMAST table.
My need is to write a report to get the messages based on the these status from table level.
Please let me know the table name and field name for this and the table name for the desciption of the status of XI messages at Adapter level.
Thanks
Gopesh

Hi Gopesh,
the Adapter Engine Messaging System messages are on the Java schema,
i.e., see the following -
[XI/PI tables|https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/xi+tables]
Regards
Kenny

XI Adapter ? No messages in the adapter engine in RWB

Hi Guys,
I have the scenario SOAP-PROXY. I have configured XI Adapter on the receiver side. I have used xml spy to post the messages directly to the IS. I could not see any messages in the adapter engine in RWB.
I have seen the messages processed successfully in the integration engine under RWB.
can anybody explain why i could not see any messages in the adapter engine ? Is It normal with the xi adapter on the receiver side ?
Thanks,
Raj
Message was edited by:
raj reddy

Raghu.
I've done the following:
1. I've executed SE38 tx code.
2. I've entered the "RSXMB_DELETE_MESSAGES" report as "Program"
3. As the "RSXMB_DELETE_MESSAGES" report does not have a selection screen, it must be executed with default parameters. So, I selected "Program -> Execute -> Background".
4. There are no available variants, so I clicked on the "Execute immed." button.
5. The job starts. I can monitor it on the SM37 tx code.
6. It only deleted 20 messages.
What I get from this, is that the "RSXMB_DELETE_MESSAGES" report cannot delete the big part of the messages since them are marked as "Archivable" and not as "Archived".
what do you think of it??
regards
Carlos.

How to get Payload of SOAP Message in Advance Adapter Engine

HI All,
I am wondering if anybody can tell me how to view the Payload of SOAP Sender and Receiver Message in Advance Adapter Engine?
Does Anybody know how to check mapping payload in Advance Adapter Engine because in ABAP you can see the mapping payload under Request Message Mapping but when you use AAE you can't see the Request Message Mapping Payload.
I have a SOAP to RFC Scenario in which I can't see the SOAP Sender and RFC Receiver Mapping Payload.
When I am sending incorrect data to an RFC I am getting this error which is very strange and new to me.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Unable to split a synchronous message
Any comments would be much appreciated.
Thanks,
Iqbal

HI All,
I have managed to find Michal's Blog which is talking about getting the mapping payload but unfortunately I don't know how to create Adapter Module so I am wondering if somebody can please provide me EAR file so that I will request the Basis guys to deploy the code and hopefully this will solve my query.
Michal's Blog
As you all probably know while using local Advanced Adapter Engine (AAE) processing in SAP PI 7.1 the message is logged only once (during processing by sender adapter). This is great in terms of performance but what if we need to check the mapping output? Is there a way do do it somehow? It turns out that we don't have such an option in standard yet. Is there any alternative then?
It turns out there is - a simplest adapter module there is...
Local AAE works in such a way that from the sender adapter it executes the receiver adapter so in the outbound message to PI processing you can see the adapter info logs of the receiver adapter and this is what we can use. The idea is to add an adapter module to the receiver adapter which will put the content of the message into the audit log of PI message processing. We can do it by writing a few lines of code:
PI/XI: target message logging with local AAE not possible ? not anymore...
*Please upload the file in any free site or <REMOVED BY MODERATOR>
<READ RULES OF ENGAGEMENT>
Thanks,
Edited by: Prateek Raj Srivastava on Jan 6, 2012 9:10 PM

Messages are failed in Adapter Engine

Hi Experts,
give me solution as early as possible pls
There is a problem with production system in XI.
I am getting the error in Adapter Engine level in Runtime workbench.
"Attempt to process file failed with
com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution:
com.sap.aii.adapter.file.varsubst.VariableDataSourceException: Caught SAXException while parsing XML payload:Fatal Error:com.sap.engine.lib.xml.parser.parserException: XMLparser: No data allowed here(:main:,row:,col:75)"
The scenario is IDOC to JMS & File.
There are 2 conditions
if the data is coming from ECC is valid then Msg will go to the JMS
other wise it will be dropped into File System.There is no problem with valid data.
when ever invalid data will come 70% Messages are processed succefully and few Messages not processed.
if i resend this error message 2 or 3 times it is processed succefully, iam getting huge number of messages like this,
it is difficult to resend because if i select all Msg's it is not processed only one Msg will be processing when iam trying to re-send
please can any body give me the permanent solution for it.
Thanks & Regards
Sankar

Well,
Take account the following considerations.
1. Check your source code for the variable substitution(Maybe you can show us).
2. check in the tab "Advanced" on you file adapter configuration, there are many checkBox, for example is you are replcainf the file name in you mapping The "File Name" check(in Adapter specific attributes) has to be checked, and if you are using other variables you need to do the same.
I hope It helps you.
Ivan

Resend Message that fails in adapter engine but shows success in sxmb_moni

Hello SDN!!
We are testing sending soap requests out via SSL. We are using a BEA as a pass through server for SSL encryption only.
The scenerio is to send a message from SAP to PI 7.1 to BEA (SSL enc) to Receiving System. We successfully connect to BEA (only used as a pass-through) but the connection to Receiving System does not work. This returns an error to our adapter engine.
My question is this, Since SXMB_MONI shows the message as successful, but the adapter engine is showing an error. What is the best way for
1. Monitor the errors, (I only see where you can monitor the type of adapter only)
2. Resend the message, since it shows valid in SXMB_MONI, it won't let me resend.
Any help will be greatly appreciated and awarded
Cheers
Devlin

1. Once the message is in successful status in moni, the best way to monitor becomes RWB -> Message Monitoring.
2. For adapter engine related errors, you may resend the data manually using the resend option in the Message Monitoring. Otherwise, for automatic retry of messages, you may change the default settings.
Regards,
Prateek

How to delete / cancel messages in PI adapter engine

Hello expert,
we have a scenario File (EOIO) --> PI --> ABAP. Today the file we received is big (>100mb), apparently PI can't handle it, and we got error
Transmitting the message to endpoint http://host:port/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.
seems like PI adapter engine got problem while delivering the huge message to ABAP integration engine. In RWB message monitoring, the message is set to Error. Unfortunately the file has been picked up many times, thus the huge message is stuck in adpater engine. In RWB message monitoring, I can see the message listed many times and status is HOLDING because the previous message can not be delivered to Intergration engine. I want to delete/cancel all the messages, I tried in RWB message monitoring to cancell the messages, however after cancelling one message, it crashed the PI system and cause a reboot.
My question is; Is there some place in NWA (net weaver admin) to force all the messages to be deleted? (Because deleting/cancel in RWB message monitoring does not work because it causes system crash).
Thanks
Jayson

Hi Team,
I couldn't able to delete old message's from one of Q system, Persistence layer is 584 % filled, after triggering delete job(RSXMB_DELETE_MESSAGES) and Persistence layer has come to 384% and further I couldn't able to delete old messages.I executed program "
                                                                                                      RSXMB_CHECK_MSG_QUEUE" and manage to delete few entries.Could you please suggest how to reduce fill level to below 100%
Switch Procedure (for Persistence Tables) Deactivated
Number of Table Entries
3.185.992
Maximum Number of Table Entries
830.000
Current Fill Level in %
384
Threshold value for fill level for executing a switch run in %
60
Number of Logically Deleted Table Entries
0
Decline of Fill Level in % Following Deletion
384
Delete or archive processed XML messages
Job log overview for job:    SAP_BC_XMB_DELETE_001 / 06302000
Date       Time     Message text                                                                               Message class Message no. Message
13.03.2013 06:39:55 Job started                                                                                     00           516          S
13.03.2013 06:39:55 Step 001 started (program RSXMB_DELETE_MESSAGES, variant &0000000000034, user ID SAPBATCH)      00           550          S
13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ASYNC: 1                                        XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ROWS: 100                                       XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-IDX5_DELAYED: 0                                 XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-ROWS_PER_LOOP-DELETE: 100                                       XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-ASYNC: 007                                     XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-SYNC: 007                                      XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR-SYNC: 007                                XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-IDX5: 007                                      XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-ASYNC: D                                  XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-SYNC: D                                   XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR_UNIT-SYNC: D                             XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-IDX5: D                                   XMS_ADM        375          S
13.03.2013 07:27:58 0 XML messages deleted                                                                        XMS_ADM        351          I
13.03.2013 07:27:59 Step 002 started (program RSXMB_TABLE_SWITCH, variant &0000000000034, user ID SAPBATCH)         00           550          S
13.03.2013 07:28:00 Job finished                                                                                    00           517          S

Cancelling/Deleting messages in the adapter engine

Hi Everyone:
How can I cancel or delete a message in status 'system error' in my adapter engine.
I do not want this message will be resent by mistake when the receiver comm chanel will be active.
Thanks a lot guys.

Alvaro,
If the message is successfully processed then you cannot delete. If your message is in waiting or etc. then go through this weblog for much information:
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Hope this helps you...
---Satish

PI 7.0: Message prioritisation in adapter engine for SOAP adapter.

Hi All,
We have both high and low priority synchronous messages using the SOAP sender Channel of the Central AE.
How can we make sure that High Prio messages ALWAYS get a thread right away when entering the AE? Installing a separate AE is not an option.
When I look in RWB->Component Monitoring->Adapter Engine->Engine Status in the Queues tab, I see this:
SOAP_http://sap.com/xi/XI/SystemCall Yes 5(5) 5
SOAP_http://sap.com/xi/XI/SystemRqst Yes 5(5) 5
When a new High Prio message enters, it can take more than one hour before it gets processed, because there are 1000 Low Prio messages also using the same 5 available Threads...
This delay is of course unacceptable for High Prio messages.
I checked in many other threads in SDN, looks like we cannot priortise for particular messages in PI 7.0, as we can do only at adapter level, not at interface level.
I was thinking of going to the approach which was suggested by "Gr, Wout" in the below thread.
xi prioritization in adapter engine (ae, af, adapter framework, java, jca)
Creating own adapter "MYSOAP" by copying the metadata of SOAP adapter. By that we can use our own adapter "MYSOAP" for high priority interfaces.
what you think guys about this approach?
Is there any thing I need to take care going through this approach apart from copying SOAP metadata into my own adapter.?
Thanks
Deepthi

increased thread count for soap adapter

Delay of Message in the Adapter Engine when put into queue

Hi XI/PI Experts,
We are having problems in the Adapter Engine wherein messages are staying longer in the AE queue as usual. Sometimes, it stays longer in Delivering status also. Is there any way we can monitor and try to push the message out of AE to avoid delays? I know we can do this in the ABAP side (Integration Engine)...but how can we do this in the Adapter Engine?
See below sample logs in AE RWB:
2008-07-17 13:28:13 Success Using connection SOAP*****. Trying to put the message into the receive queue.
2008-07-17 13:28:13 Success Message successfully put into the queue.
2008-07-17 13:34:12 Success The message was successfully retrieved from the receive queue.
2008-07-17 13:34:12 Success The message status set to DLNG.
As you can see there is a gap of 4 minutes.
Hope you can help me. Thank you so much in advance.
Grace

Hi.
Thanks for your answers but the messages are not set into EOIO but just EO. So the messages are not ending up in Holding Status.
I also believe that issue is not occurring because of too many messages in error in AE nor because of the receiving system is down. Issue is happening when message is about to be sent to the SOAP communication channel in AE. As you can see in the sample log I provided above, in RWB AE, after the message was put into queue, it took several minutes to be delivered to corresponding comm channel. My questions are:
1. Is there a way we can monitor the queue in AE like the way we monitor the queue in IE? (e.g. smq1 and smq2 transactions) .
2. If there is a way, how are we going to intervene manually on the queues in AE? (we can intervene with smq1 and smq2 in IE)
3. For messages with Delivering Status in AE, sometimes it is taking hours to move to "Successful/Delivered" Status. Is there a way we can intervene with that? I believe we can resend messages with "System Error" Status and Staus "To be Delivered" but for status "Delivering"...it is not possible (from what I know -- I hope there is a way).
I look forward to hearing from you guys/gals.
Grace

Messages Stuck in adapter engine but passing through Integration engine

Hi All,
SOAPFault Error. Error Code/Category: XI Protocol/ Wrong Value...Received HTTP Response Code 500: Error during Parsing of SOAP Header
Above error as system error appears in adapter engine when messages are coming into SAP PI. At sender, we are having sender mail adapter.
Adapter Modules are also configured in mail adapter.What could be the possible reason.
Please suggest
Regards,
Kanisha

Below is the error log. As per scenario, Mail To File.
Please Suggest
Regards,
Kanisha

Outgoing messages failing in adapter engine

Similar Messages

Maybe you are looking for