Error in Receiver SOAP adadpter

Hi ,
While trigeering PI synchronous message with SOAP as receiver adapter, I am receiving error in the response message as
"Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error".
The scenario is SAP -> PI -> SOAP (Legacy ).I tried options like opening the url  maintained in receiver communication channel in explorer it points to webservice.
I had the same issue in Development and the issue got resolved by changing the url in the receiver channel but doesnt work
in Quality.
Regards
Robinson T

Hi Everyone,
I presume that the url present in the adapter engine cache url is not correct.
1.Login to PI server , go Tx sxmb_moni -> click on Goto -> Adapter Engine Cache.
The entry present in the Adapter Engine cache url should be in the form
http://<Integration Server name>:<com.sap.aii.connect.integrationserver.r3.httpport>/MessagingSystem/receive/AFW/XI
Kindly correct if it is wrong.
2.The above url should also match with the entries present for Adapter Framework in SLD.
In the link http://wiki.sdn.sap.com/wiki/display/XI/ChangingHTTPPortofdecentralizedAdapterEngine, there is the
mention of Content Maintainance -> XI Adapter Framework where one has to check the Port for XIRA of af.SID.
I am working in PI7.1 ( Service Pack:08 Release: NW07_08_REL ), but I could not see the above mentioned navigation.
Waiting for the reponse.
Regards
RT

