Error in outbound proxy

I am getting the following error and am not sure what is causing it. can anyone point me in the right direction?
Thanks
Mike
<b>- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIProxy</SAP:Category>
  <SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
  <SAP:P1>ifmmessif</SAP:P1>
  <SAP:P2>MI_SapDownload_Sync_OB</SAP:P2>
  <SAP:P3>urn:igt-com:appl:license:fno</SAP:P3>
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>No implementing class registered for the interface (type ifmmessif, name MI_SapDownload_Sync_OB, namespace urn:igt-com:appl:license:fno )</SAP:Stack>
</b>

hi,
>>>>We have not changed the message interface.
then everything should be ok
but since I'm not a believer - try to generate the
class once more in SPROXY ok ?:)
Regards,
michal

Similar Messages

  • SPROXY error testing outbound proxy interface

    Hi,
    I am trying to test an outbound proxy interface using SPROXY but am getting the following error:
    Apart from the above messages there is no more help available. When I try testing the generated XSLT program using SXSLT_TEST it gives an error "No valid XSLT program supplied". I have checked and the auto generated XSLT program does exist.
    Any help appreciated.
    Thanks
    Che

    Hi Che Eky,
    Check out below helpful thread & doc:
    SERIALIZE_APPLICATION_DATA Conversion error ABAP => XML: Request Message
    Serialization issue in abap proxy
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a89312f8-0b01-0010-86b3-fdd7178e0534?QuickLink=index&…
    Regards,
    Krupa

  • Interface Registration Error in Outbound Proxy

    Hello Gents,
    I created outbound synchronous proxy scenario where i am passing two fields "sales order no" & "Description". But when I executed this it is giving strange error like
    "   <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Inbound Proxy
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
      <SAP:P1>ifmmessif</SAP:P1>
      <SAP:P2>mios_sec_md_request</SAP:P2>
      <SAP:P3>http://se.com.sa/sec-sa_interfaces</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No implementing class registered for the interface (ABAP interface, request message mios_sec_md_request, request message, namespace http://se.com.sa/sec-sa_interfaces)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>"
    I tried out deleting the proxy & recreated. Also, Message interface is sync with the integration repository.
    Please help me to solve the issue.
    Thanks in advance.
    Regards,
    Santhosh

    can you confirm this;
    In SXMB_ADM -> Execute Integration Engine then,
    edit -> Change Global configuration data
    Role of Business System should be Integration Server
    Is that setting correct? At times it might have been set as Application server, which can cause this error.

  • Outbound Proxy is generating Mapping Transformation XSLT error in SPROXY Test

    Hi,
    I have searched already online but i am unable to find anything relevant.
    The scenario is that I have an Inbound proxy for processing the incoming payload and in this code the call is made to the oubound proxy method and i am gettin the MAPPING.TRANSFORMER_EXCEPTION Exception occurred during XSLT mapping of the application
    CALL METHOD outbound_obj->shipment_status_notification_o
    EXPORTING
    output = wa_orders_request_out
    IMPORTING
    input = wa_orders_response_out.
    We just updated the orders_request_out  with a single field and activated and regnerated the proxy in ECC and i can now see the updated structure.
    However, if i take the payload from production and just pass the payload in debug to the above method call  in both Dev and QA with the added field, I am getting the above error.
    I cannot do the proxy debug in production unfortunately so i cannot see if this is happening only in Dev and QA.
    Can anyone please help me as this is urgent and If i can get past this error  i can actually test if processing is working as expected?
    Regards,
    Archana

    Hi Mark,
    I have checked the data type and the field occurrence is 0.1
    The change was made only to the request structure as based on this field value some selection needs to be made. The Response structure was not changed at all.
    I have regenerated the outbound proxy as well and surprisingly even though it was not modified it still did not give me a message that the proxy object has not changed. I had to activate it as changed to inactive.
    I am also not sure why that happened.
    Regards,
    Archana

  • Outbound Proxy error when triggering from SPROXY

    Hi Everyone,
    I was working on outbound proxy from ECC to PI. I have generated the proxy and activated. When I am trying to test the proxy manually from SPROXY the message is not getting triggered to SXMB_MONI in ECC itself. But I didn't get any error message as well. When I am executing the proxy from SPROXY I was getting below message in the status bar. So can anyone help me with the possible solution why the message is not getting triggered.
    Below is the options I have selected while executing the proxy.
    This was the status message which was giving after execution of proxy from SPROXY. The same status was giving for all the Proxy interface which ever is executing from SPROXY.
    Regards,
    Kankipati.

    Hi Kankipati
    can you please try Commit work  by navigating on test proxy screen .
    Extra- Trigger Commit work .
    Follow the below link .
    SAP PI Reference: SAP PI ABAP Proxy Outbound settings, Triggering message to SAP PI(When many sap pi systems)
    Best Regards
    Srinivas

  • Error while triggering Synchrous outbound proxy

    Hi,
    While triggering synchronous outbound proxy from a abap program,it is throwing an system fault message. the system fault message is "Application Integration system error".
    Please help me how to avoid this error.
    My code is as below.
      TRY.
        CALL METHOD proxy=>execute_synchronous
          EXPORTING
            output     = op_message
          IMPORTING
            input      = ip_message.
        CATCH cx_ai_system_fault into LO_SYS_EXCEPTION.
          CALL METHOD LO_SYS_EXCEPTION->IF_MESSAGE~GET_TEXT
            RECEIVING
              RESULT = TECHNICAL_EXCP_MESSAGE.
        CATCH cx_ai_application_fault .
      ENDTRY.

    Hi Ashwini,
    Quite possible, there is something missing in the partner profile. There are several threads already in SCN with the same problem. Please refer below and see if it is helpful:
    http://scn.sap.com/thread/319852
    Entry in outbound table not found: Error Status... | SCN
    Idoc Error Status "Entry in outbound table not found "
    Regards,
    Abhishek

  • ABAP Outbound Proxy: some messages stuck in CRM system

    Hi all,
    we've a strange issue with a ABAP Outbound proxy we've generated in our CRM 5.0 system (asynchronous interface).
    Sometimes messages stuck in the CRM system. They are in status 'Scheduled' (green flag) in SXMB_MONI in the CRM system. When I have a look at the corresponding queue, there's no message within. Status in SMQ1 and SMQ2 is fine, too. All queues are registered. When I reprocess such a message manually in SXMB_MONI in CRM with the restart button, they're sent fine to XI.
    Please note: it's NOT a general issue with that outbound proxy. In most cases the messages are sent immediately, just in some cases the messages stuck and I don't know why.
    Is it possible to restart such messages automatically? I just know the report RSXMB_RESTART_MESSAGES, but that one just restarts messages in Error status. But the ones we have aren't in error status so they cannot be selected with that report.
    Any idea where could be the problem / we should check?
    BR
    Holger

    On which SP r u working correctly. May be an SP upgrade could help.
    Regards,
    Prateek

  • Sync Async using proxies ( Calling Outbound proxy from Inbound proxy )

    I'm trying to generate Asynchronous Outbound message from the Synchronous Inbound message message  due to a requirement. My question is : is it really possible to develop such a scenario?. I'm getting weird error such as Kernal exception etc. Please let me know if you have developed such scenario and what should we do dfifferently in such scenarios?. Thank you for any suggestions.

    Hi,
    This error has has nothing to do with Calling Outbound Proxy from from Inbound Proxy. The scenario which you are telling is very much possible.
    It looks like there is some problem in your proxy code while calling RFC from within there or something like that. Try catching the exception and see what is the exact error or put in debug mode and see the step where exactly your code is failing.
    Use the following links for Catching Exception in Proxy
    Inbound ABAP Proxy Trace and error handling
    Handling Exceptions
    ABAP Server Proxies - Fault Handling
    Exception handling in integration processes
    ABAP Proxy and fault messages
    /people/bhanu.thirumala/blog/2006/02/07/abap-proxy--xml-to-abap-transformation
    Thanks
    Amit
    Reward point if answer is helpful

  • Outbound Proxy is triggered from CRM 4.0,  tag is missing in the payload

    Hi,
    A Outbound Proxy is triggered from CRM 4.0, one of the tag is missing in the payload. I had checked the SXMB_MONI in CRM and in XI as well both seems to miss that. I checked the BADI which triggers this PROXY the data is rightly populated to the PROXY method. Also, this problem is not occuring regularly but few times it misses the same tag. The occurrance defined in the datatype is 0 to 1. Can anyone help why this is happening..
    Many Thanks..

    This could rather be a logical error. May be the logic is not populating the XML tag on those occassions. I would suggest to debug in that direction.
    VJ

  • EJB - inbound and outbound proxy

    I have implemented inbound and outbound proxy to transfer file. In proxyFTPClientREQIB method of ProxyFTPClientREQIB_PortTypeImpl class I want to invoke outbound proxy that sends structure to XI. I have a problem with context, because after invoking outbound proxy method from inbound proxy there is an incorrect context (concatenation of EJB inbound context and EJB outbound context: ejbContexts/bcc.com.pl/MonaApp/bcc.com.pl/MonaApp/ProxyFTPClientREQIB_PortTypeBean and localejbs/bcc.com.pl/MonaApp/ProxyFTPClientRESOB_PortTypeBean)
    Context ctx = new InitialContext();
    proxyFTPClientRESOB_PortTypeLocalHome = ProxyFTPClientRESOB_PortTypeLocalHome) ctx.lookup("localejbs/bcc.com.pl/MonaApp/ProxyFTPClientRESOB_PortTypeBean");
    proxyFTPClientRESOB_PortTypeLocal = proxyFTPClientRESOB_PortTypeLocalHome.create();
    Error:
    Path to object does not exist at localejbs, the whole lookup name is ejbContexts/bcc.com.pl/MonaApp/bcc.com.pl/MonaApp/ProxyFTPClientREQIB_PortTypeBean/localejbs/bcc.com.pl/MonaApp/ProxyFTPClientRESOB_PortTypeBean.
    What should I do to avoid concatenation of contexts?

    Hi Julia,
    the correct call is:
    ... ctx.lookup("java:comp/env/ejb/ProxyFTPClientRESOB_PortTypeBean");
    The Reference to the JNDI name is done in the ejb-jar.xml:
    <ejb-local-ref>
      <ejb-ref-name>ejb/ProxyFTPClientRESOB_PortTypeBean</ejb-ref-name>
      <ejb-ref-type>Session</ejb-ref-type>
      <local-home>YourLocalHomeInterface</local-home>
      <local>YourLocalInterface</local>
      <ejb-link>ProxyFTPClientRESOB_PortTypeBean</ejb-link>
      </ejb-local-ref>
    Hope that helps,
    Stefan

  • Outbound proxy in Inbound proxy

    Hi Experts,
       I am doing two way interface. JDBC asyn - proxy-JDBC asyn
    I am calling outbound proxy in inbound proxy here.
    While i am calling it is giving HTTP connection error.
    So can i call outbound proxy in inbound proxy ????
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>

    Outbound proxy inside inbound proxy scenario usually works fine. But few suggestions,
    1. Check if the message is failing in request side of asynchronous scenario. If this is the case then I think the error which you are getting is probably due to improper channel configuration.
    2. If problem is not the one mentioned in point 1 above then, test the proxy in transaction SPROXY of ECC as to whether outbound proxy is called while inbound proxy is executed manually in transaction SPROXY . Once you execute the inbound proxy then go to transaction "SXMB_MONI" of ECC to check whether a message which outbound proxy is required to send to PI appears over there, if it appears there that means there is no issue on programming of proxy.
    Hope it might help in finding resolution.
    Thanks,
    Amit

  • Outbound proxy acknowledgment user

    hello,
      we have the following scenario
      async. outbound proxy -> file adapter
      this works correctly but the acknowledgment that we would like to receive uses an unexisting user
      and returns following error "HTTP 401 - Unauthorized"
      anybody knows were to adjust this user ?
      we could create the user but we would like to know where to find it
      thanks 
    regards,
    michel

    HTTP logs have to be activated at instance profile level, ie :
    icm/HTTP/logging_0                          PREFIX=/,LOGFILE=devs_http.trc,MAXSIZEKB=50000, SWITCHTF=day,FILEWRAP=on
    icm/HTTP/logging_client_0                   PREFIX=/,LOGFILE=devc_http.trc,MAXSIZEKB=50000, SWITCHTF=day,FILEWRAP=on
    and then restart the ICM (tcode SMICM and soft restart) ... Then, in SMICM, there is a HTTP logs menu that will display contents of these traces, you can often find user/url/rcode in it
    But maybe Stefan's solution could solve your issue (I'm not familiar with ACKs )
    Rgds
    Chris

  • Cube Alternative \ Outbound Proxy

    Hi,
    I currently have CUBE setup to my SIP provider, I would like to add an additional register or user agent. However since my current service provider uses outbound proxy for the invite messages I'm running into issues with the second UA.
    So I'd like to know if anyone has setup any alternatives to using CUBE such as a software b2bua or session border controller. I currently looking at Yate 

    Thanks for the assistance,
    Ok here is the configuration which was provided by our ISP. It is different to other configurations I'm used to as the register and sip-server addresses are our company name.
    This configuration connects to a local ISP router.
    voice service voip
     ip address trusted list
      ipv4 0.0.0.0 0.0.0.0
     address-hiding
     allow-connections sip to sip
     fax protocol none 
     sip
      outbound-proxy dns:Provider.telstra.com
      midcall-signaling passthru
      privacy-policy passthru
      sip-profiles 100
      error-code-override options-keepalive failure 503
    sip-ua 
     credentials username User password 7 pass realm ourcompanyname.com
     authentication username User password 7 pass
     authentication username User password 7 pass realm ourcompanyname.com
     set pstn-cause 47 sip-status 486
     retry invite 2
     retry response 3
     retry bye 3
     retry prack 6
     retry register 2
     timers expires 300000
     registrar dns:ourcompanyname.com expires 30000
     sip-server dns:ourcompanyname.com
     connection-reuse
    Gi0/0 Internet (Public)
    Gi0/1 Direct connection to provider voicegateway
    Gi0/2 Management (Internal Traffic)
    I have configured a specific route for Provider.telstra.com
    So I'd like to add a second register, but I ran into issues with the invite going out Gi0/1 the provider gateway.
    I tried to add a specific route out Gi0/0 (internet) however it still goes to via Gi0/1 due to the outbound proxy setting.
    I'm unsure how to reconfigure the setup to avoid using outbound proxy. I managed to set the outbound proxy the outgoing dial peers and calls would work however the b2bua wouldn't register for incomming calls.

  • Error in ABAP Proxy

    Hi ,
    I am getting an error in the proxy , it was working fine but today only it is throughing the following error :
      <SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
      <SAP:P1>CREATE_OBJECT_CLASS_NOT_FOUND</SAP:P1>
      <SAP:P2>ZZCL_MIIA_UKEUROPE_TLOG</SAP:P2>
      <SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error during proxy processing</SAP:Stack>
    Please let me know the reason of this .
    Thanks in anticipation
    Anita

    Hi,
    I am assuming you have a server proxy (Inbound interface).
    Your proxy objects have not been created properly.
    To check this, send a message to XI.
    Either XI itself will throw an error message, or running SXI_MONITOR in receiving SAP application will show you the error . If you do not see any entry for corresponding interface, then proxy objects have not been created properly.
    Regards,
    Puloma.

  • Error When connecting proxy

    Hi,
    When I try to connect proxy in application, it is not connecting instead when I check whether it is going through proxy or not it is telling that it is establishing direct connection only. Here I have posted part of the coding. Please If any error give me a hint.
                System.setProperty("ProxySet", "true");
                SocketAddress addr = new InetSocketAddress("webcache.mydomain.com",80);
                proxy=new Proxy(Proxy.Type.HTTP,addr);here in this code part I am checking whether is connecting with proxy or not.
    URL u = new URL(url);
    URLConnection uu=u.openConnection(ScrapperInterface.proxy);
    try
                    URI uuu = uu.getURL().toURI();
                    List l=ProxySelector.getDefault().select(uuu);
                    for (Iterator iter = l.iterator(); iter.hasNext(); )
                         Proxy proxy = (Proxy) iter.next();
                         System.out.println("proxy hostname : " +proxy.type());
                         InetSocketAddress add = (InetSocketAddress)proxy.address();
                         if(add == null)
                             System.out.println("No Proxy");
                         else
                             System.out.println("proxy hostname : " +add.getHostName());
                             System.out.println("proxy port : " +add.getPort());
    catch (URISyntaxException ex)
                    Logger.getLogger(StartThread.class.getName()).log(Level.SEVERE, null, ex);
    }Output is:
    proxy hostname : DIRECT
    No Proxy

    Re: Error When connecting proxy You didn't get any error when you created the connection. Your title is misleading. Probably you are misleading yourself - see below.
    System.setProperty("ProxySet", "true");That does nothing. There is no such property, contrary to widespread belief.
    SocketAddress addr = new InetSocketAddress("webcache.mydomain.com",80);
    proxy=new Proxy(Proxy.Type.HTTP,addr);... and using java.net.Proxy has nothing to do with system properties in any case.
    URLConnection uu=u.openConnection(ScrapperInterface.proxy);Here you are opening a URLConnection via the proxy. As you got output from the code further down it is clear that this step must have succeeded. So all the code below is pointless.
    URI uuu = uu.getURL().toURI();Here you are getting the URI you created the connection for.
    List l=ProxySelector.getDefault().select(uuu);Here you are getting the Proxies the default ProxySelector would have given you for that URI. Nothing to do with the URLConnection you created, and nothing to do with the Proxy you created either.
    InetSocketAddress add = (InetSocketAddress)proxy.address();So here you are testing the proxy address for the system's default proxy for that URI. Again, nothing to do with what you did above.
    What you should be doing here is using the URLConnection you have already created. Not testing an address.

Maybe you are looking for