Moni error

Hi Experts,
I am having a problem with the receiver agreement condition. I am getting an error as Problem occurred in receiver agreement .
I am having a IDOC to JMS flow in which an IDoc is triggered to two receiver systems both JMS.
I have used 1 receiver determination having the two systems and two receiver agreement for the two comm channels.
Still the error is coming.Please reply.
Regards,
Aniruddha

Hi Aniruddha,
No, this is nowehre related to the JMS receiver channel. First the receiver agreement step is executed in IE and if it passes, then the message is passed on to the JMS receiver channel. So, your message is not even reaching the JMS receiver channel and failing in the receiver agreement step.
As per the Error thrown, Please check whether your receiver agreement has different values than the following:
Sender Party:
Sender Component: SAP_ECC_FPI
Sender Interface: DESADV.DELVRY07.ZMMDELVRY07_02
Namespace: urn:sap-com:document:sap:idoc:messages
Receiver Party:
Receiver Component: MAINFRAME_FPI
Match these values with the receiver agreement from your ID. IF everything is fine, then there must be some cache issue. Re-activate your agreement after some dummy changes and then everything should work fine.
Regards, Gaurav.

Similar Messages

SQL--XI--RFC Scenario    MONI Error MAPPING" EXCEPTION_DURING_EXECUTE

Dear All
I am doing Scenario SQLXIRFC Scenario .
I am able to pick the data from sender JDBC Communication Channel .
But at SXMB_MONI , i am getting this error   MAPPING">EXCEPTION_DURING_EXECUTE
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_EMPLOYEE_MST_Message_Mapping_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
Source Data Type is    EMPLOYEE_MST_Data_Type
                                            I-row
                                                  I-Field1
                                                  I-Field2
                                                  I-Field3
                                                  I-Field4
RFC structure is      /BIC/CQEMPLOYE00001000
                                         I-Data
                                              I-Item
I-Field1
I-Field2
I-Field3
I-Field4
                                                    I-FieldFlag
Please help , need your all kind help for the same
Regards
Priya
Edited by: Priya Gupta on Sep 1, 2009 2:20 PM

Hi Priya,
Take the input payload from Moni and test your message mapping (using test tab). Keep the Trace to All and see which target element is not getting created.
Is your mapping like this?
Source Data Type is EMPLOYEE_MST_Data_Type
I-row --->I-Item
I-Field1 --> I-Field1
I-Field2 --> I-Field2
I-Field3 --> I-Field3
I-Field4 --> I-Field1
Regards
Suraj
Edited by: S.R.Suraj on Sep 1, 2009 8:24 AM

MONI ERROR MESSAGE

Hi Guys,
Message stucked in PI queues. in queue it was status as RETRY, i selected that message and executed LUW..its shows as successful in MONI..but i am getting below DUPLICATE_DETECTED message..is there any problem with target system or any chance of creating multiple files in target system? this is BW to FILE interface...pls explain me..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 80144fe7-7074-1ed0-a2b7-352a8ec2d99d(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00169819) violated</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Thanks,
Siva..

Not sure how much will this help for your problem but pls check
SAP Notes Note 962578 -Wrong persist exception - duplicate detected
Also
Check SM59 . JCo*
try to restart the J2EE
see the below links
JCO_System_Failure
System Error During Message Mapping
Jco System Failure
JCO_SYSTEM_FAILURE
getting error "JCO_COMMUNICATION_FAILURE"
Mapping probem after CMS export
Regards
Pothana

Duplicate message and Duplicate key error in Moni and RWB

Hi,
I am getting very frequent issues of Duplicate messages in production system moni and RWB.
Moni error: (IDOC to JMS) Errors are coming in call adapter step:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not insert message 005056aa-730e-1ed4-a6c9-a01ee2b86cb3(INBOUND) into duplicate check table. Reason: com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error OpenSQLExceptionCategories: [RECOVERABLE]
RWB error: (File toIdoc) Errors are coming in sender channel.
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id a6d559cf-b00c-11e4-b786-00000daf354a(OUTBOUND) already exists in duplicate check table: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: Violation of PRIMARY KEY constraint 'PK__BC_MSG_D__99C1915D3DE9247A'. Cannot insert duplicate key in object 'SAPPGXDB.BC_MSG_DUP_CHECK'. The duplicate key value is (a6d559cf-b00c-11e4-b786-00000daf354a, OUTBOUND). OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION
Moni errors are manually reprocessed and RWB are automatic.
Can you please let me know if there is any solution available for these issues?
Thanks
Navneet.

I'm getting the same issue at my current client:-
Putting message into send queue failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id e1d4a31b-f0cc-11e4-c7fb-0000029706f7(OUTBOUND) already exists in duplicate check table: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00188646) violated OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
I've tried restarting the SOAP channel but this has not resolved the problem.
Just read on another thread that this may be a misleading error message (see last post on the link). It may be an idea to increase the trace level temporarily and look for any other issues that may be the cause.
So far I've not seen any post that describes the error on the SOAP channel - only seeing it for JDBC & File. However it seems to be a common problem across a number of sender channels.

Abap mapping - Error in Control Framework

