Error in SXMB_MONI in SOAP Header -- Call Adapter

Hi ALL,
Got a problem with monitoring activity.
In SXMB_MONI, iam getting errors with Call Adapter section in SOAP HEADER section of the message.
The Error part shows 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="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: Problem inserting 4657f861-f853-60e8-e100-00000a80314d(INBOUND) into the database: java.sql.SQLException: ORA-25153: Temporary Tablespace is Empty</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anybody give me a clear picture of the exact error and what could be the diagnosis for this particular problem.
cheers,
Santosh

Hi Santhosh
1.Check your authorization settings in XI and R/3. Whether the user has sufficient rights to execute the Function Module etc. This is the most common reason for this error.
2.If the XI system was brought online even before the R/3 system then re-activate the communication channels from the Integration directory.
Cheers..
Vasu
<u><i><b>** Reward Points if found useful **</b></i></u>

Similar Messages

Mail-Adapter Integration Engine Error during parsing of SOAP header

Hello,
we use XI with the mail adapter. Most of the messages are processed correctly. But sometimes I get following errors in the J2EE-logviewer:
Transmitting the message to endpoint http://<xi-host>:<http-port>/sap/xi/engine
?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.a
pi.RecoverableException: Received HTTP response code 500 : Error during
parsing of SOAP header.
Failed to transmit message 4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND)
due to com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP
response code 500 : Error during parsing of SOAP header.
Retries exceded, set message
4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND) to status NON_DELIVERED.
Has somebody else the same problem and solved it or any idea what the matter could be?
Thanks for your help
Christian

Hi Reddy,
We´ve got the following scenario:
Exchange-Server (is always up)
XI Mail-ReceiverAdapter
I use IMAP4 to access the Outlook-Email-Box
Everything works fine. But some Emails aren´t processed.
I think it´s a problem between adapterframework and the integration engine?
There is no difference between the emails?
If you´ll need further informations ask me?
Thanks

HTTP response code 500 : Error during parsing of SOAP header

Hi Experts,
I have a MAIL to IDOC scenario. An external third party emails invoices to our inbox - which we pick up and process the attachment. All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
When I look at the SOAP header of the failed message I see the values from the dump in this field:
<sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
Can anyone tell me what SHeaderTHREAD-INDEX does? Or what my problem is (Our email is Outlook)
ERROR MESSAGE.........
SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage: ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

We work with Microsoft Outlook, but I'm sure this could work with any email system.
This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company. This is set up as a regular email account. On this email put a forward rule to email2 for a particular sender/subject. email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
Doing this accomplishes a couple of things:
1) We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
Hope this helps your situation.

Error during parsing of SOAP header

Hi all,
I have configured the j-meter to send an http request to inegration engine of PI.
The request xml that I am sending is as follows:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
<SOAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30"
versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1">
</SOAP:Main>
</SOAP:Header>
<SOAP:Body>
<ns1:UnitOfMeasure xmlns:ns1="urn:sapappl:mdm:cp:eame:masterdata:uom:620">
<Record>
<FinishedMaterialCode>000000000000000233</FinishedMaterialCode>
<BaseUOM>KG</BaseUOM>
<AlternateUOM>GEB</AlternateUOM>
<UnitsInAlternateUOM>100</UnitsInAlternateUOM>
<UnitsInBaseUOM>2268</UnitsInBaseUOM>
<Active_Deleted></Active_Deleted>
</Record>
</ns1:UnitOfMeasure>
</SOAP:Body>
</SOAP:Envelope>
I am getting the following response from the XI:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during parsing of SOAP header</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><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="PARSER"/><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>System error in parser
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Any idea as to why PI is not able to parse the request header?
Thanks,
Amit

Hi,
Better to take WSDL from PI(ID window) and try.

ABAP runtime error in sxmb_moni when SOAP message has header with some tags

