Execption_during_execute - RFC2WS

hello
I am running RFC2WS sync message and recieve this error
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>Application</SAP:Category>
  <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
  <SAP:P1>com/sap/xi/tf/_WorkQueuesInquiry_WS2RFC_Response_</SAP:P1>
  <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
  <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>During the application mapping com/sap/xi/tf/_WorkQueuesInquiry_WS2RFC_Response_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
  <SAP:Retry>N</SAP:Retry>
  </SAP:Error>
it happend in the QA environment after exported from DEV to QA(it is working ok in DEV). the mapping seem to be identical what in QA and in DEV, but still recieve this message.
I checked this mapping problem
and every thing seem to be OK unless I didnt under stand exactly whta to test.
help will be apprecieated how to find the exact error.
Kfir

I tryed this already and forgot to add it, I took the payload from the source meassage (request), and this is what I recieve in the test
10:19:18 Start of test
Cannot produce target element /ns1:getWorkQueues. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns1:getWorkQueues. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
10:19:19 End of test
and now I am stuck and dont know what is the exact problem
Kfir

Similar Messages

  • Problem in test environment in RFC2WS service (worked in DEV)

    hello
    I have RFC2WS sync scenario. every works ok in the dev environment. after import the interface to the test environment, I recieve this error below.
    I also tryed to run the unitest and recieved and error in the IM stage that "root element expected" but I think it is ok, since this message I also recieved in the dev environment and as I said before, it is working as expected.
    more over, if I take the measse from the sxmb_moni and run it in the MM it is successfully transfer to the WS.
    I also tryed to refresh the cache and reimport the RFC and the interface and rewrite the scenario in the ID. any suggestions?
    (added the error message and below that message in the SXMB)
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AdobeMail_RFC2WS_REQ_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:463) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:174) 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:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor305.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 $Proxy158.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler
    message in the SXMB
      <?xml version="1.0" encoding="UTF-8" ?>
    <rfc:ZRFC_SPREAD_FROM_IMAGE xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
    <DOCIDS>
      <item>09002347802f6d70</item>
      </DOCIDS>
    <MAIL>
      <SUBJECT>******************************</SUBJECT>
      <MESSAGE>*************************************</MESSAGE>
      <FROMADDRESS>#######</FROMADDRESS>
      <FROMNAME>AVRAHAMP</FROMNAME>
    <TO>
    <item>
      <ADDRESS>#######</ADDRESS>
      <NAME>טסט טסט</NAME>
      </item>
      </TO>
      <CC />
      <BCC />
    <REPLYTO>
    <item>
      <ADDRESS>#######</ADDRESS>
      <NAME>AVRAHAMP</NAME>
      </item>
      </REPLYTO>
      <BOUNCEADDRESS />
      <HOSTNAME />
      <HOSTPORT />
      <CHARSET />
      </MAIL>
      <PASSWORD></PASSWORD>
      <TARGETAPPLICATION>CRM</TARGETAPPLICATION>
      <USERNAME>imagesoa</USERNAME>
      </rfc:ZRFC_SPREAD_FROM_IMAGE>

    this is the trace
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <Trace level="1" type="B" name="interface activity determination">
      <Trace level="1" type="T">Version 000</Trace>
      <Trace level="1" type="T">Message status 000</Trace>
      <Trace level="1" type="T">Interface action INIT</Trace>
      <Trace level="1" type="T">(must be INIT for a new determination)</Trace>
      <Trace level="1" type="T">Message type BEST EFFORT. -> No determination</Trace>
      <Trace level="1" type="T">Set interface action INIT into *MAST*</Trace>
      </Trace>
      <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Interface Mapping http://Migdal.co.il/CRM/SAP-CRM/AdobeMail AdobeMail_RFC2WS_IM</Trace>
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AdobeMail_RFC2WS_REQ_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:174) 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:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor305.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 $Proxy158.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451)(:main:, row=7, col=451) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.engine.lib.xml.parser.XMLParser.handleContentReference(XMLParser.java:2329) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2460) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.engine.lib.xml.parser.XMLParser.handleContentReference(XMLParser.java:2329) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2460) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more</Trace>
      <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AdobeMail_RFC2WS_REQ_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451)</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/_AdobeMail_RFC2WS_REQ_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor305.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 $Proxy158.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:174) 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:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor305.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 $Proxy158.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451)(:main:, row=7, col=451) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.engine.lib.xml.parser.XMLParser.handleContentReference(XMLParser.java:2329) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2460) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.engine.lib.xml.parser.XMLParser.handleContentReference(XMLParser.java:2329) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2460) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more</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" />
    - <!--  ************************************
      -->
      </SAP:Trace>

  • RFC2WS sync - dont see the responce from WS in the xmb_moni

    hello experts
    I know that a respond is send, but I can not see it in the sxmb_moni.
    in the RWB I recieve this erros
    SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
    Delivery of the message to the application using connection AFW failed, due to: Sync application request expired.. Setting message to status failed
    The message status set to FAIL
    Returning synchronous error message to calling application: Sync application request expired..
    I think this is Timeout but I am not sure.
    appreciate if this is familiar and know how to fix this problem in order to recieve the return message

    You use the ABAP proxy runtime to handle the errors
    System errors, which are triggered by the runtime. These might be errors during transfer, due to a failed server,
    Application errors, which are triggered or handled by the application alone. An example would be a request for data about a material that is unknown in the receiver system.
    Application error handling is essentially of interest in the synchronous case. In this case, a receiver can inform a sender that an application error has occurred during processing of a request message.

  • Call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException

    hello
    I am running an interface RFC2WS sync and recieve this message in the RFC. the message does not get out of the XI and rich the target (WS).
    the XI been upgraded lately, and I think this might be the cuase to the problem, becuase the interface been worked before, and still working in PROD environment as is.
    what could be the problem and how can I start investigate it to find the problem?
    this is what the SAP recieves
    call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException
    Thanks
    Kfir

    Hi Kfir,
    just check in RWB, in component monitoring, the status of integration server and adapter engine.......if it is red, then ask your basis guys to remove that error................just check your comm channels, i think your comm channels are in error, if they are just edit them, save and activate them again..........i think then your this issue will be resolved.'
    Regards,
    Rajeev Gupta

  • Cutting last char in the XI

    hello experts
    I have a scenario RFC2WS and sending
      <?xml version="1.0" encoding="UTF-8" ?>
    - <rfc:ZRFC_POLICY_OR_INSURANCE xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
      <PASSWORD>kf001</PASSWORD>
      <USERNAME>kfirg001</USERNAME>
      </rfc:ZRFC_POLICY_OR_INSURANCE>
    but in the XI I am recieving
      <?xml version="1.0" encoding="UTF-8" ?>
    - <rfc:ZRFC_POLICY_OR_INSURANCE xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
      <PASSWORD>kf00</PASSWORD>
      <USERNAME>kfirg00</USERNAME>
      </rfc:ZRFC_POLICY_OR_INSURANCE>
    it is always cutting the last char in the username\password. in the RFC it is defined as a String.
    I couldnt find out why it is cutting the last char and help would be great.
    Thanks
    Kfir

    Hi,
    Is it possible for you to send it with Filed type as CHAR instead of String..
    In RFC source code you could handle this kind of conversion.
    Try with CHAR...instead of string.
    Thanks
    Swarup

  • Loading WSDL to the XI

    hello experts
    I have XI7.0 and a scenario RFC2WS. I am trying to load the WSDL to the XI and when I enter it to the MESSAGE INTERFACE I dont see any of the methods that the WSDL has.
    in XML SPY I am able to make a SOAP REQUEST out of the WSDL.
    I try to play with the schema (make one schema) or with the name spaces but with out any success.
    the wsdl is:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://compulsoryRenewService.services.elementar.migdal.co.il" xmlns:intf="http://compulsoryRenewService.services.elementar.migdal.co.il" xmlns:tns1="http://vo.compulsoryRenewService.services.elementar.migdal.co.il" xmlns:tns2="http://common.services.elementar.migdal.co.il" xmlns:tns3="http://exceptions.common.fw.ness.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://compulsoryRenewService.services.elementar.migdal.co.il">
         <wsdl:types>
              <schema elementFormDefault="qualified" targetNamespace="http://compulsoryRenewService.services.elementar.migdal.co.il" xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://vo.compulsoryRenewService.services.elementar.migdal.co.il"/>
                   <import namespace="http://common.services.elementar.migdal.co.il"/>
                   <import namespace="http://exceptions.common.fw.ness.com"/>
                   <element name="getCompulsoryRenewData">
                        <complexType>
                             <sequence>
                                  <element name="anaf" type="xsd:int"/>
                                  <element name="year" type="xsd:string"/>
                                  <element name="month" type="xsd:string"/>
                             </sequence>
                        </complexType>
                   </element>
                   <element name="getCompulsoryRenewDataResponse">
                        <complexType>
                             <sequence>
                                  <element name="getCompulsoryRenewDataReturn" type="tns1:PolicyRenewDataList"/>
                             </sequence>
                        </complexType>
                   </element>
                   <complexType name="ArrayOf_tns1_PolicyRenewData">
                        <sequence>
                             <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:PolicyRenewData"/>
                        </sequence>
                   </complexType>
                   <element name="fault" type="tns3:FatalException"/>
              </schema>
              <schema elementFormDefault="qualified" targetNamespace="http://common.services.elementar.migdal.co.il" xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://compulsoryRenewService.services.elementar.migdal.co.il"/>
                   <import namespace="http://vo.compulsoryRenewService.services.elementar.migdal.co.il"/>
                   <import namespace="http://exceptions.common.fw.ness.com"/>
                   <complexType name="BaseResult">
                        <sequence>
                             <element name="errorMessage" nillable="true" type="xsd:string"/>
                             <element name="errorCode" type="xsd:int"/>
                        </sequence>
                   </complexType>
              </schema>
              <schema elementFormDefault="qualified" targetNamespace="http://vo.compulsoryRenewService.services.elementar.migdal.co.il" xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://compulsoryRenewService.services.elementar.migdal.co.il"/>
                   <import namespace="http://common.services.elementar.migdal.co.il"/>
                   <import namespace="http://exceptions.common.fw.ness.com"/>
                   <complexType name="PolicyRenewData">
                        <sequence>
                             <element name="policyId" nillable="true" type="xsd:decimal"/>
                             <element name="id" nillable="true" type="xsd:decimal"/>
                             <element name="endDate" nillable="true" type="xsd:string"/>
                             <element name="anaf" nillable="true" type="xsd:decimal"/>
                             <element name="startDate" nillable="true" type="xsd:string"/>
                             <element name="runninigNum" nillable="true" type="xsd:decimal"/>
                        </sequence>
                   </complexType>
                   <complexType name="PolicyRenewDataList">
                        <complexContent>
                             <extension base="tns2:BaseResult">
                                  <sequence>
                                       <element name="policyRenewDataList" nillable="true" type="impl:ArrayOf_tns1_PolicyRenewData"/>
                                  </sequence>
                             </extension>
                        </complexContent>
                   </complexType>
              </schema>
              <schema elementFormDefault="qualified" targetNamespace="http://exceptions.common.fw.ness.com" xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://compulsoryRenewService.services.elementar.migdal.co.il"/>
                   <import namespace="http://vo.compulsoryRenewService.services.elementar.migdal.co.il"/>
                   <import namespace="http://common.services.elementar.migdal.co.il"/>
                   <complexType name="GeneralException">
                        <sequence/>
                   </complexType>
                   <complexType name="FatalException">
                        <complexContent>
                             <extension base="tns3:GeneralException">
                                  <sequence/>
                             </extension>
                        </complexContent>
                   </complexType>
              </schema>
         </wsdl:types>
         <wsdl:message name="FatalException">
              <wsdl:part name="fault" element="intf:fault"/>
         </wsdl:message>
         <wsdl:message name="getCompulsoryRenewDataResponse">
              <wsdl:part name="parameters" element="intf:getCompulsoryRenewDataResponse"/>
         </wsdl:message>
         <wsdl:message name="getCompulsoryRenewDataRequest">
              <wsdl:part name="parameters" element="intf:getCompulsoryRenewData"/>
         </wsdl:message>
         <wsdl:portType name="CompulsoryRenewService">
              <wsdl:operation name="getCompulsoryRenewData">
                   <wsdl:input name="getCompulsoryRenewDataRequest" message="impl:getCompulsoryRenewDataRequest"/>
                   <wsdl:output name="getCompulsoryRenewDataResponse" message="impl:getCompulsoryRenewDataResponse"/>
                   <wsdl:fault name="FatalException" message="impl:FatalException"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="CompulsoryRenewServiceSoapBinding" type="intf:CompulsoryRenewService">
              <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="getCompulsoryRenewData">
                   <wsdlsoap:operation soapAction=""/>
                   <wsdl:input name="getCompulsoryRenewDataRequest">
                        <wsdlsoap:body use="literal"/>
                   </wsdl:input>
                   <wsdl:output name="getCompulsoryRenewDataResponse">
                        <wsdlsoap:body use="literal"/>
                   </wsdl:output>
                   <wsdl:fault name="FatalException">
                        <wsdlsoap:fault name="FatalException" use="literal"/>
                   </wsdl:fault>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="CompulsoryRenewServiceService">
              <wsdl:port name="CompulsoryRenewService" binding="intf:CompulsoryRenewServiceSoapBinding">
                   <wsdlsoap:address location="http://mguxp70:9064/ElementarSOA/services/CompulsoryRenewService"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    if any one know what is missing, or to add something to the WSDL in order to load it and see the method will be much of an help.
    Thank you very much for your help
    Kfir

    Hi Kfir,
    I was able to load your wsdl file and can see three messages (FatalException,getCompulsaryRenewDateRequest, getCompulsaryRenewDateResponse)
    I will suggest you to do like this:
    1. Open your wsdl in a notepad
    2. Find for namespace http://compulsoryRenewService.services.elementar.migdal.co.il (namespace length = 61 characters)
    3. Replace with http://compulsoryRenewService.services.elementar.migdal.co (new length = 8 character)
    4. Save and try to import as a wsdl in external definitions. Keep option of Messages as "From all Available Message Definitions"
    Regards
    Suraj

  • Problem creating schema source while using WebService in MessageMapping

    Hi, scenario is RFC2WS.
    Problem that occurs is that when i want to use a method from WebService in MessageMapping XI won't import the structure. I am getting following error. The WSDL is from an external portal on which a WebService is ready to invoke.
    <b>What might be the problem?! </b>
    <i>
    Problem when creating schema source:
    Details
    java.lang.NullPointerException
    STACKTRACE:
    com.sap.aii.utilxi.misc.api.BaseException: java.lang.NullPointerException
        at com.sap.aii.ib.gui.xmleditor.docview.views.XsdSchemaTextable.setSchema(XsdSchemaTextable.java:86)
        at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.setSchema(XsdContainerTextView.java:46)
        at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.<init>(XsdContainerTextView.java:36)
        at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.makeFromTreeDoc(MultiViewEditor.java:216)
        at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.<init>(MultiViewEditor.java:64)
        at com.sap.aii.mappingtool.mf.TransformationPanel.createTargetView(TransformationPanel.java:264)
        at com.sap.aii.mappingtool.mf.TransformationPanel.<init>(TransformationPanel.java:100)
        at com.sap.aii.mappingtool.mf.MappingTool.<init>(MappingTool.java:32)
        at com.sap.aii.mappingtool.api.MappingToolFactory.getInstance(MappingToolFactory.java:96)
        at com.sap.aii.mappingtool.fwutil.util.ToolUtil.restartTool(ToolUtil.java:315)
        at com.sap.aii.ibrep.gui.mapping.xitrafo.XiTransformationView.loadIfrSchema(XiTransformationView.java:274)
        at com.sap.aii.ibrep.gui.mapping.xitrafo.XiMappingView$LinkDataTarget.setData(XiMappingView.java:378)
        at com.sap.aii.ibrep.gui.mapping.xitrafo.XiTransformationView$MessageDataTarget.setData(XiTransformationView.java:973)
        at com.sap.aii.utilxi.swing.toolkit.dnd.DataTarget.setData(DataTarget.java:514)
        at com.sap.aii.utilxi.swing.toolkit.dnd.DataTarget.drop(DataTarget.java:462)
        at java.awt.dnd.DropTarget.drop(Unknown Source)
        at sun.awt.dnd.SunDropTargetContextPeer.processDropMessage(Unknown Source)
        at sun.awt.dnd.SunDropTargetContextPeer.access$800(Unknown Source)
        at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchDropEvent(Unknown Source)
        at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchEvent(Unknown Source)
        at sun.awt.dnd.SunDropTargetEvent.dispatch(Unknown Source)
        at java.awt.Component.dispatchEventImpl(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
        at java.awt.LightweightDispatcher.processDropTargetEvent(Unknown Source)
        at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Window.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)
    STACKTRACE:
    java.lang.NullPointerException
        at com.sap.aii.utilxi.xsd.api.XsdHandler.saveSchemaToDocument(XsdHandler.java:61)
        at com.sap.aii.ib.gui.xmleditor.docview.views.XsdSchemaTextable.setSchema(XsdSchemaTextable.java:82)
        at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.setSchema(XsdContainerTextView.java:46)
        at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.<init>(XsdContainerTextView.java:36)
        at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.makeFromTreeDoc(MultiViewEditor.java:216)
        at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.<init>(MultiViewEditor.java:64)
        at com.sap.aii.mappingtool.mf.TransformationPanel.createTargetView(TransformationPanel.java:264)
        at com.sap.aii.mappingtool.mf.TransformationPanel.<init>(TransformationPanel.java:100)
        at com.sap.aii.mappingtool.mf.MappingTool.<init>(MappingTool.java:32)
        at com.sap.aii.mappingtool.api.MappingToolFactory.getInstance(MappingToolFactory.java:96)
        at com.sap.aii.mappingtool.fwutil.util.ToolUtil.restartTool(ToolUtil.java:315)
        at com.sap.aii.ibrep.gui.mapping.xitrafo.XiTransformationView.loadIfrSchema(XiTransformationView.java:274)
        at com.sap.aii.ibrep.gui.mapping.xitrafo.XiMappingView$LinkDataTarget.setData(XiMappingView.java:378)
        at com.sap.aii.ibrep.gui.mapping.xitrafo.XiTransformationView$MessageDataTarget.setData(XiTransformationView.java:973)
        at com.sap.aii.utilxi.swing.toolkit.dnd.DataTarget.setData(DataTarget.java:514)
        at com.sap.aii.utilxi.swing.toolkit.dnd.DataTarget.drop(DataTarget.java:462)
        at java.awt.dnd.DropTarget.drop(Unknown Source)
        at sun.awt.dnd.SunDropTargetContextPeer.processDropMessage(Unknown Source)
        at sun.awt.dnd.SunDropTargetContextPeer.access$800(Unknown Source)
        at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchDropEvent(Unknown Source)
        at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchEvent(Unknown Source)
        at sun.awt.dnd.SunDropTargetEvent.dispatch(Unknown Source)
        at java.awt.Component.dispatchEventImpl(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
        at java.awt.LightweightDispatcher.processDropTargetEvent(Unknown Source)
        at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Window.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)
    </i>

    Hi ,
    Can you please cross check these steps carefully.
    1. After importing the WSDL using external definition, did you checked msges Tab for for the included msg to see what msges you have added.
    and be careful that the namespaces of the messages are part of the WSDL description and can differ from the namespace of the external definition object.
    2.Did you created message Interface corresponding to the message types from the external definition? it is needed to route the message to webService. Here select message types of the external definition object. Assign input and output messages.
    3. Creating a SOAP Receiver Channel
    To call the Web service, you create a communication channel with type SOAP and
    direction receiver in the Integration Directory. The obligatory parameters in the
    configuration are Target URL and SOAP action. You get the values you have to enter
    here from the WSDL file.
    Creating a SOAP Sender Channel
    When you create a SOAP sender channel you have to define the namespace and the
    name of a message interface. Since no input help is provided, you copy and paste the
    values from your Integration Repository.
    Select the Quality of Service according to your interface type. If you are using a
    synchronous interface, select Best Effort. Otherwise, select Exactly Once or EOIO.
    Hope this will help you to figure out.
    Regards
    Aashish Sinha
    PS : reward points if helpful

  • Flat XML in the WSDL

    hello
    I am recieving in RFC2WS a WSDL. in the respone the WSDL look like this:
    <s:element name="GetZagmshDataResponse">
      <s:complexType>
        <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="GetZagmshDataResult">
         <s:complexType mixed="true">
              <s:sequence>
                 <s:any/>
            </s:sequence>
         </s:complexType>
            </s:element>
         </s:sequence>
      </s:complexType>
    </s:element>
    in the Tag <any> I will recieve a full structure. for example:
    <Table>
      <DateID>3044</DateID>
      <DateValue>2008-05-01T00:00:00+03:00</DateValue>
      <OriginalEmployeeId>10000416</OriginalEmployeeId>
      <OriginalReportDate>2008-05-01T00:00:00+03:00</OriginalReportDate>
      <OriginalImportTime>2008-05-02T04:12:08.687+03:00</OriginalImportTime>
      <OriginalDayType>5</OriginalDayType>
    </Table>
    <Table1>
    <employName>kfir</employName>
    <employLastName>gold</employLastName>
    </Table1>
    my Q is how can I map the inner data in the XML that I will recieve for this kind of WSDL so I will be able to recieve all the tables (could be multiple tables)?
    Thanks
    Kfir

    Refer these links for XSLT mapping:
    Step – By – Step Simple Approach for XSLT Mapping
    File to Multiple IDocs (XSLT Mapping)
    Regards,
    Geetha.

  • Connection refused message

    hello
    I am trying to run a sync interface RFC2WS.
    I recieve the message and in the response I recieve this message:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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: Connection refused: connect</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    in the comm. channel I recieve a familiar Q,
    24.03.2008 08:18:00 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
    24.03.2008 08:18:00 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
    24.03.2008 08:18:00 Error Exception caught by adapter framework: Connection refused: connect
    24.03.2008 08:18:00 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect. Setting message to status failed.
    24.03.2008 08:18:00 Error The message status set to FAIL.
    24.03.2008 08:18:00 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect.
    I am trying to get to the root of the problem, and from what I know, the problem is not in the XI.
    what else can I check in order to be sure that the problem is not in the XI? how can I know exactly where the problem is?
    Thanks
    Kfir

    HI,
    The XI monitoring tools are best for troubleshooting these kind of problems.
    In RWB, in Adapter Engine..you could monitor the communication Channels you have developed for RFC and SOAP connection.
    Check for the log in it. From this you will get where is the problem.
    Even the URL that you are using for SOAP receiver , try to copy -paste it in Internet browser and see if you can successfully ping to the Web Service.
    Even in SXMB_MONI, you could analyse the whole message flow step-by step
    Thanks
    Swarup