Hi Gurus,
Scenario: IDOC - -- XI -
Http (post)
i am using ABAP mapping for IDOC to XML. I am able to test it using sxi_mapping_test which gives me output XML. But, when i test the scenario from RWB, it fails with "SYSFAIL" error in inbound queue as per moni.
error - "Error in Control Framework".
Looks like it did not even go to message mapping pipeline step.
Please help.
Thank you,
mk

HI,
Hope you have done all the necessary pre-requisites for ABAP mapping
This may help u- http://help.sap.com/saphelp_47x200/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm
just cross verify with this guide-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
Please also try to debug as follows...
put a break point inside your class/method....
goto tcode SXI_MAPPING_TEST....give in the configuation details of your scenario...and when you execute, give the IDOC-XML, copy it from SXMB_MONI where you are getting the error....
when you execute, it shoudl stop at the break point that you had set in your class....continue debugging using 'F6' function key, and check where you are hitting this error...
The chances are that the FM that converts IDOC-XML to flat file format might not have been executed correctly...
Thanks
Swarup

Error in File to Idoc

Hey guys i m doin a asynchronous file to IDoc scenario and getting the followin error in MONI
Error:IDoc XML data record:In segment attribute occured instead of SEGMENT.
i copied the payload from MONI and its workin fine in message mapping.
is there a way i can monitor IDOC adapter(i cant do it in RWB).
any idea where the error might be?
thanx
ahmad

Hey the payload i m getting is as follows
<?xml version="1.0" encoding="UTF-8" ?>
- <ns:MT_Idoc_sender xmlns:ns="http://Thoughtbyte.com">
- <Record>
- <Row>
<Name>Mark</Name>
<Address />
</Row>
</Record>
</ns:MT_Idoc_sender>
and the error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>IDoc XML data record: In segment attribute occurred instead of SEGMENT</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: IDoc XML data record: In segment attribute occurred instead of SEGMENT</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
thanx
ahmad

Receiver soap : Error ADAPTER.SOAP_EXCEPTION

Hi all,
My Scenario is IDOC -> XI -> WEBSERVICE using BPM & SOAP adaptor.
when i send idoc from R/3 it is going Xi
From Xi to web service using WSDL Request message .it is not reach to web service(connection is ok but wsdl request massage is not going properly) .
sxmb-moni :error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: com.sap.webservice.SchemeTopupDeliveryService</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
<SAP:AdditionalText>soap fault: com.sap.webservice.SchemeTopupDeliveryService</SAP:AdditionalText> : this service is not related to my service (It is showing wrong service name)
Pleas tell me where error is happened

this service is not related to my service (It is showing wrong service name)
This is the reason, you somehow call the wrong web service. But are you talking about BI or XI here?
Best regards
Dirk

Error Category: BPE ADAPTER???

i have a simple file to file scenario...with a BPM in which i have a send, a receive and one transformation...
on running the scenario..i get the error in the MONI
Error Category: BPE ADAPTER
Error ID: UNKNOWN MESSAGE...
whats the reason???????

Hi,
Tcode : SXI_CACHE
Select your integration process which you created in IR and activate.
again you will get the return code is 2 and again activate your integration process until you will get the return code is '0'.
Prerequisite for BPM : check tcode : SWF_XI_CUSTOMIZING
all are in green hook , if not get all are green hook
Regards
Chilla

Error while refreshing cache

Hi ,
My scnearo was working fine . Suddenly i am getting this error in moni
error while refreshing cache
if any one ever faced this problem plz let me now
thanks
amit

Hi Amit,
1. Check the RFC destination INTEGRATION_DIRECTORY_HMI in transaction sm59. Check the connection and the username & pwd.
2. Check the HTTP services default_host/sap/xi/cache and default_host/sap/xi/cache_ssl. They should be active.
There are other troubleshooting steps outlined in the document 'How To Handle Caches in SAP XI 3.0'. I suggest you go through them.
https://websmp104.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
Cheers
Manish

Monit configuration on archlinux (mysql)

This config lines should work ok on an archlinux system?
check process mysql with pidfile /var/run/mysqld/mysqld.pid
group database
start program = "/etc/rc.d/mysqld start"
stop program = "/etc/rc.d/mysqld stop"
if failed host 127.0.0.1 port 3306 protocol mysql then restart
if 5 restarts within 5 cycles then timeout
depends on mysql_bin
depends on mysql_rc
Those "depends" lines are needed?
edit: at least the last one looks like not "Mar 20 23:01:20 localhost monit: monit: Error: Depend service 'mysql_rc' is not defined in the control file"... lol
any idea?
edit2: and the previous neither, lol "Mar 20 23:04:56 localhost monit: monit: Error: Depend service 'mysql_bin' is not defined in the control file"
edit3: without those depends it runs... then I tried killing mysqld... but it tried to restart it 5 times without luck (I have received the email alert "Description: service restarted 5 times within 5 cycles(s) - unmonitor")
Last edited by luuuciano (2013-03-21 03:23:05)

