Resource com.sap.aii.af.svc with type service, not active on the server

Hi Forum,
in my X1 server, in rwb, it gave error:
HTTP request failed. Error code: "503". Error message: "Service Unavailable [http://xyz:50000/AdapterFramework/rtc,
on further analysis we find that:
<b>  Application cannot be started.
  Details:   com.sap.engine.services.deploy.container.ExceptionInfo: Application sap.com/com.sap.xi.mdt cannot be started. Reason: it has hard reference to resource com.sap.aii.af.svc with type service, which is not active on the server.</b>
and the service/component com.sap.aii.af.svc is not present as the error says,
In visual admin, in the services list i couldnt find this particular resource,
pls instruct me how to deploy/start this service com.sap.aii.af.svc ,

Hi,
Please check out the user authorization and role and also check that you are maintaining the passwords in all places where required.
Regards
Aashish Sinha
PS : reward points if helpful

Similar Messages

  • FTP error-Unable to create new pooled resource: com.sap.aii.adapter.file.ft

    Hi,
    We have a scenario where XI receives a Idoc and based on the contents of Idoc, It will generate 5 different files and send it to the external FTP server.We configured 5 receiver channels for these 5 files.
    When this interface runs, most of the files will be delivered but some of the messages will be errored out.
    The receiver channel has shown the following error-
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: com.sap.aii.adapter.file.ftp.FTPEx
    I tried to resend them by temperorily stopping other channels to reduce connections to this FTP server.But these messages again resulted with same error.
    Can someone suggest what might be the cause for this error.
    Thanks in advance.

    Hi ,
    As I am not sure about the problem so U just try all of the option I am writing below. It may help u as these are the probable solutions for this problem.
    1.perform Full CPA cache refresh using PIDIRUSER
    2.The problem seems to be in establishing the connection with the File server . This could be due to
    a. Wrong user name or password in receiver adapter .
    b. Firewall connection are not open
    actually you are saying that some files are being delivered so all the file has to be deliverd on same server on diffrent directory or all files are going on diffrent server at present I am assuming that all files are going on diffrent server so please check UID & PWD properly.if they are on same server but diff. directory it can be easily done using one Communication channel only.
    3. Finally please check the errorneous communication channel .
    to check your communication channels are working fine or not you can check in channel monitoring in PI7.0, adapter monitoring in Xi3.0.
    if you are on PI7.0, goto RWBCache monitoring select AE and cilck disply-select the date todays--check everything is greent here
    4.Please check your maximal connection pool .
    Regards,
    Saurabh

  • Error when attempting to get processing resources: com.sap.aii.af.service.

    Dear All,
    i am getting below error in RWB in receiver Channel
    Error
    "Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'CONNECTION STRING: NoClassDefFoundError: sun.awt.X11GraphicsEnvironment (initialization failure)"
    Note: outbound has processed succesfully in both ABAP and Java Stack.

    Hi,
    Can you please let us know, which receiver adapter are you using??
    I guess it is JDBC: IF it is ...can you check the Driver and Connection details maintained on the channel.
    JDBC Driver:com.microsoft.sqlserver.jdbc.SQLServerDriver
    CONNECTION:jdbc:sqlserver://IP ADDRESS:PORT;Database=HOST NAME;
    -Rahul

  • Last conditon type is not active in the pricing procedure

    Hi gurus,
    In the standard system, when there are multiple Condition types exists in the pricing procedure for the same condition class ( Example : Price) then the value of the last condition type should be active and rest all should be inactive. Where as in my case i have 4 pricing condition types , instead of last condition type 3rd condition type is being active. Can any one suggest what would be the reason for this and how to make sure that last condition type is set as active?

    I found that as the condition value is less than the condition base value , even though conditon type was last in the list it was not set as active. This can be seen by selecting the condtion type in the pricing details and then click on the details icon ( Lens ) .

  • Error com.sap.aii.af.sdk.xi.util.URI$MalformedURIException: no scheme

    Hi,
    I am registering the following error in a SOAP Sender Communication Channel, it's very strange because of in the Development Environment everything worked fine.
    com.sap.aii.af.sdk.xi.util.URI$MalformedURIException: no scheme
    The Scenario is the following:
    Sender: SOAP
    Receiver: ABAP Proxy (Using the XI configuration)
    I configured all the scenario to use only the Adapter Engine instead the Integration Server and, as I explained in the previous paragraph it worked fine in Development environment.
    Does anybody know what could be going on?
    Thank a lot for your help.
    Kind Regards,
    Victoria

    Hello Victoria,
    Can you please check if the inbound address for SOAP messages should be as follow.Other wise you will exceptions.
    : http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    Under
    party:service:channelenter the party name, the service name, and the
    name of the communication channel. If no party has been created, enter the
    following: channel=:service:channel
    Kind Regards
    Praveen Reddy

  • Where is the directory for "com.sap.aii.adapter.lib.sda" - PI 7.1 ?

    Hi,
    I want to install new JDBC driver in PI 7.1 EHP1, base on notes 1138877 i have to modified file "com.sap.aii.adapter.lib.sda".
    please advise in which directory the file is ?
    Best Regards
    Fernand

    Hi
    you can go to the drive in which your PI is installed for example if it is E then path will be like
    E:/usr/sap/<SID>/DVEBMGS00/j2ee/cluster/bin/ext/com.sap.aii.adapter.lib
    copy this file on your local desktop unzip it using winzip and add the driver jar to this
    make the entry of your driver jar file in provider.xml file and  again zip the folder
    then using SDM deploy this file
    for complete process search on SDN "how to install and configure external  drivers for jDBC and JMS"
    Thanks
    sandeep

  • Error message com.sap.aii.af.ra.ms.api.DeliveryException: error while proce

    hello experts
    I am sending a message WS2RFC and recieve an error message that return from the RFC.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing the request to rfc-client: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Date '03042008' has a wrong format at field DATUM: Unparseable date: "03042008"</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    any ideas what it is and how to solve it?

    Hi,
    Looks like you have passed data in wrong format to RFC input parameter.
    Your format: DDMMYYYY (03042008)
    Expected: YYYYMMDD
    I would use a graphical mapping function "DataTrans" to convert date format from DDMMYYYY to YYYYMMDD.
    Regards,
    Jakub

  • Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_MAPPINGPROGR

    Hi all,
    I am currently doing a File --> RFC --> File synchronous interface ( I am not using RFC lookup functionality here ).
    I am doing this scenario according to the following Wiki link,
    [http://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File(Without+BPM)]
    When testing the interface, i am getting an error "Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_MAPPINGPROGRAM_FOUND:" in the sender communication channel. I don't have any idea about this error, could anyone help me in this issue.
    Cheers,
    Sherin Jose P

    Hi Sherin Jose P,
                                Please recheck your Integration Directory configuration for the scenario. Specially please check inbound interface determination settings. Here the communication channel is unable to find the interface mapping after receiving XML message. Did you use java mapping ? then please check the code again since it might not be producing exact target xml structure. Finally please ensure all mapping programs are existing and activated. If all mapping are activated then refresh the cache.
        Please check  in st22 transaction all errors in PI, whenever you get this message. There may be other reasons of error as well. There can be occasional short dumps due to data lengths or validations in ABAP programs. These short dumps in ERP may cause failures raised in PI.
    Finally if there are some exception in mapping then this error you can expect.
    Hope this helps.
    regards
    Anupam

  • Com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc don't start

    Hello,
    In order to configure JMS Receiver Adapter to access Websphere Application Server 7.0, I have recently deployed file com.sap.aii.adapter.lib.sca with the following libraries:
    com.sap.aii.adapter.lib_api.jar
    com.ibm.ws.ejb.thinclient_7.0.0.jar
    com.ibm.ws.orb_7.0.0.jar
    com.ibm.ws.sib.client.thin.jms_7.0.0.jar
    com.ibm.ws.runtime.jar   
    javax.j2ee.jms.jar
    The communication channel can reach the queue but when I send a message it fails because services sap.com/com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc are not started.
    Checking dev_server0 file I found the following error.
    ==============================================================================================
    Service com.sap.aii.adapter.jdbc.svc start ================= ERROR =================
    com.sap.engine.frame.ServiceException: Could not obtain an initial context due to a communication failure. Since no provider
    URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used.  Make sure that any
    bootstrap address information in the URL is correct and that the target name server is running.  Possible causes other than
    an incorrect bootstrap address or unavailable name server include the network environment and workstation network configurati
    on.
    at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:151)
    at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
    at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
    at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
    Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
    e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used.  Make
    sure that any bootstrap address information in the URL is correct and that the target name server is running.  Possible caus
    es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
    rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,
    port=2809  vmcid: 0x4942f000  minor code: 3586  completed: No]
    at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
    at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
    at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
    at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
    at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:100)
    ... 6 more
    Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,port=2809  vmcid: 0x4942f0
    00  minor code: 3586  completed: No
    at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:425)
    at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:436)
    at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:187)
    at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
    at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:120)
    at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:209)
    at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
    at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
    at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
    at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
    at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
    ... 16 more
    Caused by: java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    at java.net.Socket.connect(Socket.java:522)
    at java.net.Socket.connect(Socket.java:470)
    at java.net.Socket.<init>(Socket.java:367)
    at java.net.Socket.<init>(Socket.java:180)
    at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:270)
    at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
    ... 28 more
    Service com.sap.aii.adapter.jms.svc start ================= ERROR =================
    com.sap.engine.frame.ServiceRuntimeException: Could not obtain an initial context due to a communication failure. Since no pr
    ovider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used.  Make sure t
    hat any bootstrap address information in the URL is correct and that the target name server is running.  Possible causes othe
    r than an incorrect bootstrap address or unavailable name server include the network environment and workstation network conf
    iguration.
    at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:171)
    at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.start(AdapterServiceFrameImpl.java:125)
    at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
    at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
    at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
    Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
    e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used.  Make
    sure that any bootstrap address information in the URL is correct and that the target name server is running.  Possible caus
    es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
    rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5)  vmcid: 0x4942f000  minor co
    de: 775  completed: No]
    at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
    at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
    at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
    at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
    at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:163)
    ... 7 more
    Caused by: org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5)  vmcid: 0x4942f000  minor code: 775  completed: No
    at com.ibm.rmi.iiop.Connection.checkEstablished(Connection.java:3091)
    at com.ibm.rmi.iiop.Connection.send(Connection.java:2145)
    at com.ibm.rmi.iiop.Connection._locate(Connection.java:463)
    at com.ibm.rmi.iiop.Connection.locate(Connection.java:439)
    at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
    at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
    at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
    at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
    at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
    at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
    at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
    ... 17 more
    ==============================================================================================
    Could anyone tell me why is trying to connect to "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService"? Do I have to configure a default provider URL for SAP PI server? If so, where I configure it? Any help will be appreciated.
    Thank you in advance.
    Roger Allué i Vall

    Hi Roger,
    we also experience the same issue and would be very keen to understand how you resolved this problem.
    Many thanks.
    Dieter

  • Java proxy problem:com.sap.aii.proxy.xiruntime cannot be resolved to a type

    hi:
        i am new to Java proxy and new to SAP netweaver developer studio.
        thei PI version is 7.1
        I have generate a java proxy , then create a project in netweaver developer studio and import this java proxy according document "How Tou2026Work with XI 3.0 Java Proxies".
        but i can not find :aii_proxy_xirt.jar  aii_msg_runtime.jar on the PI server, only guidgenerator.jaraii_utilxi_misc.jar could be found. then i could not config the build path.
        in the  SAP netweaver developer studio, the error shows like :com.sap.aii.proxy.xiruntime cannot be resolved to a type
       then how to resolve this problem
       thank you very much

    Hi Cheng,
    I am trying to create a java proxy to send message from WebAS to PI using java proxy.
    I am using NWDS 7.1. Can you please help with step on how to create a java proxy in NWDS 7.1?
    Thanks and best regards,
    Arun prabhu S

  • Unable to start service 'com.sap.aii.adapter.jms.svc'

    Hi people,
    After I have successfully deployed the external drivers jdbc/jms drivers on a PI 7.1 system trough JSPM using the com.sap.aii.adapter.lib.sda file but now the com.sap.aii.adapter.jms.svc and the com.sap.aii.adapter.jdbc.svc do not want to start up. When checking the log DefaulTrace log file I found the following error Reported reason: Service com.sap.aii.adapter.jms.svc is not loaded Any ideas on what the problem could be?

    Hi people,
    Thanks for all the ideas. I have followed all the notes and guides to prepare the SDA file ie editing the XML file and adding the JAR files.
    The problem was that somewhere along the line the provider.xml file of the old aii_af_jmsproviderlib.sda and the new com.sap.aii.adapter.lib.sda file seeming ot "merged" during my struggles.
    The provider.xml file of the SDA which I tried to uploaded had the two reference entries which actually belong to the old aii_af_jmsproviderlib.sda in as well as the correct reference entry. Once I removed these incorrect reference entries the services started up correctly.
    I found the error mention above by firstly renaming the DefaultTrace_X.trc file and restarting the JAVA stack. I then stepped through each line of the newly created DefaultTrace_X.trc file from the top down and found the following entries:
    1) Cannot resolve component library:sap.com/com.sap.aii.adapter.lib because referenced component Reference strong to library com.sap.aii.messaging.runtime not found#
    2) Cannot resolve component service:sap.com/com.sap.aii.adapter.jdbc.svc because referenced component library:sap.com/com.sap.aii.adapter.lib not resolved#
    3) Cannot resolve component service:sap.com/com.sap.aii.adapter.jms.svc because referenced component library:sap.com/com.sap.aii.adapter.lib not resolved#
    In line line 1 I saw that it was referencing the com.sap.aii.messaging.runtime which seemed suspect. Luckily I still had the original SDA file and when comparing it to the uploaded SDA file I found the incorrect entry.
    Thanks again for all the help

  • XI messages failed with com.sap.aii.af.ra.ms.api.ConfigException

    Hi forum experts,
    A group of POs were sent at the same time, but once a while we get one PO failed with the below error.  Could someone help me understand what the below error message mean.  Your help would be greatly appreciated.
    thanks,
    Velvet
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Call Adapter
    -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    <SAP:Category>XIAdapterFramework</SAP:Category>
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.ConfigException: Could not check current user (PIISUSER) against technical IS service user. Reason: Failed to read IS ServiceUser Id from EP. Reason: null</SAP:AdditionalText>
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack />
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>

    Hi,
      we are facing exactly the same problem. Where you able to solve it? And how?
    Thanks.
    S.Socratous

  • Sda with com/sap/aii/utilxi/misc/api/BaseRuntimeException jar?

    Hi,
    does anybody know the location and name of the sda file which contains the class com/sap/aii/utilxi/misc/api/BaseRuntimeException?
    Kind regards and thank you in advance,
    Heiko

    Hi Gopinath
    Check this thread
    An invalid XML character (Unicode: 0x1d) was found in the element
    Kind regards
    Javi

  • Error message "com.sap.aii.af.ra.ms.api.DeliveryException: "

    Hi Team,
    Created a simple file2file scenarion successfully. Unable to pick the file from Sender directory to Receiver Directory.
    Checked from monitoring the Communication Channel.
    Error message shown for sender communication channel as below:
      Communication Channel  Status   Short Log                                Control Data   Party  Service           Adapter Type  Direction 
      sen_cc                 Red ball Processing Errors In the Last 30 Seconds  Manually             kanchuf2f_sen_bs   File         Sender                                                                               
    Line 1 / 1
    By selecting the sender communication channel "sen_cc", below is the node details given.
    Processing Details for Cluster Node Server 0 1_54295
    Type 
    Time Stamp         Message ID                           Explanation 
    12/3/08 8:20:01 AM 45f841be-a421-43bd-235a-c7ad19b0aec8 Retry interval started. Length: 60.0 seconds
    12/3/08 8:20:01 AM 45f841be-a421-43bd-235a-c7ad19b0aec8 Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:
    By clicking on the first Message ID, The message says successful upto some point  and give error says JCO COMMUNICATION FAILURE and RFC issue.
    Below is the information provided in detail.
      Audit Log for Message: 45f841be-a421-43bd-235a-c7ad19b0aec8
    Time Stamp          Status  Description
    03.12.2008 08:20:00 Success Channel sen_cc: Send binary file  "f:\xi_file\sender\f2fmap.xml". Size 210 with QoS BE
    03.12.2008 08:20:00 Success Application attempting to send an XI message synchronously using connection AFW.
    03.12.2008 08:20:00 Success Trying to put the message into the call queue.
    03.12.2008 08:20:00 Success Message successfully put into the queue.
    03.12.2008 08:20:00 Success The message was successfully retrieved from the call queue.
    03.12.2008 08:20:00 Success The message status set to DLNG.
    03.12.2008 08:20:01 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:.
    03.12.2008 08:20:01 Error Transmitting the message using connection http://sitaserv33:8001/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:.
    03.12.2008 08:20:01 Error The message status set to FAIL.
    03.12.2008 08:20:01 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:                                                                               
    Page 1 / 2
    I think this could be the problem with some basis related settings, I am not sure what exactly the issue with.
    Any idea what exactly the error is talking about please do help me in finding the solution to thresolve this error message.
    Regards,
    Venkat Ramana K

    Hi Carlos,
    Thank you for the quick information.
    Followed all the steps and also basis person from onsite restarted the XI server.
    Now, I am able to log onto XI with the login Id but, when I give Tr Code: SXMB_IFR, unable to open the browser that shows Integration Builder.
    Getting the error message.
    *500   Internal Server Error*
                                                                                    *SAP J2EE Engine/7.00*
    **Exception**
    *An internal error occurred. Contact you XI administrator*
    *Unable to read configuration data (ExchangeProfile/aii.properties)*
    Error Details, Error History, Build Info, Generic Application Info
    Regards,
    Venkat Ramana K

  • Transport Fail -com.sap.aii.utilxi.misc.api.ResourceException:Import

    Hi Experts,
    My Transports through Solution Manager is failing in Production PI. Transports are imported, deployed successfully in Test and Regression environments and working fine. Transport requests are of type Workbench and we are attaching '.tpz' files as Non abap objects. All contain ESR objects, no ID components. Import and Check version steps are good but failing at Deployment step in Production PI.
    Please find the log which I can see in SE10. All the transports failed with the same below error description.
    CTS Import Service - Version 0.94 04.04.2008
    ==============================================================
    Deploy Web service destination = CTSDEPLOY
    Directory = /usr/sap/trans/data
    SDM Deploy URL =
    SLD Deploy URL =
    XI Deploy URL = http://ABC2159161:50000
    Start import with id:4E8B872CA9F100F2E10080000A32109F
    DeployProxy (patch level:0) called with followingparameters:
    Deployable(0)
    Deployable-Type:1
    Deployable-Id:4E6E38F506B601AAE10080000A321063
    Deployable-TransportContainerId:DI1K900677
    Deployable-ContentLocator:/usr/sap/trans/data/DI1K900677/XI7_1
    >>>63.tpz
    Property(0)
    Property-key:TARGETSYSTEMID Property-value:PI1
    Begin CommunicationData-Type[0]:1
    CommunicationData-Address:http://ABC2159161:50000/rep
    CommunicationData-Host:ABC2159161
    CommunicationData-Port:50000
    CommunicationData-User:'filled'
    CommunicationData-Password:'filled'
    Importing archive:XI7_1_A_SAPPI_CM_1.0_of_ABC.com-objs_6
    com.sap.aii.ibtransportclient.XiTransportException: caused by:
    >>>rt failed: Internal error when importing object [Lcom.sap.a
    >>>aused by: com.sap.aii.utilxi.misc.api.ResourceException: Im
    >>>g object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@7ffc92d
    >>>ethodFault: caused by: ClientServerException exception:Impo
    >>>object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@7ffc92d c
    >>>sourceException: Import failed: Internal error when importi
    >>>IWorkspace;@7ffc92d
    End CommunicationData-Type[0]:1
    End import with returncode:'8'
    Deployment
    End date and time : 20111009003401
    Ended with return code:  ===> 8 <===
    Thanks,
    Nabendu.

    Hi,
    I have already informed Basis about these. But do we have any way to check the exact reason for this failure?
    All the above points can ensure the successful transport to Production or not, I am not sure.
    Thanks,
    Nabendu.

Maybe you are looking for