Maybe you are looking for

  • HT2731 I want to create a second  iTune account for iBooks.

    I am trying to publish an iBook. When I tried to use my current ID which I used for my Apple apps. I provided banking and tax information when I made the application to upload the apps. I received a message I must create a different ID. How to create

  • Any ideas on how to swap a to&from date table to monthly using DI?

    New to DI, so after a bit of product usage advice! I've got a table that looks like this... ID,NAME,SDATE,EDATE,TOTALDAYS,WEEKDAYS 1,James,01/01/2010,10/01/2010,10,6 2,John,03/02/2010,19/02/2010,16,13 1,James,15/04/2010,23/07/2010,100,72 3,Chris,05/0

  • Programming binary data in Java

    A use case contains a series of yes/no options. In the web front end, they are in the form of checkboxes. For anyone with CS background, it is easy to think of a series of binary data which is an integer in Java. One advantage of this approach is tha

  • Elements 11 (not premier) will not run on Windows7

    Want to but Elements 11. Amazon does not list Windows 7 as an option, only XP and vista. Will elements not run on 7? Do not want Premier.

  • IMac G5 iSight won't boot from external optical drive . . . FW or USB

    Hello, all. I have an iMac G5 iSight with a busted optical drive. Every six months or so, OS 10.4 eats itself (directory structure goes corrupt), and I need to reinstall. The issue I'm having is that the computer won't boot off of my external optical