Hi!!!
I have a problem with sxmb_moni transaction.
If I double-click on a successfully processed
message, then this monitor can't show me
the message details but fails with the following error:
<COPY_AND_PASTE_FROM_SCREEN>
Runtime errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exception              CX_SY_REF_IS_INITIAL
Occurred on     02.03.2005 at 16:44:21
Access with 'ZERO' object reference not possible.
What happened?
Error in ABAP application program.
The current ABAP program "CL_XMS_PROP_STRING============CP " had to be
terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
</COPY_AND_PASTE_FROM_SCREEN>
This situation takes place only when I want
to look at a SOAP message which was sent to XI
from .Net platform or was sent to
.Net platform from XI (via SOAP adapter).
In all other cases sxmb_moni works fine.
I know that the problem is connected with some tags from Header record of SOAP message:
      <soap:Header>
         <wsa:Action>http://aaa.bbb.ccc/MessageResponse</wsa:Action>
         <wsa:MessageID>uuid:1838f870-1688-4cfe-8c4f-afe14d98c515</wsa:MessageID>
         <wsa:RelatesTo>uuid:308b950f-8cff-4b63-9861-93b041825f9d</wsa:RelatesTo>
         <wsa:To>http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa:To>
         <wsse:Security>
            <wsu:Timestamp wsu:Id="Timestamp-389847df-8760-4d57-9777-6ce159d85205">
               <wsu:Created>2005-03-02T08:54:29Z</wsu:Created>
               <wsu:Expires>2005-03-02T08:59:29Z</wsu:Expires>
            </wsu:Timestamp>
         </wsse:Security>
      </soap:Header>
If I take a SOAP message I have problem with, and
I remove all tags from this Header (or remove
the whole Header) and send it from any XML editor
that can send SOAP messages then sxmb_moni hasn't
any problems with showing me details of a such message.
Any hints how to force a .Net platform not to send
a such header or how to force sxmb_moni transaction
not to fail if a such header occurs?
Regards,
Andrzej Filusz

Hi Santhosh
1.Check your authorization settings in XI and R/3. Whether the user has sufficient rights to execute the Function Module etc. This is the most common reason for this error.
2.If the XI system was brought online even before the R/3 system then re-activate the communication channels from the Integration directory.
Cheers..
Vasu
<u><i><b>** Reward Points if found useful **</b></i></u>

No Payload in the soap receiver call adapter ?

Hi Guys,
configured Proxy-SOAP Asynchronus process and in the sxmb_moni, i am unable to see the payload under call adapter in sxmb_moni, but i am able to see the payload under RWB in MDT. The message is checked successful in monitor.
I am not understanding why i am unable to see the payload under call adapter in sxmb_moni. I am not getting the data into my receiver system.
Do i need to mention the QOS as EO in the soap url in the soap receiver adapter configuration ?
any help would be really appreciated
Thanks,
srini

Hi,
You can only see the Payload(both with and without transformation) in MONI. message that is handling by adapter can only seen in Adapter Framework using RWB-Message Monitoring or using Communication Channel Monitoring.
Regards,
Farooq.
<b>
Rewards points if you find it usefull.</b>

Error in SXMB_MONI of SOAP to JDBC scenario

<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:352) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy153.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor371.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7650) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2275) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1614) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8009) at com.sap.mw.jco.JCO$Server.work(JCO.java:8129) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8076) at com.sap.mw.jco.JCO$Server.run(JCO.java:7992) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:212) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:347) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy153.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor371.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7650) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2275) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1614) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8009) at com.sap.mw.jco.JCO$Server.work(JCO.java:8129) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8076) at com.sap.mw.jco.JCO$Server.run(JCO.java:7992) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_Jdbc_Response_Soap_Response_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_Jdbc_Response_Soap_Response_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy153.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor371.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7650) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2275) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1614) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8009) at com.sap.mw.jco.JCO$Server.work(JCO.java:8129) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8076) at com.sap.mw.jco.JCO$Server.run(JCO.java:7992) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:352) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy153.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor371.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7650) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2275) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1614) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8009) at com.sap.mw.jco.JCO$Server.work(JCO.java:8129) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8076) at com.sap.mw.jco.JCO$Server.run(JCO.java:7992) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:212) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:347) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy153.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor371.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7650) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2275) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1614) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8009) at com.sap.mw.jco.JCO$Server.work(JCO.java:8129) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8076) at com.sap.mw.jco.JCO$Server.run(JCO.java:7992) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
</Trace>
<Trace level="1" type="T">SystemError message generated. Guid: 77F087459C16DB10E1000000C0A8641B</Trace>
<Trace level="1" type="T">Error during execution of message : 6733E5718FF711DB97EE00132026BD95</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 659AF5F08FF711DB85C800132026BD95</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
This is the error showing in SXMB_MONI, can u please tell where i went wrong...
I did Transforormation correctly data is entered into JDBC but it doesn't picking up the response into SOAP message.
Can u please find out the error..
Regards,
Pushparaju.B

