SAP R/3 - XI:  Commit fault com.sap.aii.af.mp.module.ModuleException

Hi -
We have an integration setup between SAP R/3 4.7C and SAP XI -
It uses background queues - and in our development environment, on the call to XI, we are receiving the error message:
Commit fault com.sap.aii.af.mp.module.ModuleException: call to messaging
The queue then goes into SYSFAIL status.
This is occurring on all of our integrations between R/3 and XI - which has been previously working -
I have been working w/ our Basis guy & he said that all his checks to both systems look ok.
Do you have any pointers on what to look at or check out?
Your help is very appreciated!
Thanks,
Michelle

Hi Michelle,
Please check if the background Xi database to which your transactions are committed is full. In case it is, you would need Basis help to archive them, before you proceed. Please check your dump for the same.
cheers,
Prashanth
P.S Please mark helpful answers.

Similar Messages

  • Commit fault: com.sap.aii.adapter.rfc.afcommunication.RFCAFWExpection: lo

    Hi,
    we are doing a RFC to file scenario. it works fine in DEV and QA. but in production sporadically it shows commit fault: com.sap.aii.adapter.rfc.afcommunication.RFCAFWExpection: lo error in SM58.
    I have refreshed the cache and all the necessary componets like Sender C.C, receiver C.C, Receiver determination, interface determination, sender agreement and receiver agreement is present.
    how to solve this issue. its production issue. pls help ASAP

    Hi,
    The ECC's business system has Technical System,Client number and Logical System Name.
    Also the same is reflected in BS of Integration Builder. it has the logical system, R/3 system and client number in Adapter specific identifiers.
    Can you also let me know how to check the complete error message in Tcode SM58. when i double-click on the error it just shows "Commit fault: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException:lo". how can i view the full message

  • RFC Error in SM58 Commit fault com.sap.aii.af.rfc.afcommunication

    Have a RFC interface between Sap R/3 and XI. Submit RFC request: call function 'Z_PGM'
            in background task
            destination 'XID'
            tables
              it_zmsfi_labels = t_table.
    Getting error in SM58 in R/3 : Commit fault com.sap.aii.af.rfc.afcommunication.Rf cAFWException: alternat
    Message no. SR053
    Any ideas? If I do test connection on in SM59 on TCP connection it's Ok.

    call function 'Z_PGM'
    in background task
      destination 'XID'
    tables
    it_zmsfi_labels = t_table.
    <b>COMMIT WORK.</b>
    This should solve your problem.
    regards
    SKM

  • RFC Error : Commit fault: com.sap.aii.af.rfc.afcommunication

    Hi ,
    I am having a problem in a RFC to File scenario. My Sender RFC is working fine and is showing the status green in the CC Monitoring in AdapterEngine under Component Monitoring. But we are trying to trigger the data to the RFC we are getting the following error "Commit fault: com.sap.aii.af.rfc.afcommunication.R
    fcAFWException: alterna "
    The RFC connection when tested it is ok .. the connection is established.
    Please suggest.
    Regards,
    Hemanthika

    Hi,
    1. Refer to the following notes
    SAP Note 730870
    SAP Note 775765
    Also check
    RFC Error in SM58 Commit fault
    RFC Error in SM58 Commit fault com.sap.aii.af.rfc.afcommunication
    2. have a look to R/3 transaction SM58 to find your message
    Thanks
    swarup

  • Another SOAP Sender adapter "com.sap.aii.af.mp.module.ModuleException" erro

    I am working on a synchronous scenario SOAP <-> XI <-> RFC.
    This worked fine, when I run it without SOAP adapter, direct via XI Pipeline.
    Now I want to use the SOAP sender adapter, but get the error as described below this post.
    As this is a real new XI installation, some patches or updates might be required to make it work. Or some adapter modules ?
    Any suggestions on how to solve this problem will be rewarded.
    What worries me a bit is the line "  " in the error description.
    Extra info: I use SoapSonar as a test webservice client. The error is the message as received in te test client.
    <?xml version="1.0"?>
    <!-- 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>ModuleUnknownException</code>
              <text><![CDATA[
    com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/645_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#9 $)
         at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427)
         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:160)
         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>

    Hi Chandravadhana,
    The colon should be there :
    http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
    The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    Under party:service:channel enter 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
    Regards
    Suraj

  • Package com.sap.ip.me.api.logging and com.sap.ip.me.api.user not found.

    I don't have
    com.sap.ip.me.api.logging
    and
    com.sap.ip.me.api.user
    packages in me2lib.jar (and none of the jars in the lib folder of the SAPMobileEngine folder).
    Any ideas as to where these are ?

    I don't think you can use ME2.1 Client with MI2.5 Server. At least they have different login protocol, and maybe different synchronization protocol as well.
    The library MEg.jar, that I have inspected for the missing libraries, is a part of MI25 SP09. I heartily advise you to migrate your application to MI.
    Cheers,
    Todor

  • Sap R/3 and XI -- Commit fault ModuleException. Please help

    Hi All,
    I have a RFC interface between Sap R/3 and XI.
    I am getting error in SM58 in R/3 :
    Commit fault com.sap.aii.af.mp.module.ModuleException: call to messaging.
    If I do test connection on in SM59 on TCP connection it's ok.
    For the above error I also receive for some time the below SLD error message in RWB of XI
    "Error during communication with System Landscape Directory: HTTP response code: 503 (Not Ready)"
    Please advice as it is production problem.
    Regards

    Hi Rick,
    Sometimes this error comes when there are huge amount of transactions taking place simultaneously. To resolve this ask your Basis guy/DBA to increase the screen numbers in database.
    Thanks!

  • RFC Data not sending to Destination ( com.sap.aii.af.rfc.afcommunication.Rf

    Hi Experts,
             i have created a TCP/IP connection in sm59 as ID4 with R/3 details. now i am calling a function module like this.
      call function 'Z_CBT_RFC_SALESPERSON'
           exporting
                p_sdate       = p_sdate
                p_edate       = p_edate
           tables
                isalesperson  = i_salesperson
           exceptions
                no_data_found = 1
                others        = 2.
      if sy-subrc <> 0.
        message e111(zi) with text-101.
      endif.
      if not i_salesperson[] is initial.
        call function 'Z_CBT_RFC_SALESPERSON' in background task destination
                                                 'ID4'
             exporting
                  p_sdate      = p_sdate
                  p_edate      = p_edate
             tables
                  isalesperson = i_salesperson.
        write: text-103.
      else.
        message e111(zi) with text-101.
        exit.
      endif.
      commit work .
              i am getting a problem that some times the data is exported to XI system but some times not.
            and in sm58 i am getting an error message for this execution as
    KOMMP2       Z_CBT_RFC_SALESPERSON         ID4           05/28/2007 02:30:10 <b>Commit fault: com.sap.aii.af.rfc.afcommunication.R</b> 95B7F6ADB04C465A8502002E brcpfd04 SE38 ZSIOPSP                                 105  0000
    Commit fault:
    com.sap.aii.af.rfc.afcommunication.RfcChannelMismatchExcept
             For all execution iam getting this error. Anyone call tell me how to resolve this issue.
              Please suggest me, do i need any modification in the program and in connection settings.please do the needful as soon as possible.points will be awarded for all answers.
    Thanks in advance.
    Thanks & Regards,
    Poorna

    Hi Sergio,
             Actually we are using the same connections for all the interfaces the we are developing in development system, and XI guys are using the same Program-ID in all their interfaces to configure.
             So when we are triggering the interface, some times the messages are going to XI, but sometimes no data is going.
             and let me know, if any more settings are required in sm59.
    Thanks & Regards,
    Poorna.

  • RFC - XI  Commit Fault error

    Hi All
    I have created an RFC (from R/3) that I am using to trigger a BPM in XI (3.0). 
    <b>RFC Destination - SM59</b>
    I have set up the RFC Destination in R/3 as follows:
    Connection Type = T
    Activation Type = Registration
    Program ID = zabfcxi
    GatewayHost = Trx SMGW -> HostName = R/3 system (i.e. NOT the XI server)
    GatewayService = sapgw00
    <b>XI Sender Communication Channel - CC_RFC_SENDER</b>
    In XI I have configured a RFC Sender communication channel as follows:
    <i>RFC Server Parameter</i>
    Application Server = Trx SMGW -> HostName = R/3 system (i.e. NOT the XI server)
    Application Server Service = sapgw00
    Program ID = zabfcxi
    <i>RFC Metadata Repository Parameter</i>
    Application Server = Trx SMGW -> HostName = R/3 system (i.e. NOT the XI server)
    System Number = 00
    Logon User/Password = myUser and myPassword
    Logon Language = EN
    Logon Client = 041
    <b>Sender Agreement</b>
    I have also set up a sender agreement:
    Service = R3_DEV_030
    Interface = Z_RFC_GET_SO_REQUESTS2 (name of RFC imported to XI)
    Sender Comm channel = RFC Sender adapter defned above
    When I run the test connection in SM59 it works without any problems.
    I have written a small ABAP that calls the RFC:
    CALL FUNCTION 'Z_RFC_GET_SO_REQUESTS'
      IN BACKGROUND TASK
      DESTINATION 'Z_ABFC_XI'
      EXPORTING
        REQUEST_SALES_ORDERS = export.
    COMMIT WORK.
    When I run this it completes with no errors.  However, nothing appears to be getting through to XI.  I have checked the log in SM58 and find that it is failing with this error:
    Commit fault: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup
    I have followed the SAP note "FAQ XI 3.0 RFC Adapter" qu.19 which states this is caused by incorrect Sender agreement but it all looks OK to me - hence why I have posted the details of it. I have also performed a full refresh of the cache but this has not fixed it either.
    Is anybody able to help...?
    Thanks
    Andy

    Hi Andrew,
    Hope these threads will help you.
    Error: Commit fault com.sap.aii.af.rfc.afcommunication.RfcAFWException: alt
    RFC error Commit fault com.sap.aii.af.rfc.afcommunication
    "maximum size of requests for one LUW has been reached"
    getting error in RFC sender adapter
    Error in RFC communication
    Reward points if helpfull.....

  • RFC Error in SM58 Commit fault

    My scenario is RFC to XI to FILE.
    I made RFC destination in SM59
    and configure xi according to
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    The connection test in SM59 is succeeded.
    I would like to execute BAPI, so wrote following..
      CALL FUNCTION 'BAPI_CUSTOMER_GETLIST'
           IN BACKGROUND TASK
           DESTINATION 'BAPI_XI_001'
       <<< parameters >>>
       COMMIT WORK.
    BUT in SM58, I got error
    'Commit fault: com.sap.aii.af.rfc.afcommunication.
    RfcAFWException: alterna '.
    Any ideas?
    Best regards.

    Thank you very much for your information.
    I checked Q&A19 of SAP NOTE 730870
    and configured XI again.
    Then I got a different error...
    ' program BAPI_CUSTOMER_GETLIST not registered / CPI
      C-CALL: 'ThSAPECMINIT'#  '
    I have already checked the spelling of BAPI's name.
    Have you saw this error??

  • Com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or passwo

    Hi All,
    I'm configuring the Solution Manager Diagnostics.
    I have all my agent SMD and IS installed.... but when I run the Setup Wizard, I received the following error:
    Step Wilyhost Agent Details
    Created destination BD1_DVEBMGS00_server0
    Created destination SapStartSrv_bnsr3dci_BD1_00
    Created destination BD1|bnsr3dci_BD1_00
    Created action SAP GC|BD1_DVEBMGS00_server0 - SAP GC|BD1_DVEBMGS00_server0
    Created action BD1|bnsr3dci_BD1_00 - SapStartSrv_bnsr3dci_BD1_00
    Created action BD1 - BD1 AbapSystem
    Created action BD1|bnsr3dci_BD1_00 - BD1|bnsr3dci_BD1_00 AbapInstance
    Created 4 action(s).
    0 Wilyhost Agent(s) from host bnsr3dci are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (bnssmpci.bns.local:6001) no Wilyhost Agent was detected from host bnsr3dci. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    and checking the jvm_smdagent.out file on managed system
    Running SMD Agent ...
    [ms://bnssmpci:8101/P4] Agent ready.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Using Java VM version "SAP Java Server VM 1.5.0_17" from SAP AG
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily
    host/IntroscopeSapAgent.profile
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Loaded file from /usr/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/Int
    roscopeSapAgent.profile
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval is set to 1800
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to 500
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is set to 3000
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions director
    y.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] The agent extensions directory /sap_mirrlog/sap/DAD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.ap
    plication.wilyhost/ext was successfully located
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Introscope Agent startup complete.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent SMDA97" based on the value of the System Property "com.wily.introscope.a
    gent.agentName".
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent SMDA97
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
    10/27/09 02:58:19 PM EDT [INFO] [IntroscopeAgent] Started Error Reporting service
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    10/27/09 02:58:20 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (1).
    Initialization done.
    10/27/09 02:58:30 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (2).
    10/27/09 02:58:40 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (3).
    10/27/09 02:58:50 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (4).
    10/27/09 02:59:00 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (5).
    10/27/09 02:59:11 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (6).
    10/27/09 02:59:21 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (7).
    10/27/09 02:59:31 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (8).
    10/27/09 02:59:41 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (9).
    10/27/09 02:59:51 PM EDT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.
    postofficehub.link.net.DefaultSocketFactory (10).
    10/27/09 02:59:51 PM EDT [INFO] [IntroscopeAgent.ConnectionThread] The Agent will continue to attempt to connect to Introscope Enterprise Manager. Further fai
    lures will not be logged.
    [ms://bnssmpci:8101/P4] Agent ready.
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Initialization done.
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    This is error common ?
    Any idea ?
    Weird for me is this line:
    "Failed to connect to the Introscope Enterprise Manager at localhost:6001"
    Because my INtroscope Enterprise Manager name is bnssmpci
    Thanks and Regars,
    Juan.

    SOLVED !!!
    Restart the J2EE Managed System and check the SAP Note - WilyHost agent fails to connect to ABAP stack (bad password

  • Com.sap.security.core.ume.service failed. J2EE Engine cannot be started

    Hi,
    I have configured SNC on NetWeaver 7.0 (ABAP+JAVA) System on Windows 2003 Server with MS-SQL 2005 Database.
    After the SNC configuration restarted the Server but the JAVA Server process is going down with EXIT Code -11113. The SNC Configuration is working fine but JAVA is not running. SDM and dispatcher are in green but server process is going gray.
    I have checked the log files under C:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log
    The following is the part of log file.
    #1.5#005056BA6C3F001D0000000F000008D8000489ACAFC86070#1277274683393#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_71##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    [EXCEPTION]
    #1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    #1.5#005056BA6C3F001D00000011000008D8000489ACAFC8628E#1277274683393#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_71##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
    Please help me to solve the issue.
    Thanks,
    Ajay.

    Hi Tim,
    I have configured using Kerberos library for 32 bit on Net Weaver 7.0 with MS SQL 2005 Server on Windows 2003 Server. I didnt change any thing on JAVA side. I have configured as per the Kerberos configuration steps  as per below URL
    http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/frameset.htm
    The configuration was successful and I am able to login with out asking password, but After the configuration when I have restarted every thing on ABAP side works well but JAVA server process going down with EXIT code -11113. One of the log file contains follows error message.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Jun 25, 2010 3:05:24 AM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    One of the line says "SNC required for this connection". What does this mean? What else need to be done for JAVA to communicate with ABAP?
    Thanks,
    Ajay.

  • Com.sap.security.core.server.secstorefs.WrongKeyException

    Hi,
    we have done a system copy,while starting the java stack we are getting the below error.
    Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong..
            at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
            at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
            at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
            at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
            at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:112)
            ... 15 more
    Caused by: com.sap.security.core.server.secstorefs.WrongKeyException: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong.
            at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:2017)
            at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
            at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
            at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
            ... 17 more
    Caused by: com.sap.security.core.server.secstorefs.InvalidStateException: Internal error during the decryption process.
            at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:850)
            at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1985)
            ... 20 more
    Caused by: javax.crypto.BadPaddingException: Invalid PKCS\#5 padding length: 30
            at iaik.security.cipher.s.b(Unknown Source)
            at iaik.security.cipher.w.a(Unknown Source)
            at iaik.security.cipher.w.engineDoFinal(Unknown Source)
            at javax.crypto.Cipher.doFinal(Unknown Source)
            at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:825)
            ... 21 more
    #1.#000255334607000000000015000640DE00046E8629009A5B#1247422399420#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Loading: ConfigurationManager returned false! #
    #1.#000255334607000000000017000640DE00046E8629009BC2#1247422399421#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Kernel not loaded. System halted.#
    #1.#00025533460700000000001A000640DE00046E862908A703#1247422399948#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#######Thread[Thread-1,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
    Thread[SAPEngine_System_Thread[impl:5]_2]
    Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.core.cluster.impl6.JoinPortListener | toString: com.sap.engine.core.cluster.impl6.JoinPortListener@252e252e] with classloader [com.sap.engine.boot.CoreClassLoader@21d821d8]#
    Regards,
    Sam

    Hi,
    Check with this note,
    Note 791574 -
    Also
    Secure Storage for Application Specific Data
    Applications or application components, deployed on the J2EE Engine, can save sensitive data
    in encrypted form in a secure storage area in the J2EE Engineu2019s configuration database. The
    data saved in this area is encrypted using a secret key that is created explicitly for the application
    or service. The J2EE Engine uses the triple DES algorithm to perform the encryption.
    You can use two approaches for storing and maintaining the encrypted data for the individual
    applications or application components:
    u2022 Centralized storage
    With centralized storage, applications or application components use the Secure Storage
    service on the J2EE Engine to encrypt and decrypt the data. This data is also stored in the
    corresponding secure storage context on the J2EE Engine. You can control the
    parameters of this secure storage area from the properties of the Configuration Manager.
    For more information
    u2022 Decentralized storage
    With decentralized storage, the applications and application component maintain their own
    storage area for the encrypted data. They only uses the Secure Storage service on the
    J2EE Engine to retrieve the key, which is necessary to encrypt and decrypt the data.
    Regards,
    Ravi

  • Java.lang.NoClassDefFoundError: com/sap/util/monitor/jarm/TaskMonitor

    hi all,
    i was trying to build and try a web service in my project.
    but at runtime it keeps throwing the following error(  log trace)
    i am unable to figure out the source of error.
    is it in the jco or anything else
    thanks in advance
    1.5#001143C809E500470000002E00000B8C00040CBB0F05957C#1139897457152#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#Guest#2####a9a4e0009d2011dacd42001143c809e5#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Server#Plain###User Guest, IP address
    HTTP request processing failed. HTTP error [401] will be returned. The error is [Cannot authenticate the user.No details available].#
    #1.5#001143C809E500530000001F00000B8C00040CBB0FEBCF9E#1139897472233#com.sap.engine.services.ejb#sap.com/xappsospservicebundle~enterpriseapp#com.sap.engine.services.ejb#I020381E1#1839####b13de9b09d2011da944e001143c809e5#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Java###
    [EXCEPTION]
    #1#com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method getRelatedReports.
         at com.sap.xapps.osp.orgmgmt.servicebundle.sbejb.OrgMgmtSBLocalLocalObjectImpl10.getRelatedReports(OrgMgmtSBLocalLocalObjectImpl10.java:121)
         at com.sap.xapps.osp.orgmgmt.servicebundle.facade.OrgMgtFacadeBean.getRelatedReports(OrgMgtFacadeBean.java:425)
         at com.sap.xapps.osp.orgmgmt.servicebundle.facade.OrgMgtFacadeLocalLocalObjectImpl10.getRelatedReports(OrgMgtFacadeLocalLocalObjectImpl10.java:103)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
         at SoapServlet.doPost(SoapServlet.java:51)
         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:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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)
    Caused by: java.lang.NoClassDefFoundError: com/sap/util/monitor/jarm/TaskMonitor
         at com.sap.mw.jco.util.Jarm.getRequestMonitor(Jarm.java:57)
         at com.sap.mw.jco.JCO$Repository.getFunctionInterface(JCO.java:19069)
         at com.sap.mw.jco.JCO$BasicRepository.getFunctionTemplate(JCO.java:18151)
         at com.sap.xapps.osp.orgmgmt.servicebundle.common.OrgMgmtSBHelper.createFunction(OrgMgmtSBHelper.java:491)
         at com.sap.xapps.osp.orgmgmt.servicebundle.impl.OrgMgmtBusinessDelegate.getRelatedReports(OrgMgmtBusinessDelegate.java:1273)
         at com.sap.xapps.osp.orgmgmt.servicebundle.sbejb.OrgMgmtSBBean.getRelatedReports(OrgMgmtSBBean.java:170)
         at com.sap.xapps.osp.orgmgmt.servicebundle.sbejb.OrgMgmtSBLocalLocalObjectImpl10.getRelatedReports(OrgMgmtSBLocalLocalObjectImpl10.java:103)
         ... 27 more

    hi,
    thanks for the replies.
    well i guess that(user authentication) is not the problem.
    Coz that happens even before i start the web service.
    i guess the problem is that the appl. is not finding the TaskMonitor class ( see the last 10 lines of the log).
    does anyone have a solution for that.
    thanks

  • JCO - RFC_ERROR_SYSTEM_FAILURE: com/sap/mw/jco/JCO$Server

    Hi,
    I call from Java an ABAP RFC and this RFC in turn call back the Java stack and it fails.
    At Java side I get:
    #1#com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: com/sap/mw/jco/JCO$Server
         at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
         at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1515)
         at com.sap.mw.jco.JCO$Client.execute(JCO.java:3996)
         at com.sap.mw.jco.JCO$Client.execute(JCO.java:3544)
         at com.sap.sup.admin.setup.SolManRfcAdapter.getJabapLandscape(SolManRfcAdapter.java:787)
         at com.sap.sup.admin.setup.SetupUpgrader.execute(SetupUpgrader.java:52)
    At ABAP side I get:
    Category               ABAP Programming Error
    Runtime Errors      CALL_FUNCTION_REMOTE_ERROR
    ABAP Program      CL_DIAGLS_SMSY_FACTORY========CP
    Application Component  SV-SMG-DIA
    Date and Time        21.09.2009 17:50:59
    Short text
         "com/sap/mw/jco/JCO$Server"
    Is it allowed to call JAVA -> ABAP -> JAVA from JCO point of view?
    Thanks in advance!
    Regards,
    Serge.

    Hi Serge,
    Two doubts:
    - Does your RFC work when you call it directly from the SE37 puting the same input parameters used by Java application?
    - Was the RFC changed after the coding of Java application? If so, the interface between Java and RFC must be regenerated.
    Regards,
    Rodrigo.

