SOAP Sender CC - Error Application:RESOURCE_NOT_FOUND

I am using a sender SOAP communication channel in XI 2.0;
When a message is posted to the URL, I get a exception as below as response.
<!see the documentation>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: Application:RESOURCE_NOT_FOUND:
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
     at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
I can see the messages received in the CC monitor - which says 'error occured' and there is no message ID attached to it.
In the SXMB_MONITOR - I can see the payload; Can anyone give a hint on what is wrong?

The requirement was to convert the SOAP message from the Sender Communication Channel to IDOC with this interface.
After all your helps, we have come a long way and
Now I get a error message at the 'CALL ADAPTER' in SXMB_MONI for my message.
At the 'Response' node of my message I get the following error information
- <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="IDOC_ADAPTER">ATTRIBUTE_BE_NOT_SUPP</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Only asynchronous processing supported for IDoc adapter outbound processg</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Any hints/ideas please.

Similar Messages

  • HTTPS SOAP Sender Adapter Error

    I have a SOAP client connecting to XI through HTTPS. SOAP Channel is configured to receive HTTPS request. We have been receiving messages successfully but the following error message occurs intermittently:
    Error text from the Adapter Engine: java.security.AccessControlException: https scheme required
    I don't see anything in SXMB_MONI. I don't see anything in RWB on the adapter message monitoring.
    This scenarios is synchronous.

    hi rodel,
    You need to configure the HTTPS security level.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
    regards
    Ramesh P

  • Question: Application error when using SOAP sender

    Hi,
    I got the following error when calling SOAP sender:
    - <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="UNKNOWN">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>application fault</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The return message is:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
      <ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">gdcn-admin</ns2:hostname>
    From the runtime monitor, it shows:
    SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
    Actually I maintained the host name in file hosts. And with XMLSpy, I can directly connect the Webservice successfully, but with XI, it stops me at this point. It seems the connection has been established, because if the WebService is stopped, I will get error HTTP 0 Null, If it's started, I get the above problem.
    Could you please provide the hints.
    Thanks a lot!
    Best Regards
    Yuedong

    Hi,
    I found the problem:
    It's because of the wrong format of message. the message is created with a WSDL file generated by external development system, but it's not correctly explained by XI. I manually created the messge (request & response), then it worked.
    Actually the error has nothing to do with hostname. it means the host returns application error (but unfortunately there is no detailed information).
    Thanks a lot for your kindly help!
    Best Regards
    Yuedong
    By the way, how can I reward the point?
    Message was edited by: Yuedong Chen

  • SOAP: response message contains an error Application/UNKNOWN/APPLICATION

    Hi,
    My scenario is Proxy>Soap>WS. When I tested proxy using SPROXY,the web service call is working fine and I am getting response. However, when I call proxy in the the program, I am getting "SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault" in adapter engine. I have gone through many similar posts in SDN but did not help.
    Thanks for your help.

    Thanks. I used SOAPUI outside SAP and it works perfectly fine. Even in SAP, it works fine when using Sproxy.  Here is the error from adapter engine:
    2010-06-24 12:59:34     Success     SOAP: continued from request message 6600174c-8a22-613e-e100-000018280c11
    2010-06-24 12:59:34     Error     SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
    2010-06-24 12:59:34     Success     SOAP: response message leaving the adapter
    2010-06-24 12:59:34     Success     MP: Leaving module processor
    2010-06-24 12:59:34     Success     Application attempting to send an XI message asynchronously using connection SOAP_http://sap.com/xi/XI/System.
    2010-06-24 12:59:34     Success     Trying to put the message into the send queue.
    2010-06-24 12:59:34     Success     The response message for message 6600174c-8a22-613e-e100-000018280c11(INBOUND) was successfully transmitted to the calling application.
    2010-06-24 12:59:34     Success     The message status set to DLVD.
    2010-06-24 12:59:34     Success     The application sent the message asynchronously using connection SOAP_http://sap.com/xi/XI/System. Returning to application.

  • Error while posting messages to SOAP sender adapter SP 13

    Hi Friends,
                    I have configured a SOAP sender adapter in XI 3.0 and is using the URL
    http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
    Message Servlet is in Status ERROR
    Status information:
    Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
    Classname ModuleProcessor: null
    Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
    Lookupname for remoteModuleProcessorLookupName: null
    ModuleProcessorClass not instantiated
    ModuleProcessorLocal not instantiated
    ModuleProcessorRemote not instantiated
    But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
    <?xml version="1.0" ?>
    <http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_EBTR_WEBSERVICE:CC_EBTR_WEBSERVICE_SOAP> <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
      <channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
      <name>CC_WEBSERVICE_SOAP</name>
      <type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
      <direction>INBOUND</direction>
      <party />
      <service>BS_WEBSERVICE</service>
      </s:ChannelInfo
    I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy we are getting a 500 internal server error.
    Am not sure what causes the error ? I saw two notes in SDN related to SOAP - J2EE SP13. We are in SP13. Is this the issue ? Wanted to know your opinion before applying the notes.
    Thanks & Regards,
    Mathew

    ABAP & Java stack was on different SP levels.

  • SOAP : response message contains an error Application/UNKNOWN/APPLICATION_E

    Hi All,
    I am working in a Proxy to SOAP synchronous scenario. Message is processing successfully through IE but i am getting the below error in receiver (SOAP) communication channel.
    SOAP : response message contains an error Application/UNKNOWN/APPLICATION_ERROR.
    Please suggest what will be possible way out to resolve this issue.
    Thanks,
    Priya Ranjan

    Dear Priya
    Have you configured Fault Message for this scenario.
    This kind of error is generally thrown by the end target system where the message is not processed succesfully due to some error in there system.
    Sourabh

  • SAP PI 7.1 SOAP sender 500 internal server error

    Hello!
    We would like to receive messages from our business partner. As the partner sends EDIFACT we have to use the conversion from EDIFACT-text to EDIFACT-xml. That's why we have to use SOAP instead of plain HTTP.
    As the partner already sent messages over X.400 we just added a SOAP communication channel and used this channel in the sender agreement instead of the X.400 communication channel.
    We sent the following link to the customer:
    http://<server>:<j2ee port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<SOAP sender communication channel>
    One question: is the <service> the communication component used for the partner?
    At the moment the partner receives a 500 error message. Due to our network partner the message reaches the PI system.
    Due to the information I found that also a message parsing error can cause a 500 error message I would like to add the processing sequence:
    Does anyone have an idea how to solve this problem?
    Thanks a lot!
    Regards
    Christian

    Hi Christian
    You can refer to the following SAP Library link on how to configure the SOAP sender.
    Configuring the Sender SOAP Adapter - Configuring the SOAP Adapter in the Integration Directory/PCK - SAP Library
    For the URL, the <service> is the Communication Component that the SOAP channel belongs to.
    Using the example below, the value would be P_B2B_:BC_:CC_S_SOAP_
    Actually SAP recommends a new alternative for the URL. If you scroll right to the end of the library link above.
    You have configured the sender SOAP adapter. You can trigger a call to the sender SOAP adapter using either of the following URLs. However, SAP recommends you to use the second option.
    http://hostname:portname/XISOAPAdapter/MessageServlet?channel=partyname:service name:channelnameIf you have not created a party, enter channel=servicename:channelname.
    http://hostname:port name/XISOAPAdapter/MessageServlet?senderParty=name of the sender party<&senderService>=name of the sender service<&interface>=name of the interface<&receiverParty>=name of the receiver party<&receiverService>=name of the receiver service<&interfaceNamespace>=name of the interface namespace
    You can get this by generating the WSDL from the Sender Agreement object (Sender Agreement -> Display WSDL). The generated URL will be at the last section of the WSDL.
    Also, please note that modules cannot be added to the SOAP sender adapter, also mentioned in the link.
    You cannot add your own modules to this adapter.
    An alternative would be to receive the EDIFACT Flat file as it is, and write it to at temporary File/FTP location. Then have a second channel pick it up, you can configure the second channel with module to convert it to EDIFACT XML.
    Lastly, regarding the issue about the partner getting HTTP 500 error. Please check if you are able to see any error logs in the communication channel. It might give you some pointers as to what might be wrong - invalid sender agreement, etc, etc.
    Rgds
    Eng Swee

  • HTTP Error 501 with SOAP Sender channel

    Hello,
    i've am simple Question:
    I want to call the following SAP XI SOAP Sender channel "MySoapSenderChannel":
    XI-Parameters:
    namespace: <myInterfaceNamespace>
    Interface:   <myAsynchInterface>
    QoS: Exactly Once in Order
    Queue: MY_QUEUE
    We do not care about the Response - so the processing is asynchron.
    Thus my interface mapping maps to asynch interfaces. The desitnation
    is an ABAP Proxy. The configuration has been done and tested.
    Here my question:
    according the documentation, the URL has the following syntax:
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel.
    In our case:
    http://<myHost>:8002/XISOAPAdapter/MessageServlet?channel=:MyService:MySoapSenderChannel.
    But when i generate a WSDL for the interface out of the Configuration, the address is:
    <soap:address location="http://<myHost>:8002/sap/xi/engine?type=entry&amp;version=3.0&amp;Sender.Service=MyService&amp;Interface=...
    and so forth.
    But was is the difference between these 2 possibilities?
    Why do i get HTTP Error 501 when i use the URL from the documentation (the first one)?
    Thanx in advance
    Gunnar

    Gunnar,
    I will suggest you to go through it once to check all your connection.
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    Regards,
    Sarvesh

  • Error in SOAP sender CC. Channel stopped by administrative task.

    I am getting an error in my SOAP sender communication chanel as follows;
    com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Channel stopped by administrative task.
    The channel is Active but still gets the same error. Any help would be appriciated.

    RWB ---> Component Monitoring ---> Adapter Engine ---> Communication Channel Monitoring ---> Choose your CC and check its properties....check if it shows Channel Stopped...if yes then restart it.
    Channel should be Active in ID and Started in RWB to work properly.
    Regards,
    Abhishek.

  • SOAP Sender Error - com.sap.engine.interfaces.messaging.api.exception

    Hi,
    I am testing a SOAP Sender Channel using a SOAP Client and getting the following error. I have read almost all the posts related to errors in SOAP Channel and also have checked my URL which is correct. AS mentioned in many of the posts, my url goes like
    https://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST&version=3.0&SenderService=DEMO&interface=si_os_GETLIST&interfaceNamespace=<namespace>
    This is the error that I get when sending a message to the interface
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
    <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
         at sun.reflect.GeneratedMethodAccessor1044_10001.invoke(Unknown Source)*
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    Has Anybody got this problem before? Is it any problem with the SOAP Adapter itself or with the data that is going in the message? If so, What is the possible solution for this?
    Thanks,
    Rashmi.

    Hi Rashmi,
    I also think your problem is data related.
    Check the response in your SAP PI message monitor (SXMB_MONI) when you trigger a request using SoapUI. It sometimes provides a bit more detail. You design (data types, message types, service interfaces etc.) was done in SAP PI 7 then an Abap Proxy was generated from the service interface?
    Sometimes there is an issue between the XSD data type declaration in SAP PI and the conversion to Abap data types that takes place when a proxy is generated from a PI Service Interface.
    Check the data that you pass in your request, especially those like datetime fields. Maybe even change some of the data type definitions (like datetime) to a string (request & response) & then test through SoapUI & see if you still get the error. Then you can work out how to best resolve it.
    Best Regards, Trevor

  • SOAP Sender with additional header: Interface determination error

    Hello Experts,
    I need to implement a scenario where in sender will add custom header fields and in PI, the values needs to captured. Second step: Based on the custom header value, the receiver needs to be determined.
    Scenario: SOAP Sender -> PI -> SOAP Receiver
    Request Message:
    <RequestMsg>
         <request>
              <Field 1>...</Field 1>
              <Field 2>...</Field 2>
              <Field 3>...</Field 3>
         </request>
    </RequestMsg>
    Without any custom SOAP header, I have created Request / Response Message, Message Mapping, Service Interfaces (Inbound & Outbound) and Operation Mapping and tested the scenario by triggering call through SOAP UI, it works fine. SOAP Request XML looks like below:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:v1="http://www.test.abc.com/v1">
        <soapenv:Header />
        <soapenv:Body>
          <v1:RequestMsg>
             <request>
                  <Field 1>1</Field 1> 
                   <Field 2>2</Field 2>
                   <Field 3>3</Field 3>
             </request>
          </v1:RequestMsg>
       </soapenv:Body>
    </soapenv:Envelope>
    To use customer fields in SOAP Header, I have checked the option "Do Not Use SOAP Envelope" in the SOAP Sender CC and added "&nosoap=true" to url. SOAP Request XML looks like below:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:v1="http://www.test.abc.com/v1">
        <soapenv:Header >
              <id>REC1</id>
         </soapenv:Header >
        <soapenv:Body>
          <v1:RequestMsg>
             <request>
                  <Field 1>1</Field 1> 
                   <Field 2>2</Field 2>
                   <Field 3>3</Field 3>
             </request>
          </v1:RequestMsg>
       </soapenv:Body>
    </soapenv:Envelope>
    Now, when I invoke the url, I see that the message reaches PI but it throws error: RoutingException: InterfaceDetermination did not yield any actual interface
    Please note that I have added a Java Mapping before main message mapping to read the soap header and pass only the request message to the next message mapping.
    I am sure, I am missing important steps in the configuration. Please help me in reolving the issue.
    Thanks & Regards,
    Ankit Srivastava

    Hello Hareesh,
    Bingo! The second option suggested by Nicolas worked like a charm. I am just copying the same here:
    -----In ESR, you set the attribute "Interface Pattern" of the outbound service interface as "Stateless (XI30-compatible)", which does not use operations.----
    Thanks a lot. Now, I will be able to concentrate on the next steps.
    Regards,
    Ankit Srivastava

  • "NO_RECEIVER_CASE_BE" error with SOAP Sender assigned to a Business Service

    Hi all,
    we have a strange error with XI3.0
    We created a configuration scenario where the initial step is done by a Business System, that uses a SOAP Sender communication channel to send its request. And this works great when testing it with XMLSpy.
    But we then needed to shift from a Business System to a Business Service, as the machine sending the SOAP request changed and was not anymore part of the landscape, but elsewhere.
    Hence we recreated a SOAP sender which we assigned to this new business service, doing absolutely the same configuration work as for the other soap sender of the former business system.
    Yet when testing it through XMLSpy, we everytime get a NO_RECEIVER_CASE_BE error back, stating that "No receiver could be determined". Yet when checking in sxi_cache, receiver determination is clearly there. All the blogs I went into are only refering to Business System for a SOAP sender, so I was wondering if any of you already managed to assign a SOAP sender to a business Service.
    Regards,
    Cedric

    hi,
    so you sue SOAP to make a query ? (sync)
    or to send the data to XI ? (async)?
    if async then make sure
    you use <b>Quality of Service</b> other then BE
    in your soap adapter channel
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Error in SOAP sender scenario

    Hi All,
       I am getting the following error when i execute a sender SOAP scenario from XMP Spy.
      Scenario : SOAP --> XI --> RFC
    I am getting the following error when i try to send request from XML Spy.
    Error in XMl Spy:
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
                   <text>com.sap.aii.af.mp.module.ModuleException: *adapter inactive*
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:703)
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3.process(ModuleLocalLocalObjectImpl0_3.java:103)
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
         at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
         at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:174)
         at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:436)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         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)</text>
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    When i go to RWB-- > communication channel monitoring i see the channel status as "Started but Inactive" and when i go to Cluster node tab--> Cluster Node Details for Channel Unifier i see the following two entries every single time i try to send a message
      14/10/10 05:35:10   error occured
      14/10/10 05:35:10   request received
    Please help to figure out what could be wrong.

    open the SOAP Sender channel in Integration directory and change the status to active and then activate. Try resending SOAP message from XML spy

  • Error with Soap sender channel

    I have a scenario SOAP->Proxy ..whenever I send a message through SOAP its giving error as below:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection SOAP_http://sap.com/xi/XI/System is currently not started.
    Please help me in rectifying this...

    Kiran,
    strange thing is that when we remove the standard module from the channel then its workign fine..
    Well, you can try couple of things more -
    1. Re-start the java engine.
    2. If step 1 doesn't work, delete the channel -> activate the change list -> create a new channel and try again.
    I feel that after step 1, it should work. Let us know how it goes.
    Regards,
    Neetesh

  • SOAP Sender Adapter gets error '(401) Unauthorized.'

    Hi all,
    we are using XI 3.0 and have a scenario with a SOAP Sender Adapter, which is using "HTTPS with Client Authentication". I have configured everything I have found on the forum at Visual Admin and Integration Directory:
    Set the UME property ume.logon.allow_cert to TRUE in 'Service-->UME Provider'
    Imported client certificate and root CA certificate to 'Service-->Keystore'
    Created user with role role SAP_XI_APPL_SERV_USER
    Assigned this user to the client certificate in 'Security Provider-->UserManagement'
    Added the user to xi_adapter_soap_message and xi_adapter_soap_help in 'Security Provider'
    Added the root CA in 'SSL Provider>Dispatcher>Client Authentication' and marked 'Request client certificate.
    Added the user to BusinessSystem at tab 'Assigned Users'
    Added the user to Sender Agreement at tab 'Assigned Users'.
    Our business partner got a certificate of our server and the according PrivateKey is added to 'SSL Provider>Dispatcher>Server Identity'
    Unfortunately, our server certificate is not verified by an root CA!!
    When the business partner now browse the URL 'https://url:port/XISOAPAdapter/MessageServlet?channel=:BS_3RD_PARTNER:SOAP_SENDER&nosoap=true' on his system, he will get a 'Message Servlet is in Status OK'.
    But when he tries to process the URL directly in his messaging system, he gets an error '(401) Unauthorized.' 
    Any hints what could be the problem between browing the URL in InternetExplorer and sending from the messaging system?
    Does it really mean that authorization was successful, when getting  'Message Servlet is in Status OK' in the Browser?
    How can I assign an user when not using ClientAuthentication?
    I would be very thankful for every help...
    Grtz, Juergen

    Hi Satish,
    could the user or password also be wrong, even if you get 'Message Servlet is in Status OK' when browsing the URL in the Internet Explorer? I would have seen this as a sign, that the user authentication works basically...
    Is there a special place to store the password in the Visual Admin, or will the password be used, which is available in the SU01 ?
    Grtz,
    Juergen

Maybe you are looking for