This is my JDBC Request structure...
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Jdbc_request xmlns:ns0="http://soaptojdbcsync.com/demo"><STATEMENTNAME><TEST1 action="INSERT"><TABLE>TEST1</TABLE><access><BPID>1</BPID><REQ_CUST_NUM>234</REQ_CUST_NUM><MATERIAL_NUMBER>1067</MATERIAL_NUMBER><QTY>234</QTY><SUPP_CUST_NUM>456</SUPP_CUST_NUM></access></TEST1></STATEMENTNAME></ns0:MT_Jdbc_request>
This is my JDBC Response Structure....
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Jdbc_request_response xmlns:ns0="http://soaptojdbcsync.com/demo">
   <STATEMENTNAME>
      <TEST1 action="">
         <TABLE/>
         <access>
            <BPID/>
            <REQ_CUST_NUM/>
            <MATERIAL_NUMBER/>
            <QTY/>
            <SUPP_CUST_NUM/>
         </access>
      </TEST1>
   </STATEMENTNAME>
</ns0:MT_Jdbc_request_response>
can u see the structure if i went wrong with it

WebService Error: SoapFaultCode:3 SOAP header To was not understood

Hello All,
I am trying to consume a webservice. I have created a client proxy and a logical port for the webserive.
But when i try to test the service consumer in SE80, i get the following error.
SoapFaultCode:3 SOAP header To was not understood.
Could you please help me out here.
Thanks & regards
Kassin

>
kassindro wrote:
> Hello All,
>
> I am trying to consume a webservice. I have created a client proxy and a logical port for the webserive.
> But when i try to test the service consumer in SE80, i get the following error.
>
> SoapFaultCode:3 SOAP header To was not understood.
>
> Could you please help me out here.
>
> Thanks & regards
> Kassin
Hallo Kassin,
I do not know how you added the webservice hearder.
Please refer the thread here with similar problem [Web Services Security using ABAP Proxies|Web Services Security using ABAP Proxies]
Still not working then post your WDSL ,<SOAP-ENV:Header> tag
Try to use XMLSpy or SOAP UI to test as alternative.

XI to XI Communication : SOAP Header behavior

Hi Techeis,
I have a scenario XI(A) to XI(B) communication..
I use Receiver XI adapter using HTTP Destination to transfer the payload from IE of A to IE of B. However i see strange behaviour as mentioned below;
in A --> in the SOAP header o/b message interface is A_OUT & i/b message interface is A_IN
when the paylaod reaches XI(B)
in B --> in the SOAP header o/b message interface is A_IN & i/b message interface is A_IN
i.e. in the target XI server, in the SOAP header o/b message interface is always same as the i/b message interface in source XI server !!
why is that behavior , does anybody have idea on this?

Hi Stefan,
Thanks for your inputs. If that is the case then please help me get answerd for the following queries:
1) Why we need to make the o/b MI in B same as i/b MI in A while creating Receiver Determination again in B ?
2) why it loses the information of another MI ? why does it not carry the information of both MI to the B-XI system?
3) Does that mean, in SXMB_MONI, the SOAP header that we see is only for the display purpose and does not reflect the actually nformation carried ?
Thanks in advance!