Maybe you are looking for

  • Why are some of the forums locked?

    Why are some of the forums locked?  Could it be because the number of complains for service (the lack of), scams by stores - employees, placating that happens just to make a sale or general MISINFORMATION and a total disregard for their customers wou

  • How do I get Adobe Acrobat to appear in the Conent Type listins under Tools/Options/Applications

    I want PDFs to open in Acrobat within the browser and not open up the Acrobat application. The Firefox 4.0 Help lists the way to do this, but Acrobat does not appear in my list under Tools/Options/Applications, so I'm stuck with no answer

  • Using Roll Over Images for Hots Spots in DW CS 5

    Ok  I had this sort of working .. but what i am trying to do is have pictures pop up when the mouse rollovers a hot spot.   I do this with two layers and using the behavior window The full project is at http://www.kasdivi.com/pages/map.html...  ( tho

  • All format DTD in new document

    As a product update, new features in Dreamweaver, the header Doctype, DW could be compatible with the standard documents HTML 5, XHTML 1.2, XHTML 2 and XHTML Mobile Profile 1.2, can build Web applications persistent over time. Thank, Siriö Astaroth

  • Receiving sms in labview from GSM USB Module

    I am using HSUPA 7.2Mbps gsm usb module. Program is not showing any error but sms is not received.