Similar Messages

  • ADAPTER.HTTP_EXCEPTION, HTTP 500 Internal Server Error, in Receiver soap A

    Greetings All,
                         In my scenario i am calling external service of SFDC using receiver soap adapter but i am facing below error in the response.
    ADAPTER.HTTP_EXCEPTION, HTTP 500 Internal Server Error
    I am creating the soap structure/envelope using Java mapping since need to add additional parameter in soap header.
    I am setting the URL in java UDF using parameter TServerLocation.
    In comm channel checked "do not use soap envlope" also set the format to text/xml using MessageTransformBean.
    The service was working fine when tested in SoapUI tool.
    Looking forword for your help and will be appreciated.
    Thanks,
    Sandip

    Hello Sandip, I hope you are doing fine!
    I`m not sure if you are using a sync or async scenario...
    The behavior that you describe is the expected behavior for SOAP receiver adapter in nosoap mode, asynchronous case.
    The explanation that lies behind it is that in nosoap mode the bahavior is just similar to pure HTTP communication. An HTTP 4/5 error received from the target server is treated as HTTP internal error and logged into AFW as an error. The message in an asynchronous scenario without acknowledgements is normally seen as successful on IE side as it is successfully sent to the target system. It can be even successfully consumed by the target webservice, but for amo other reason, the HTTP request from SAP PI to the target system returns HTTP 500 error.
    If you ask for system delivery acknowledgements, you should get a non-successful delivery acknowledgement.
    In synchrnous scenarios, when a response is expected, the behavior is different.
    If this is a sync scenario, there is an official patch released on the service marketplace. SAP Note 1533195 is released.
    In addition to deploying the patch, apply the additional configuration steps. As per this note, for the default module
    sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    you will need to set:
    Module Key  = soap
    Parameter Name = noSOAPMakeSysErrFromResponseFault
    Parameter Value = false
    If you need to bypass the HTTP errors in the communication with the target system, you need to apply note 1055678.
    To apply it, just add  for the default module
    sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean in your receiver
    channel, Modules tab the following:
    Module Key  = soap
    Parameter Name = XMBWS.NoSOAPIgnoreStatusCode
    Parameter Value = false
    If you need any SOAP fault related behavior or any other SOAP related feature, you should setup the channel to run normal SOAP mode, since as already mentioned nosoap mode is used now.
    In addition, check note:
      856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
    section "1. Sender Connection"
    Q: I get a server error "500 Internal Servler Error" from the
    adapter's servlet. What went wrong?
    and get the trace to give you more details of the error.
    One more thing, VERY IMPORTANT.
    I STRONLGY recommend you to update all XI-PI components to latest patch available in the Service Marketplace. Thery are:
    XITOOLS, XIESR, XIAF, XIAFC, MESSAGING, XIGUI. Some of them might not be present depending on the release of you system. e.g: 3.0, 7.0, 7.1
    I hope this helps you.
    Cheers
    Jorge Eidelwein

  • Error in receiver SOAP adapter.

    Hi Experts,
    scenario name is proxy to soap asynchronous interface
    we are getting the below error from the soap receiver communication channel.
    -exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
    -Adapter Framework caught exception: null
    -Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to:  com.sap.engine.interfaces.messaging.api.exception.MessagingException
    please help us.
    regards
    elton

    can you confirm if you have configured the adapter correctly? Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 ***
    Also it will be a good idea to check with your end application and confirm if they have received the message and if it is a fault  message being triggered from their end (potentially data issues) that is showing up as an error in the adapter

  • Invalid Content Type Error in Receiver SOAP Adapter

    Hello Experts,
    Is there a solution for this problem?
    I am getting the following error in one of my receiver SOAP adapters:
    com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:...:com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
    I have checked the message I am sending to the receiver adapter and it is XML, ok. After checking this thread: Re: Error in soap receiver adapter and SAP note 856597 I used the TCPGateway program to check what the web service is answering to the adapter request and I found the problem is due to an authentication failure. The TEXT/HTML is an error page the SAP WebAS that hosts the webservice is sending out as response saying no login method succeeded.
    However...  The webservice URL and basic authentication information, the user and password, are configured correctly. I double checked it and I can also run the webservice using that information directly with wsnavigator on that WebAS.
    Checking the request message I found out that the root problem is that the adapter is not sending out a basic authentication request as configured. It is actually sending a header with SAP SSO2 (single signon) ticket instead.
    The most strange thing is that I configured another channel exactly the same way and it sends a basic authentication header as it should and works correctly.
    So as a workaround I am using this new channel instead of the problematic one but why is the original sending SSO2 tickets? It is configured exactly the same as other channels. I think that SAP SSO authentication is not even supported by XI SOAP channels!!!???
    Thanks in advance for your kind responses.
    -Sam.

    Shabarish:
    Thanks for the link, but the real issue is not the request message (regarding your blog) but that the reply from the webservice is the standard HTML page informing no login module succeeded because the adapter is deciding completely on its own that it should use SAP single signon ticket instead of basic authentication as configured.
    Volker:
    I have performed full and delta cache refreshes to see if the channel performs as configured in the ID but it doesn't. It insists in trying to use SSO2 ticket instead of basic authentication.
    I am sure this is an ugly bug in the WEBAS Java, more so because an identically configured channel does use the basic authentication as it should. Anyone knows about a SAP note regarding this? I have performed many searches on the support service but haven't retrieved anything significant.
    Thanks for your help guys!
    -Sam.

  • Time out error in receiver soap adapter

    Hi,
    My scenario is file to soap file with out BPM.I am using a currency converter wsdl.
    I am getting a time out error in soap receiver channel.
    Do i need to change the time out parameter?Where do i change that?Please help me to solve it out.
    Following are the errors in the soap communication channel.
    SOAP: call failed: java.net.ConnectException: Connection timed out
    SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out
    MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out
    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 timed out: java.net.ConnectException: Connection timed out. Setting message to status failed.
    Regards
    Divia

    Hi Prateek,
    Thanks for your replay. I am able to open the URL from XI/PI.
    I tried by testing the same URL by using XI 3.0, its working fine and i am getting required data, but in PI 7.1 i am getting an error.
    Error is:
    In MONI:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect
    In RWB:
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect
    What could be the reason?
    Regards,
    Venu

  • Error in Receiver SOAP AXIS adapter.

    I have configured a receiver soap adapter and get the below error. Any help with this? Since I am able to see the Axis option in the adapter configuration, this means the axis framework is deployed or does it need to be delpoyed?
    Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.TransactionRolledbackLocalException:
    (Failed in component: sap.com/com.sap.aii.axis.app, BC-XI-CON-AFW-TAD) Exception raised from invocation of public
    com.sap.aii.af.lib.mp.module.ModuleData com.sap.aii.adapter.axis.modules.AFAdapterBean.process
    (com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws
    com.sap.aii.af.lib.mp.module.ModuleException method on bean instance
    com.sap.aii.adapter.axis.modules.AFAdapterBean@681b240 for bean

    Had to deploy the axis framework.

  • SOAP Axis - Could not initialize class OperationDesc error in Receiver SOAP

    Hi,
    We are facing a issue in receiver soap scenario with NTLM Authentication.
    We have deployed the necessary jar files needed for Axis framework. But we are geting an error 'Could not initialize class org.apache.axis.description.OperationDesc'.
    Any idea how to overcome this error?
    Edited by: Aarthi on Apr 27, 2010 8:29 AM

    Yes. I checked.
    In addition to the mandatory files, we have deployed the below 3 files for NTLM.
    Jakarta-Commons Codec
    Found: org.apache.commons.codec.Encoder at D:\usr\sap\DGX\DVEBMGS00\j2ee\cluster\bin\ext\com.sap.aii.af.axisproviderlib\lib\commons-codec-1.3.jar
    Jakarta-Commons Net
    Found: org.apache.commons.net.SocketFactory at D:\usr\sap\DGX\DVEBMGS00\j2ee\cluster\bin\ext\com.sap.aii.af.axisproviderlib\lib\commons-net-1.0.0-dev.jar
    Jakarta-Commons HttpClient
    Found: org.apache.commons.codec.Encoder at D:\usr\sap\DGX\DVEBMGS00\j2ee\cluster\bin\ext\com.sap.aii.af.axisproviderlib\lib\commons-codec-1.3.jar

  • Error in Receiver Soap Adapter for Google API

    Hi,
    I am working on HTTP-XI-Soap scenario which on the receiver side calls google API for spell check.
    I get the following error : <b>No Deserializer found to deserialize a ':key' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.</b>
    However if I try calling the webservice individually using SOAP Client it works fine and do get desired response.The soap message that is sent by the client to the target URL is :
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:GoogleSearch" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <soapenv:Body>
          <urn:doSpellingSuggestion soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
             <key xsi:type="xsd:string">qXWD4x1QFHIo/dePqlYOLwT7kMmkv80E</key>
             <phrase <b>xsi:type="xsd:string"</b>>Bratney</phrase>
          </urn:doSpellingSuggestion>
       </soapenv:Body>
    </soapenv:Envelope>
    However if i remove the "xsi:type="xsd:string" part from the element 'phrase' and 'key' it returns the same error as it does while using with XI.
    Hence I am assuming that that the outgoing soap message elements need to have the above highlighed attribute.
    Now I want to have this attribute(xsi:type="xsd:string) in the soap message that is sent from XI.
    My question is , Is there any setting using which I can add the attributes in the above form to the outgoing message from XI.I do not want to use a adapter Module.
    Thanks & Regards,
    Sidharth

    Hi Sidharth,
    You post here the soap message that is sent by the client to the target URL, but did you look to the soap message that is sent by XI?
    Try the AF monitor http://<host>:<j2ee-port>//MessagingSystem/monitor/monitor.jsp?
    Because XI soap adapter doesn't support all tags of wsdl rpc-based, we need to adjust them...
    Look to the SOAP FAQ (SAP note number 856597) under question "Can I convert an RPC styled WSDL to a document styled WSDL?"... Look at last but one paragraph ;o)
    So, you need to change this attribute to one that it is compatible...
    Go to http://service.sap.com/xi > Media Library > Documentation and there you will find this xls document -> SAP XI 3.0 (SP11) - Supported XML Schema and WSDL (EN) in this document you have all the compatible elements of wsdl for XI.
    One more thing, you can adjust your soap request and change or add the required tags You can do it with xslt-mapping or create your won data types in XI without import the WSDL generated by google. 
    Hope it helps,
    Ricardo.
    Message was edited by: Ricardo  Quintino

  • Error in Receiver SOAP adapter - but ok in sxmb_moni

    HI,
    i am trying to call a WS wich takes only input. so it is a asynchronous call.
    I configured CRM-XI-WS.
    My sxmb_moni is ok in XI. But when i check Adapter monitoring it is throwing the following error...  any help please..
    2008-01-03 16:55:53 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: 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, 179). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type.
    2008-01-03 16:55:53 Error Exception caught by adapter framework: 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, 179). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type.
    2008-01-03 16:55:53 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: 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, 179). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type..
    2008-01-03 16:55:53 Success The asynchronous message was successfully scheduled to be delivered at Thu Jan 03 17:00:53 CST 2008.

    I changed my structure to a smiple structure... still i am getting the error...
    even i tried taking the payload from sxmb_moni and tested the mapping in IR .. it is failing... saying: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    my payload is :
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:HSBP_Out_MT xmlns:ns0="http://tsfco:A_TSFCO_CRM_WS_COMM_SWC:CD:HsBpFromCrm">
      <Name>test</Name>
      </ns0:HSBP_Out_MT>
    Edited by: ashok sri on Jan 4, 2008 1:14 AM

  • Unable to open PWA in browser and MSP on application server in project server 2007. ERROR: Sending the Soap message failed or no recognizable response was received.

    Hi All,
    I am using project server 2007 and WSS 3.0. 
    I have been facing a strange issue for couple of days. I am unable to open PWA in browser and MS Project Pro on application server.
    Everything is correct whether it is URL or MS Project profile account on MSP.  This is strange because i can open same PWA/MSP from other computers (Database server / Client PCs) but not locally on server.
    When i try to connect to MSP on App server, i get the following errors in event viewer.
    Event Type: Error
    Event Source: MSSOAP
    Event ID: 16
    User: N/A
    Computer: APP-Server-Name
    Description:
    Soap error: Connection time out..
    Event Type: Error
    Event Source: MSSOAP
    Event Category: Client 
    Event ID: 16
    User: N/A
    Computer: APP-Server-Name
    Description:
    Soap error: An unanticipated error occurred during the processing of this request..
    Event Type: Error
    Event Source: MSSOAP
    Event Category: Client 
    Event ID: 16
    User: N/A
    Computer: APP-Server-Name
    Description: Soap error: Sending the Soap message failed or no recognizable response was received.
    Event Type: Error
    Event Source: MSSOAP
    Event Category: Client 
    Event ID: 16
    User: N/A
    Computer: APP-Server-Name
    Description:
    Soap error: Unspecified client error..
    One more issue i am facing and i guess that is related to above issue. The Issue is, when i am creating a new project, It's workspace gets created but doesn't get linked to the project and i can't link it manually because it already exists for the project.
    sandeep

    Hi Paul ,
    Thanks for reply. The project server URL was already added to the Trusted
    Sites/Local Intranet areas in IE. 
    sandeep

  • "Error while parsing SOAP XML payload: no element found" received when invoking Web Service

    Running PB 12.1 Build 7000.  Using Easysoap.  Error ""Error while parsing SOAP XML payload: no element found" received when invoking Web Service".  This error does not appear to be coming from the application code.  Noticed that there were some erroneous characters showing up within the header portion of the XML ("&Quot;").  Not sure where these are coming from.  When I do a find within the PB code for ""&quot;" it gets located within two objects, whereas they both reference a "temp_xml_letter".  Not sure where or what temp_xml_letter resides???   The developer of this is no longer with us and my exposure to WSDL and Web Services is rather limited.  Need to get this resolved...please.
    This is the result of the search.  Notice the extraneous characters ("&quot;"):
    dar1main.pbl(d_as400_mq_xml)
    darlettr.pbl(d_email_xml)
    ---------- Search: Searching Target darwin for 'temp_xml'    (9:52:41 AM)
    ---------- 2 Matches Found On "temp_xml":
    dar1main.pbl(d_as400_mq_xml).d_as400_mq_xml:  export.xml(usetemplate="temp_xml_letter" headgroups="1" includewhitespace="0" metadatatype=0 savemetadata=0  template=(comment="" encoding="UTF-8" name="temp_xml_letter" xml="<?xml version=~"1.0~" encoding=~"UTF-16LE~" standalone=~"yes~"?><EmailServiceTransaction xmlns=~"http://xml.xxnamespace.com/Utility/Email/EmailService" ~" xmlns:imc=~"http://xml.xxnamespace.com/IMC~" xmlns:xsi=~"http://www.w3.org/2001/XMLSchema-instance~" xmlns:root=~"http://xml.xxnamespace.com/RootTypes~" xmlns:email=~"http://xml.xxnamespace.com/Utility/Email~" xsi:schemaLocation=~"http://xml.xxnamespace.com/Utility/Email/EmailService http://dev.xxnamespace.com/Utility/Email/EmailService/V10-TRX-EmailService.xsd~"><EmailServiceInformation><EmailServiceDetail __pbband=~"detail~"><ApplicationIdentifier> applicationidentifier </ApplicationIdentifier><AddresseeInformation><AddresseeDetail><Number> number </Number></AddresseeDetail></AddresseeInformation><EmailMessageInformation><Ema
    darlettr.pbl(d_email_xml).d_email_xml:  export.xml(usetemplate="temp_xml_letter" headgroups="1" includewhitespace="0" metadatatype=0 savemetadata=0  template=(comment="" encoding="UTF-8" name="temp_xml_letter" xml="<?xml version=~"1.0~" encoding=~"UTF-16LE~" standalone=~"yes~"?><EmailServiceTransaction xmlns=~"http://xml.xxnamespace.com/Utility/Email/EmailService" ~" xmlns:imc=~"http://xml.xxnamespace.com/IMC~" xmlns:xsi=~"http://www.w3.org/2001/XMLSchema-instance~" xmlns:root=~"http://xml.xxnamespace.com/RootTypes~" xmlns:email=~"http://xml.xxnamespace.com/Utility/Email~" xsi:schemaLocation=~"http://xml.xxnamespace.com/Utility/Email/EmailService http://dev.xxnamespace.com/Utility/Email/EmailService/V10-TRX-EmailService.xsd~"><EmailServiceInformation><EmailServiceDetail __pbband=~"detail~"><ApplicationIdentifier> applicationidentifier </ApplicationIdentifier><AddresseeInformation><AddresseeDetail><Number> imcnumber </Number></AddresseeDetail></AddresseeInformation><EmailMessageInformation><Ema
    ---------- Done 2 Matches Found On "temp_xml":
    ---------- Finished Searching Target darwin for 'temp_xml'    (9:52:41 AM)

    Maybe "extraneous" is an incorrect term.  Apparantly, based upon the writeup within Wiki, the parser I am using does not interpret the "&quot;"?  How do I find which parser is being utilized and how to control it?
    <<<
    If the document is read by an XML parser that does not or cannot read external entities, then only the five built-in XML character entities (see above) can safely be used, although other entities may be used if they are declared in the internal DTD subset.
    If the document is read by an XML parser that does read external entities, then the five built-in XML character entities can safely be used. The other 248 HTML character entities can be used as long as the XHTML DTD is accessible to the parser at the time the document is read. Other entities may also be used if they are declared in the internal DTD subset.
    >>>

  • Receiver SOAP Adapter error

    Hi All,
             I am getting this response error message in my receiver SOAP Adapter while invoking a synchronous webservice.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Request Message Mapping
      -->
    - <ProcessMessageResponse xmlns="http://Sleek.Integrator.Messaging" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <ProcessMessageResult>Value cannot be null. Parameter name: Request string is a null reference.</ProcessMessageResult>
      </ProcessMessageResponse>
    Thx in advance
    Ravijeet

    Hi All,
             I am still getting the same error value is null. I am not able to track what could be the cause of the error. If I am taking the message from SXMB_MONI and using it in a client tool it is successfully calling the webservice.
    Do we need to explicitly mention in some configuration that content type is soap/xml. SOAP header is omitting the content type or is not specifying "soap/xml" as the content type.
    I am interacting with a WAF websevice, is there any compatibilty issue with Windows Webservice and SAP XI?
    Also what should I pick as the SOAP Action from this wsdl file definition
    <wsdl:portType name="IMessageProcessor">
              <wsdl:operation name="ProcessMessage">
                   <wsdl:input message="tns:IMessageProcessor_ProcessMessage_InputMessage" wsaw:Action="XXX.Messaging/ProcessMessage"/>
                   <wsdl:output message="tns:IMessageProcessor_ProcessMessage_OutputMessage" wsaw:Action="XXX.Messaging/ProcessMessageResponse"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:service name="MessageProcessor">
              <wsdl:port name="BasicHttpBinding_IMessageProcessor" binding="i0:BasicHttpBinding_IMessageProcessor">
                   <soap:address location="http://XXX.com/cardax/provisioningservice"/>
              </wsdl:port>
    Thx in advance
    Ravijeet

  • Error in the Receiver SOAP Adapter

    Hello Experts,
           I am sending an order number by running a report on the ECC 6.0 server to a web service for publishing the information on the web site. The receiver side is configured as Receiver SOAP Adapter . I am getting the following error in the SXMB_MONI Transaction.
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation.
    Kindly let me know to overcome this problem.
    Thanks
    Best Regards
    S Joshi

    Hi Ramesh,
        The message Iam getting in MONI is as follows:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation.
    This is the response for the request that i am sending for order creation. I did checked the fields also it is same and the values of the fields too. they all are correct. Over and above this it was working fine till last week , but suddendly this week I am getting this error.
    Regards

  • Error in applying security settings in Receiver SOAP Adapter

    Hi,
    I've used Web Services Security (Oasis standard) and the digital signature and encryption certificate in receiver SOAP adapter and the corresponding Sender Agreement, for adding digital signature and encrypting the message. While sending the message we are getting an error in the adapter engine as below. If anyone can throw light on this it'll be highly appreciated :
    2008-07-18 17:00:21 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: SAXException in Method: run().. To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: SAXException in Method: run()..
    2008-07-18 17:00:21 Error Exception caught by adapter framework: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii
    2008-07-18 17:00:21 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: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXExce.
    Thanks,
    Dipankar

    hi dipanker,
    check the note 856597
    its usefull
    regards
    kummari

  • Error in Adapter engine of receiver soap adapter

    Hi All,
    There is one production issue i am currently facing in receiver SOAP adapter while interacting with third party web service(Asynchronous call).
    Below is the description i am getting in audit logs.
    Success SOAP: completed the processing
    Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
    Success SOAP: sending a delivery error ack ...
    Success SOAP: sent a delivery error ack
    Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
    Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
    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: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired.
    Error The message status set to NDLV.
    Moreover this is a production issue and  interface was running fine till last friday.
    Has someone ever faced this issue ?
    Please provide your valuable inputs on this.
    Thanks
    Anku

    Hi,
    Search in sdn with your error message string,you will find ton of links.
    HTTP401 error occurs for many reasons.
    still no solution let us know..
    Regards,
    Raj

Maybe you are looking for