Error in SOAP Adapter Response

I am getting the following Error in SOAP Response
... but when i tried the with ALTOVA XML SPY its working fine..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Inbound Message
  -->
- <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: Registration Method error</SAP:AdditionalText>
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack />
  <SAP:Retry>M</SAP:Retry>

hi,
check the XML that you send to the WS
if the server returned this soap fault it might mean that XML was not correct .
also take a look at the default.trc log file from visual administrator-> server -> services -> log viewer -> locations -> com -> aii -> bc -> soap
regards
kummari
Edited by: kummari on Jul 29, 2008 5:40 AM

Similar Messages

  • ERROR IN SOAP ADAPTER

    Hi Guys,
    I am trying to send a SOAP message to an external webservice to use a proxy.
    I put host and gate in receiver soap adapter.
    When i execute i have the next error:
    SOAP:Call Failed
    SOAP:error occured:java.io.IOException: invalid content type for SOAP: TEXT/PLAIN
    Has anyone got a suggestion as to how I may resolve this problem?
    Thanks very much,
    Antonio

    Hi Antonio,
    Basically the issue is with the response that the webservice is returning, it may not be a valid reposne..use the TCP-Monitor tool from SAP to see the request/response message flowing...
    Please do a search onsdn itself on your issue...you should get lots of threads talking about the same problem in the XI forum...
    Thanks,
    Renjith

  • Error on SOAP Adapter

    Hello,
    Got the following error on a SOAP receiver. Its a synchones interface. I get the following error:
    com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Internal Server Error (Caught exception while handling request: java.rmi.RemoteException: java.sql.SQLException:
    Transport protocol: HTTP
    Message protocol: SOAP 1.1
    Any help would be welcome!
    Regards,
    Erik

    Internal Server Error (Caught exception while handling request:
    The message format that you are sending to the WebService is not proper.
    1) Confirm from the WS team that you are using the required WSDL (the WSDL is latest)
    2) The mapping is producing the required target (WSDL) structure.
    Got the following error on a SOAP receiver.
    3) Since you are having SOAP at the receiving end make sure that you have maintained the proper Target URL and Action (if any) in the SOAP Channel.
    Its a synchones interface
    I hope you have maintained proper Message/ Service Interfaces for this scenario (synchronous).
    Regards,
    Abhishek.

  • PO message processing error at SOAP Adapter

    Hello All,
    After an PO scenarion setup and performing one messageprocessing in found following error at RW Message Monitoring:
    Exception caught by adapter framework: SOAP: response message contains an error XIServer/UNKNOWN/ModuleUnknownException - com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#13 $) at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:412) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_
    Please could someone tell me where the problem is?
    Regards,
    Jochen

    Hi Jochen
    Check if thse threads can help you
    Now based on error description -
    Refer this SAP Note - 856597 QUestion no 1 -for SOAP adapter configuration- i.e URL
    Also have a look into this thread-
    SOAP Problem
    SOAP Error when testing messages.
    *************Reward points if helpfull*************

  • Mapping related errors in SOAP Adapter scenario

    Hello Friends
    I have done this several times and in this particular case I am getting some errors.
    Here is the scenario
    External  --- (SOAP) ---  XI  -
    (RFC) -
    SAP TABLE.
    Program
    I have created an XSD (External definition) to get the data to XI using SOAP Adapter.
    I have done the mapping and everything looks Ok to me. I even restarted my XI server. All other scenarios are working except for this particular scenario in question.
    When I looked at <SXMB_MONI> I see the xml string coming in correctly with proper tags and data as expected.
    However, it is failing with some mapping errors.
    Here is the error message I got in SXMB_MONI
    Any help will be greatly appreciated.
      <Trace level="1" type="T">Interface Mapping http://cincom.com/config AddConfigDNA</Trace>
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AddConfigDNARequest_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. 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:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) 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: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.processFunction(MappingServiceObjectImpl0.java:131) 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.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.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.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:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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 /ns1:ZBAPI_ADD_CONFIG_DNA. 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:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) 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: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.processFunction(MappingServiceObjectImpl0.java:131) 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.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.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.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:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. 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/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. 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: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.processFunction(MappingServiceObjectImpl0.java:131) 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.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.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.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:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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 /ns1:ZBAPI_ADD_CONFIG_DNA. 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:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) 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: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.processFunction(MappingServiceObjectImpl0.java:131) 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.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.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.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:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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 /ns1:ZBAPI_ADD_CONFIG_DNA. 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:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) 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: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.processFunction(MappingServiceObjectImpl0.java:131) 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.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.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.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:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) 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" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
    - <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
    - <SAP:Payload xlink:href="cid:[email protected]">
      <SAP:Name>MainDocument</SAP:Name>
      <SAP:Description>Main XML document</SAP:Description>
      <SAP:Type>Application</SAP:Type>
      </SAP:Payload>
      </SAP:Manifest>
      </SOAP:Body>
      </SOAP:Envelope>

    Hi Ram,
    This error is due to error in message mapping.The map rules you have specified for the Node: "ZBAPI_ADD_CONFIG_DNA" is not getting satisfies due to which it is unable to create the Node who occurance is mandatory.Check if map rule specified for this particular Node.
    Thanks,
    Bhargav.
    Note:Award Points if found useful

  • Error in SOAP Adapter because XML is big

    <b>Hi guys! I have a SOAP Adapter (Sender) that works fine when the XML it receives is small. If the XML is big, this error happens:</b><br><br><br>
    java.lang.NullPointerException; nested exception caused by:
    java.lang.NullPointerException; nested exception caused by:
    com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)
         at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
         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(Unknown Source)
         at javax.xml.parsers.SAXParser.parse(Unknown Source)
         at com.sap.aii.messaging.util.StreamXMLScannerImpl$EventProducer.run(StreamXMLScannerImpl.java:598)
         at java.lang.Throwable.<init>(Throwable.java:56)
         at java.lang.Throwable.<init>(Throwable.java:67)
         at org.xml.sax.SAXException.<init>(Unknown Source)
         at org.xml.sax.SAXParseException.<init>(Unknown Source)
         at com.sap.engine.lib.xml.parser.NestedSAXParseException.<init>(NestedSAXParseException.java:23)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
         at javax.xml.parsers.SAXParser.parse(Unknown Source)
         at javax.xml.parsers.SAXParser.parse(Unknown Source)
         at com.sap.aii.messaging.util.StreamXMLScannerImpl$EventProducer.run(StreamXMLScannerImpl.java:598)
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)
         at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
         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)
         ... 3 more
    <br><br><br>
    <b>ps: the big XML is well formed! It seems the application server refuses the http request (the message does not appear at SXMB_MONI)</b><br><br>
    thanks in advance<br><br>
    Julio

    Julio,
    Are you sure that XML is correct?
    No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)
    I also see Parse exceptions at different lines?
    check the NOTE : 931765 @
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=931765
    Check if the incoming XML has style informaton associated with it. Refer to following link for more info.
    http://schemas.xmlsoap.org/soap/envelope/
    If the problem still persists, Restart J2EE Instance.
    Regards,
    Venkat.
    Edited by: Venkat Anusuri on Jun 3, 2009 5:34 PM

  • Error Https SOAP Adapter:NoSuchAlgorithmException: No such algorithm: RSA

    Hi,
    I'm using a SOAP Adapter Receiver to integrate a file to an External WS (with HTTPS). But when I tried to execute It I got the following error:
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Unable to encrypt preMasterSecret: java.security.NoSuchAlgorithmException: No such algorithm: RSA: iaik.security.ssl.SSLException: Unable to encrypt preMasterSecret: java.security.NoSuchAlgorithmException: No such algorithm: RSA
    SOAP: call failed: iaik.security.ssl.SSLException: Unable to encrypt preMasterSecret: java.security.NoSuchAlgorithmException: No such algorithm: RSA     
    I think It is a problem with the creation of the secure channel of HTTPS.
    Any tip is very welcome!!
    Thanks
    Martin

    http://java.sun.com/j2se/1.4.2/docs/guide/security/jce/JCERefGuide.html#AppA
    there is not much info to find about who provides for RSA.RSA is already implemented in the Crypto-Provider by Sun. You don't have to laod a special provider.
    The following sample is just enough:
    Cipher cipher = Cipher.getInstance("RSA");Jan

  • HTTP error in SOAP Adapter

    Hello Everybody,
    I have a SOAP adapter with several communication channels configured.
    When i want to test these scenarios, i obtain this error:
    com.sap.aii.messaging.net.TransportException: HTTP 401 Unauthorized
         at com.sap.aii.messaging.net.ClientHttpImpl.call(ClientHttpImpl.java:180)
         at com.sap.aii.messaging.adapter.WSTestClient.doPost(WSTestClient.java:241)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.aii.messaging.adapter.Zone.service(ModuleGUIBrowserEngine.java:1072)
         at com.sap.aii.messaging.adapter.HTTPRequest.run(ModuleGUIBrowserEngine.java:370)
    What could be happening? Is something about permissions in SOAP? in this case what are the SOAP commands to specify this parameters?
    Thakns a LOT!!
    Regards,
    Javier Sahagun

    Hi agasthuri
    I readed https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4061. [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    I restarted the service in SICF transaction, etc, etc, etc.....
    now I execute and I receive
    java.lang.NullPointerException
         at com.sap.aii.messaging.net.EndpointImpl.parseURI(EndpointImpl.java:303)
         at com.sap.aii.messaging.net.EndpointImpl.<init>(EndpointImpl.java:59)
         at com.sap.aii.messaging.net.EndpointHTTPImpl.<init>(EndpointHTTPImpl.java:33)
         at com.sap.aii.messaging.net.FactoryImpl.createEndpoint(FactoryImpl.java:116)
         at com.sap.aii.messaging.adapter.XMBTestClient.doPost(XMBTestClient.java:223)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.aii.messaging.adapter.Zone.service(ModuleGUIBrowserEngine.java:1072)
         at com.sap.aii.messaging.adapter.HTTPRequest.run(ModuleGUIBrowserEngine.java:370)

  • How to handle error in SOAP adapter

    Hi all,
    I have a scenario where i have configured SOAP adapter to call a webservice which is working fine. But when ever server hosting the webservice is down, PI still shows the message is processed successfully. Through RWB, i can see that message failed in Channel Monitoring.
    Can any body suggest how to capture this so that i could raise an alert. In my alert config, i have already set it for the receiver failure.
    Thanks
    -Kulwant

    HI Kulwant
    SOAP always send SOAP fault message in SYNC as well as ASync. You get HTTP response code 200 or system failure.
    If the target system is down you will see successfully process but the response will be system failure
    Check https://service.sap.com/sap/support/notes/856597
    Moreover you can implement BPM where you can raise exception capturing this response. Thats the other way !!
    Thanks
    Gaurav

  • Suspend 20 Iterations Error in Soap Assess Response (ODS)

    OPA Experts,
    I'm trying to replace the default error message you receive when the inferencing cycle has errored-out after 20 iterations. I'm restricted to using ODS and none of the features of OWD. Using Java framework.
    I've encountered this several times before and was able to stop via error() in the rules, but for this particular instance (see below), I can throw the error and view both this and the 20 iterations message in OPM (20 iterations in red box at top of OPM interface and custom error message in output window), but the soap assess response presents the 20 iterations (ThinkException) message and nothing else.
    "This particular instance" means an illegal attribute value and relationship population in the same entity. E.g. TaxReturn entity --> <attribute>tax_filing_status = "Single" and <relationship>tax_filing_spouse populated. A person filing a tax return can only have a tax_filing_spouse populated when they have a tax_filing_status of "Married Filing Jointly".
    What I've tried so far:
    Catching and throwing the error via rules
    OnReturnResultEvent
    InferencingListener
    SoapServerException
    ThinkException override (which isn't really possible but I thought I'd try anyway )
    OnBeforeThinkEvent
    The request, in all of the above cases, only touches my empty constructors and none of my methods.
    Here's one example (among many) of my log4j log (edited for space and readability purposes):
    ========================================================================================
    388 [http-127.0.0.1-9000-Processor4] INFO  com.oracle.util.plugins.PluginRegistry  - Successfully created plugin factory: handleIllegalTaxRequest.HandleIllegalTaxRequest
    8509 [http-127.0.0.1-9000-Processor2] INFO  com.oracle.determinations.engine.Session  - User setting attribute i_return_filing-status, entity taxreturn, instance name 54f63ed31435527aebb709fac1417c00, session 1 to value 1
    21080 [http-127.0.0.1-9000-Processor2] INFO  com.oracle.determinations.engine.Session  - Engine inferring attribute o_per_pend-person, entity person, instance name SELF1120128911, session 1 to value true
    21080 [http-127.0.0.1-9000-Processor2] INFO  com.oracle.determinations.engine.Session  - Finishing inferencing on session 1
    21081 [http-127.0.0.1-9000-Processor2] TRACE com.oracle.determinations.ocs.UnknownMemberListener  - In UnknownMemberListener
    21083 [http-127.0.0.1-9000-Processor2] ERROR com.oracle.determinations.server.services.AbstractNativeService  - Could not reach a determination for rulebase 'FakeNameOfRulebase'. Reason: Think cycle has not stabilised after 20 iterations.  This is probably due to a fault in the inferencing listener.
    com.oracle.determinations.server.exceptions.ThinkException: Could not reach a determination for rulebase 'FakeNameOfRulebase'. Reason: Think cycle has not stabilised after 20 iterations.  This is probably due to a fault in the inferencing listener.
      at com.oracle.determinations.server.assess.AssessEngine.assess(AssessEngine.java:147)
      at com.oracle.determinations.server.services.assess.AssessAction.process(AssessAction.java:67)
      at com.oracle.determinations.server.services.AbstractNativeService.processRequest(AbstractNativeService.java:119)
      at com.oracle.determinations.server.DSServlet.doPost(DSServlet.java:103)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:879)
      at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
      at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
      at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
      at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
      at java.lang.Thread.run(Thread.java:722)
    ========================================================================================
    None of the inferencing responses in any of my logs present "tax_filing_spouse" relationship...so I must assume it's getting hung up on this. If I change the tax filing status in the request, I get the correct assess response with 0 errors. I tried getDecisionReport() of InferencingEvent to verify, but as mentioned above, only my constructors are being touched and none of my methods.
    Now, I could be approaching this incorrectly in my Java code, or there could be a way to catch and suspend this in the rules, but I've extended the capacity of my efforts and am about ready to throw my laptop out of the window. Any help would be greatly appreciated. I really need it!!!!
    v/r
    Mike

    Hi Mike,
    I'm not really sure what you want to achieve, this error message means that your assessment results are invalid and none of the conclusions can be relied upon so you really need to fix the rules themselves. This error can be caused by a loop in the rule logic as well as a a problem with an inferrencing listener (as suggested in the error message). You can check for rule loops in OPM and / or use visual inspection as you know which attribute / value triggers the problem.
    If you could share your rulebase and the source code for your UnknownMemberListener that may shed some light on the issue.
    If you really need to change the error message to you SOAP clients you may need to implement a custom service but this is unlikely to be trivial.

  • Data Headers in SOAP adapter Response

    Hi there,
    I have a working SOAP adapter on Xi 2.0, which accepts incoming requests from SOAP clients, it "transforms" these requests into RFC calls which in turn calls BAPI'S in R/3.
    The BIG issue is that Xi (the SOAP adapter) sets and sends a set of headers into the response back to the SOAP client. For security and performance reasons, you dont want the system to send those headers over the net to the SOAP client.
    Does anyone knows how to setup Xi in order to suppress these headers in the SOAP response?
    PS: Below an example of the headers in the SOAP envelope.
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
    <SOAP:Header><sap:MessageHeader xmlns:sap='http://sap.com/exchange/MessageFormat' version='1.0'>.......
    <Host>xxxx</Host>
    <Sysid/>
    <Sysnr>00</Sysnr>
    <Mandt>200</Mandt>
    <Dest/>
    <Userid>XI_USER</Userid>
    <Passwd>xxxx</Passwd>

    If I want to set the content in the SOAP header when the client in SAP XI how would I do that?
    I cannot see SOAP Header in XI MONI.
    Please advice. I want to add to the contents of SOAP Header created by XI SOAP Receiver Channel.
    Thanks
    Ashish

  • ABAP-Proxy to SOAP: Error in SOAP Adapter

    Hi!
    I would like to implement ABAP-Proxy to SOAP scenario.
    Unfortunately my SOAP receiver channnel has the following error:
    SOAP: call failed: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No SOAP Envelope but 1 definitions; HTTP 200 OK: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
    Furthermore the call of  /sap/bc/soap/rfc of business system B is erroneous
    http://<server system B>:8000/sap/bc/soap/rfc
    Here I get the error: HTTP 500 Internal Server error
    Can some one help me to solve this problem?
    Thank you very much!
    regards
    Holger

    Hi,
    Are you using the webservice exposed by SAP or it is third party webservice. Can you explain your complete scenario? What is the url you have given in your receiver SOAP Channel? Was that no configured earlier?
    If at all you are using the SAP webservice, the wsdl link should be.
    http://<server>:<http port>/sap/bc/soap/wsdl11?services=BAPI_MATERIAL_EXISTENCECHECK&sap-client=200
    The target url you will be able to see in the wsdl itself also
    amit

  • SOAP Adapter response

    Hi Group,
    Confifuring webservice->file asynchronous scenario ,in this scenario PI providing the webservice with request and response,once after file request is triggered needs to send back response as OK,can any body suggest how we can
    configure.

    Hello,
    You can try using the request response bean module as shown in this wiki
    http://wiki.sdn.sap.com/wiki/display/XI/UsingRequestResponseBeanModuleinFILE+Adapter
    Hope this helps,
    Mark

  • Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

    Hi All,
        We have a scenario of FTP-->PI---> Webservice.  While triggering the data in the FTP, it is failing in the PI with the below error
    SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
    Can you please help?

    Hi Raja- It seems to be a data quality issue.
    Check for the value @ 1447 position in the xml message that you are trying to send to web service..
    may be a date filed/decimal value which is not in expected format.

  • SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

    Hi there,
    I am trying to publish a file from SAP as web service using XI and SOAP Adapter.
    I am using ABAP proxy to get the data into XI.
    Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.
    But when I used SOAP Reciever adapter I am getting following error in RWB
    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: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error during parsing of SOAP header.
    <b>Scenario</b>: SAP ABAP Proxy -> XI -> WebService. Asynchronous.
    <b>SOAP</b> Receiver adaptor.
    <b>Target URL</b> http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce
    Do not use SOAP Envelop is checked.
    <b>SOAP Action</b> http://sap.com/xi/WebService/soap1.1
    What i am missing here? How should I solve this problem?
    Any help is appreciated,
    Thx,
    Yogi

    Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c).  On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can.  So in this case, the scenario would be:
    WS client -> XI -> R/3
    When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system).  XI itself does not provide or contain the service implementation.  When XI exposes a web service, it is always done via the <b>sender</b> soap adapter (i.e. if soap adapter is used).   Receiver soap adapter is used to call or consume an actual web service from an external application.
    Regards,
    Jin

Maybe you are looking for