Just read something about monit and arch and you'll be good
First, "depends" defines... well, dependencies between monit services. So in order to run mysql as shown, you have to provide these services (probably of "check file" type) or just assume they're always OK and remove dependecy check.
Then, start|stop program in your case use sysvinit style scripts, while you probably have systemd (unless you managed to avoid this monstrosity). So, replace "/etc/rc.d/mysql..." with corresponding systemctl invocation.
I don't know if mysql under systemd creates pidfile; if not, use "matching ..." or even "check host" -- as systemd takes care of process supervision, just checking connectivity will be enough.

Problem in Idoc Receiver

Hi guys.
I have a FILE to IDOC scenario.
The original idoc have only 1 ocurrence but I've changed the ocurrence with an external definition based on idoc xsd with ocurrence 0..N.
When any idoc is generated in mapping Im getting the next erro in moni:
Error: MSGGUID 901EF81123CC4D131091DF1F61EB83B4: Tag found instead of tag IDOC BEGIN=
Why Im getting this error in sxi_monitor if I've especified my cardinality to 0..N??
Thanks a lot.
Regards.

>> Error: MSGGUID 901EF81123CC4D131091DF1F61EB83B4: Tag found instead of tag IDOC BEGIN=
First export the idoc locally and change the occurence of idoc tag from 1 to 0 to unbounded. Check in the mapping you specify the modified idoc. Also acivate the objects and update cache.
Tips
a) Use your modified idoc in the message mapping target side
b) Operation mapping - Specify original idoc as target message in the inbound side. (you might get some warning during activation.. please ignore it)
c) In the interface determination check you specify operation mapping and inbound interface as original idoc....
If you do all the above steps, You should not get this error. Hope this helps.
Edited by: Baskar Gopal on Feb 24, 2011 9:30 AM

Proxy to File--- NO_RECEIVER_CASE_ASYNC

I have a proxy to xml file scenario getting data from ECC. I am getting the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have noticed one thing in my error in SXMB_MONI. The sender Service appears to be incorrect from what my SLD and configuration is set to. We actually create an entry in the SLD that we actually deleted and re-created. The old entry (deleted one) is still showing up in the moni-error. We have cleared all the cache. We have deleted everything in ID and IR and rebuilt everything twice. Test configuration is also working fine. Any help would be greatly appreciated.

Hi Tanuja,
Make sure if it is deleted from deleted from ID, not just from the configuration scenario(check in objects tab also).
If it is also deleted there just refresh the cache in SXI_CACHE and also CPACACHE.
Also check if the cache is clear in R/3 side also.
Regards,
Naveen.

Functiontemplate from repository was null

I have a sceanrio file rfc file,All my design config seems to be good i have double checked the rfc adapter configuation.I have an error in moni
Error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>******
Can any please tell me what would be the problem..
Thanks
sriram

Hi Sriram,
Is RFC adapter is active/up and running? RFC xml structure is incorrect?
Refer SAP Note - 730870 Question no 16.
Regards,
Moorthy

Seeburger X.400 messages stuck in SXMB_MONI

Dear experts,
I am getting order messages from a partner who sends those via X.400.
So I do have a Seeburger X.400 sender adapter:
Payload Mode: "Attachment"
Attachment alias: "attachment"
Encoding: "binary"
MODULE: only "localejbs/CallSapAdapter"
But the messages are always stuck in SXMB_MONI!
I get the MONI error:
Runtime exception occurred during application mapping com/sap/xi/tf/_X_ORDERS_TO_I_ORDERS02_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Parsing an empty source. Root element expected!
But when I look at the payload the XML file is displayed correctly, it is encoded in ISO-8859-1.
Where I double click the payload entry in MONI it says "attachment#0001 ( application/octet-stream )" though. Normally it should say
"attachment#0001 (application/xml)"!
I have already taken the XML message and tested it in message mapping and operation mapping and both work fine!
Does anyone have an idea? Why would PI not find the root element?
Thank you very much for any hints and best regards,
Peter

Hello Ramesh, Hello experts,
I now got an answer from the sender.
They set "application/octet-stream" for each message they send because they mostly do not know what file type the messages are.
I assume if this was "application/xml" I would not have a problem. The sender says he can not change this though. They do get a new X.400 system middle of 2010 and might be able to do more settings then but I do not want to wait so long.
> Is there anything I can do to change the file type "application/octet-stream"?? <----
Thank you again or anyone that has an idea!
Best regards,
Peter
Edited by: Peter Wallner on Mar 31, 2010 3:25 PM

Proxy :No implementing class registered for the interface

<b>Hi
I am executing an Out bound proxy from client 101.
when i execute the proxy, i could see the following error in moni.
error info----
No implementing class registered for the interface (type ifmmessif, name PORequest_Out, namespace http://sap.com/xi/3A4/Purchasing/proxytoRfc)
end of error info----
Any tips fro the experts??
Regards</b>chandra<b></b>

Hi Chandra,
You need to activate both the classes and the interfaces.
Try to regenerate and activate once again.
http://help.sap.com/saphelp_nw2004s/helpdata/en/86/58cd3b11571962e10000000a11402f/frameset.htm
Also refer the blog mentioned by earlier post.
Hope this helps,
regards,
Moorthy

Moni error

Similar Messages

Maybe you are looking for