Call Adapter failing in SXI_MONITOR

Hi Everyone,
We have a scenario = SAP HR ---> XI ---> Legacy systems designed.
proxies are used to send message from SAP HR and JDBC adapter is used in recevier side to update sql database.
And working in live but suddenly it failed and got below two errors.
1) <SAP:Category>XIServer</SAP:Category>
<SAP:Code area="<b>INTERNAL</b>"><b>HTTP_RESP_STATUS_CODE_NOT_OK</b></SAP:Code>
<SAP:P1><b>401</b></SAP:P1>
<SAP:P2><b>Unauthorized</b></SAP:P2>
<SAP:Stack><b>HTTP response contains status code 401 with the description Unauthorized Error while sending by HTTP (error code: 401, error text: Unauthorized</b>)</SAP:Stack>
<SAP:Retry><b>M</b></SAP:Retry>
2) <SAP:Category><b>XIServer</b></SAP:Category>
<SAP:Code area=<b>"INTERNAL"</b>><b>CLIENT_RECEIVE_FAILED</b></SAP:Code>
<SAP:P1><b>110</b></SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack><b>Error while receiving by HTTP (error code: 110, error text: )</b></
Its failling in Call Adapter after receiver grouping in SXI_MONITOR.
I have checked HTTP sevrvice in SMICM and its running fine.
I tried my best to search a fault but could'nt. Please suggest what will be possible cause of error !!!
Thanks IN advance
Swapnil
Message was edited by:
Swapnil Bhalerao

Hi Shabarish,
Same issue as Swapnil. We checked SU01. XIAPPLUSER has role "SAP_XI_APPL_SERV_USER" assigned.
As stated, the scenarios were working fine till day before yesterday. So, I suppose, the kernel patches and all are up-to-date. We started receiving these errors since yesterday.
Kindly advice.

Unable to process SOAP Header child element 'wsse:Security' with 'mustUnder

Hello everyone.
In have created project in Jdeveloper. In this one i have one external reference for Siebel Service.
At composite, for external reference service(Siebel Service) i have added a security policy i.e. *"oracle_wss_username_token_client_policy"*.
[Right click on SiebelService->configure WS policies->under security tab i have selected above policy]
So apart from this i have added property for the policy
<property name="oracle.webservices.auth.username" type="xs:string"
many="false" override="may">SADMIN</property>
<property name="oracle.webservices.auth.password" type="xs:string"
many="false" override="may">SADMIN</property>
But its returning following error,
Unable to process SOAP Header child element 'wsse:Security' with 'mustUnderstand="1"'(SBL-EAI-08000)
This really pushed back me in development.
Really i am in need of help. Help me out of this issue.
Thanks in advance,
Shridhar

Unable to process SOAP Header child element 'wsse:Security' with 'mustUnderstand="1"'(SBL-EAI-08000)The problem is at Siebel side. It is not able to understand the security mechanism being used at SOA side. There are two options -
1. Use the custom policy and assertion at SOA side (please refer to metalink note - 1419373.1)
2. Write your own custom message handler class and use it at Siebel side to negotiate security gap
Regards,
Anuj

500 Connection timed out when in SXMB_MONI in "Call Adapter"

Hi,
We are using SOAP as a receiver adpter. It is working fine all the time but some times we are getting "500 Connection timed out" error in SXMB_MONI in the "Call Adapter" then it retries again and it works fine but I want to know why we are getting this 500 connection time out error and in another try it works.. and what we need to do to correct it.
Here is the error message from SXMB_MONI. Any help is appreciated!
<SAP:AdditionalText><html><head><title>Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY><table width=800> <tr><td width=50 nowrap> </td><td> <H2>500 Connection timed out</H2><br><hr> <table border="0"> <tr><td>Error:</td><td>-5</td></tr> <tr><td>Version:</td><td>7000</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Thu Oct 4 03:26:15 2007 </td></tr> <tr><td>Module:</td><td>icxxthr_mt.c</td></tr> <tr><td>Line:</td><td>2698</td></tr>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description Timeout Error while sending by HTTP (error code: 500, error text: Timeout)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Thanks!
MP

can you please look in to this blog by Michal.
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts

Error in using XI-SOAP adapter, but no error with SAP-BC

Hi,
I am working on RFC->XI->Webmethod (.asp) scenatio.
I am using SOAP adapter.
Whin I am not using "Do not use SOAP Envelop".
I am getting "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML" Error in SXMB_MONI.
But when I am using "Do not use SOAP Envelop" then I am not getting any error. in SXMB_MONI status showing Successfully Processed. But the responce i am getting is "You are not authorized to view this page // HTTP 401.1 - Unauthorized: Logon Failed"
But same web-service is working fine while connected with SAP-BC.
Please Help why scenario is working with BC, but not with XI.
Thanks & Regards

Hi Bhavesh,
Thanks for reply.
I am getting all success in message monitoring, but still web-services sying they are not getting any message.
I am attaching all 4 logs for one synchronous communication of message monitoring.
I am not able to understand where message going and why XI showing success every where.
********1st(Sent Messages)
Success SOAP: response message leaving the adapter
Success Application attempting to send an XI message asynchronously using connection AFW.
Success Trying to put the message into the send queue.
Success The response message for message cf4fd921-4a74-11db-9312-001279933263(INBOUND) was successfully transmitted to the calling application.
Success The message status set to DLVD.
Success The application sent the message asynchronously using connection AFW. Returning to application.
********2nd (Sent Messages)
Success RFC adapter received sRFC for Z_PA_SAP_TO_Webservice from D02/230. Attempting to send message synchronously
Success Application attempting to send an XI message synchronously using connection AFW.
Success Trying to put the message into the call queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the call queue.
Success The message status set to DLNG.
Success The message was successfully transmitted to endpoint http://XYZ.com:8000/sap/xi/engine?type=entry using connection AFW.
Success The application sent the message synchronously using connection AFW. Returning to application.
Success The message status set to DLVD
**********3rd (Received Messages)
Success Using connection AFW. Trying to put the message into the receive queue.
Success The XI response message for message d0372be1-4a74-11db-91d7-001279933263(INBOUND) was successfully returned to the calling application.
Success The message status set to DLVD.
**********4th (Received Messages)
Success The message was successfully received by the messaging system. Profile: XI URL: http://XYZ.com:50000/MessagingSystem/receive/AFW/XI
Success Using connection AFW. Trying to put the message into the request queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the request queue.
Success The message status set to DLNG.
Success Delivering to channel: IF_O_502_WebserviceBusService_SOAP_In_02
Success SOAP: request message entering the adapter
Success SOAP: completed the processing
Success SOAP: response message received d0372be1-4a74-11db-91d7-001279933263
Success The message status set to DLVD.
Success The message was successfully delivered to the application using connection AFW.

Error in Call Adapter (IDOC- XI- FILE)

Hello,
i have got the following error message in the integration engine monitoring in the "call adapter" part:
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)
What is the AFW application?????

Hi Christian,
Have a look at the following thread, it might be useful
XI Server Malfunction:Error in Receiver Adapter
Regards
Suraj

Error in Call Adapter step

Hello,
We have RFC --> HTTPS scenario.
The RFC Destination of type G is created in XI and the connection test is working fine.
When I run this scenario, sometimes I get following error:
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
Error in sxmb_moni in Call Adapter Step:
<?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="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
However sometimes it works fine.
Please help to resolve this.
Thanks in advance,
Hetal

Hello Hetal,
Can you please elaborate more on the scenario. if it is a RFC -> PI -> SOAP scenario please check if you are using the correct target URL in your Receiver Comm. Channel. Also check if the backend service could be unstable due to network load.
Thanks.
Kiran

Error in SXMB_MONI in SOAP Header -- Call Adapter

Similar Messages

Maybe you are looking for