JCO log

Hi
I am calling an RFC Function module in R/3. I would like to see which values that is sent through the JCO, is this possible?
I know about the dev_jrfc log but this does not give me parameter information. Is there anoter JCO log?
(I have also looked in R/3 but the trace for the RFC activity does not display the in parameters for the function module)
Best Regards// -Fred

Hi,
for traces try locations com.sap.conn.rfc, com.sap.conn.jco or com.sap.mw.jco , com.sap.mw.jrfc.
for logs this category seems right //System/Server/Connector/Rfc
greetings Georgi

Similar Messages

  • How to enable JCo logging

    I know I've seen this somewhere, but now that I need it, I can't find it.  I've spent two hours searching all the forums.  Can someone tell me how I enable JCo logging?  I have a JCO/Java program that works fine from the command line, but doesn't work when I try to use it in a Tomcat servlet.  None of the log files that I can find have any errors in them, but it appears that the call to JCO.createClient fails in the servlet.  I've read all of the posts about putting the JCo jar file in the servlet's lib directory and copying sapjcorfc.dll to Tomcat's bin directory, but no luck.  I'm hoping that there is some way that I can get JCo to give me a log that will indicate what is going wrong.  Thank you for your help.

    <b>SAP Note 723562</b>
    2. Runtime loading mechanism
    When an application references a JCo class for the first time it will be loaded by the associated class loader. During this process JCo's static initializer will be executed. This routine will search and load the JCo JNI library by using the following algorithm:
    1. Try to load the sapjcorfc library from the same directory where the sapjco.jar file or the JCo class files are located.
    2. Search the sapjcorfc library along the directory path defined in the java.library.path system property from left to right and if found load it from there.
                Note: If this property is not set manually, the JVM will usually set the OS specific library path environment variable as the default java.library.path system property at startup.
    1. Let the JVM handle the loading of the sapjcorfc library by delegating this task to its System.loadLibrary(String) method.
    JCo's JNI library is linked with the native RFC library. So when it is loaded the operating system will try to resolve its dependencies by loading the native RFC library, too. Usually, this will be done by searching for the first occurrence of the rfccm | librfc32 library along the directory path defined by the OS specific library path environment variable from left to right and load it.
    If the sapjcorfc library and/or the rfccm | librfc32 library cannot be loaded, you will get an ExceptionInInitializerError from the JCO. <clinit> method saying that it could not load the middleware layer com.sap.mw.jco.rfc.MiddlewareRFC. This error message may be caused for one of the following reasons:
    The sapjcorfc library cannot be found by using the above described algorithm, because you unintentionally installed it to the wrong directory or forgot to specify its directory in the OS specific library path environment variable or alternatively in the java.library.path system property.
    The rfccm | librfc32 library cannot be found because you unintentionally installed it to the wrong directory or forgot to specify its directory in the OS specific library path environment variable.
    The version of the sapjcorfc library found via the sapjco.jar directory or the java.library.path system property is not the required version (the version numbers and dates of the JCo middleware and the JCo library must be equal).
    The version of the rfccm | librfc32 library found via the OS specific library path environment variable is too old (for example you forgot to copy the librfc32.dll to the <WinDir>\system32 directory and an older version is loaded from there).
    The sapjcorfc library, the rfccm | librfc32 library or both lack the execute permission flag.
    The sapjcorfc library, the rfccm | librfc32 library or both do not have the same bit width as the JVM.
    The sapjcorfc library, the rfccm | librfc32 library or both were from a different JCo distribution and are not for use with your operating system and/or your hardware processor.
    The sapjcorfc library, the rfccm | librfc32 library or both require a higher operating system version.

  • Unable to load the transactions"

    Hi All,
    I have established the JCO connection between SAP and xMII. However, in the Routing Rules tab of iDOC listener, I am getting the error as " Unable to load the transactions"
    Can anyone help me in this?
    Best Regards,
    Ajit Dubal.

    Hi,
      It is not some default transaction. But it would have been set by someone in it. So I don't know the details. Please check the JCO log file if it can help.
    Here <b>IDOC_XMII</b> is the iDocListener. So match server name with ur Listener name.
    C:\Lighthammer\JCO\jcoservers.xml
    <?xml version="1.0" encoding="UTF-8" ?>
    - <Servers>
    - <Server name="<b>IDOC_XMII</b>">
      <ServerProps gwhost="xxx" gwserv="sapgw00" progid="IDOC_XMII" trace="1" unicode="0" />
      <ClientProps ashost="xxx" client="xxx" lang="en" passwd="xxx=" sysnr="xx" user="xxx" />
      <Routing>
      <Rule input="Input_Material" legacy="false" msgtype="*" password="" path="C:/Lighthammer/JCO/Output/" server="localhost" <b>transaction="training/bapi_mat"</b> username="" />
      </Routing>
      </Server>
    <Servers>
    Regards,
    Harini S

  • Available RFC Destinations

    Hello,
    How can i check the available RFC destinations in J2EE engine on Portal.
    (without Visual Administrator)
    Regards

    Hi,
    you could for example check the JCO log in the J2EE:
    <root>\usr\sap\<SYSID>\DVEBMGS00\j2ee\cluster\server0\dev_jrfc.trc
    As well you could check the server or default trace.
    --> from above location
    .\log\defaultTrace.0.trc
    .\log\server\server.0.log
    For that you could use the log viewer of the J2EE (under services).
    As well check all the settings for the JCO service in the J2EE.
    Rgds Thomas

  • Data Lookup with XI mapping.

    Hi,
    I am trying to write a user define function to do a data
    lookup by calling an RFC function. I am trying this out as per the document available in SDN namely "How to Perform SAP Data Lookups Within XI Mappings". The user defined function does not compile and give me the following error. Can someone help me out with this problem.
    Compilation error
    D:/usr/sap/X3A/DVEBMGS31/j2ee/cluster/server0/./temp/classpath_resolver/Map370955f0cc2311d8959a00d0b77fc64c/source/com/sap/xi/tf/_gwMsgRFC_msg_.java:3: package com.sap.mw.jco does not exist
    import com.sap.aii.mappingtool.tf3.;import com.sap.aii.mappingtool.tf3.rt.;import java.util.;import java.io.; import java.lang.reflect.;import com.sap.mw.jco.;
                                                                                    ^
    D:/usr/sap/X3A/DVEBMGS31/j2ee/cluster/server0/./temp/classpath_resolver/Map370955f0cc2311d8959a00d0b77fc64c/source/com/sap/xi/tf/_gwMsgRFC_msg_.java:30: package JCO does not exist
    Regards
    Jayanthan

    Hallo Jayanthan,
    I guess you have XI3.0;
    please check OSS note # 753294:
    Symptom                                                                               
    A message mapping contains a user-defined function that uses a class                      
    from the "com.sap.mw.jco", "sapxmltoolkit" or "com.sap.tc.Logging"                        
    library. An error stating that the source code contains syntax errors                     
    occurs when you test or activate the message mapping. When you use a                      
    class from "com.sap.mw.jco", the system reports, for example, "package                    
    com.sap.mw.jco does not exist".                                                           
    This error only occurs in systems containing a Support Package lower                      
    than 5.                                                                               
    Other terms                                                                               
    Mapping, JCO, logging, XML tools, compilation                                             
    Reason and Prerequisites                                                                  
    You must specify the libraries in the class path of the compiler.                         
    Solution                                                                               
    Import Support Package 5 or higher.                                                       
    You can use the following workaround as a short-term solution: Upload                     
    the library that is referenced in the message mapping into the software                   
    component of the message mapping as an "imported archive". Do not                         
    activate the "imported archive" with the library since it is not needed                   
    for the runtime. The only purpose of the archive is to allow the message                  
    mapping to be compiled. To avoid version conflicts with newer libraries,                  
    you should delete the archive again after you import Support Package 5                    
    or higher.                                                                               
    In your case this does mean you have to import the jar jrfc.jar which you find in the path
    [j2ee engine instalation directory]\cluster\server0\bin\ext\com.sap.mw.jco.
    Regards Franz

  • JCO - request response log file

    Hi
    I could not find log files of the Request and Response to ERP (using JCO). Anyone has idea where I could see the log?
    thanks

    I know in workbench of the XML output method - this is not what I am looking for. I have the XML request and response but I would like to see how MII sends this request and response
    From the Netweaver, I did what you suggested but I got an empty page. No logs.
    (show view Expert, display log dev_jrfc.trc)
    The reason I am asking is that I sent in a BAPI  with JCO (BAPI_MATERIAL_GETLIST ) note: at the end of the BAPI name is an empty space. In workbench when I generate sample, the Rquest and response has BAPI_MATERIAL_GETLIST_ .
    In XML Request it is written <BAPI_MATERIAL_GETLIST_> and the response is <BAPI_MATERIAL_GETLIST_--20>. The weird thing is I got the Material list that I required.
    So I would like to see what exacly being sent out  BAPI_MATERIAL_GETLIST_  or  BAPI_MATERIAL_GETLIST   and what actually the repy I got from ERP BAPI_MATERIAL_GETLIST or BAPI_MATERIAL_GETLIST_--20
    it could be a bug in MII 12.1

  • JCOerror: This system does not let you log on using a password

    Hi,
    "JCOerror: This system does not let you log on using a password"
    This is the error message I get from MII tries to connect to the Production ECC using my credentials to perform a BAPI call.
    These credentials work fine interactively (using the SAP GUI) and for BAPI calls from MII on SAP Development instances.
    I can interpret this message in two ways:
    - My login can not log on using password (though I can interactively)
    - The server does not allow logging on using password only. (It might require to pre-authorize the connecting server as well).
    I guess my question can be if this error requires adding additional rights to my login for the production environment, or if this is a global SAP setup for this system?  Or something else?
    In either way, what is required to have this work?
    Thanks.

    Hi,
    Kindly try the following options.
    Try executing the BAPI seperately in se37, using your login credentials.
    Check whether RFC is enabled for the BAPI.
    Check whether the SAP server is details are furnished correctly in "SAP Server"(available under "Data Services") editor.
    We can ensure this by checking the connection status link in xMII.(Link is available under "Data Services").
    If connection status is "Running" then SAP server setting configuration is fine. Else it is not configured properly.
    Try executing the BAPI in BLS(Business Logic Services) using JCO connector.
    I believe if any one of these scenarios fail then "Proxy Error" might thrown.
    Thanks
    Rajesh Sivaprakasam

  • Deployable cannot be retrieved from FILE_PROVIDER , stopping. Cause:com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Name or password is incorrect

    Hi All,
    After two years of CTS+ working without issue, in the last fortnight JCO_ERROR_LOGON_FAILURE has occurred. I have reviewed all the configuration  in document http://scn.sap.com/doc/DOC-30177, and it all looks fine. The user configured also checks out fine as well. The user id that is causing all the trouble is CTS_<SID>. We chose this option so we could determine which user in case of future issues. We have two development paths, Project and BAU. So at anyone time transports that have started in the BAU development system will need to be imported into the Project development system (using transport express) and vice versa.  Attached is the security authentication log from the system showing authentication failure. I have also checked the transport routes defined for the business systems in the SLD and these look fine as well. Roles assigned to the user are SAP_CTS_PLUS,
    SAP_J2EE_ADMIN, SAP_XI_CMS_SERV_USER, SAP_XI_CONFIGURATOR, SAP_XI_DEVELOPER, Z_CTS_PLUS_ADDITIONAL. I have also checked the permissions on the file at the operating system level.
    Any suggestions/advice gratefully received as this really has me scratching my head.
    Log:
    !REPOSITORY_ERROR_CHECK_STACKTRACE!
    [EXCEPTION]
    com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon) on DXI mshost strsap31
    at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:662)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1364)
    at com.sap.conn.jco.rt.ClientConnection.connect(ClientConnection.java:731)
    at com.sap.conn.jco.rt.PoolingFactory.init(PoolingFactory.java:103)
    at com.sap.conn.jco.rt.ConnectionManager.createFactory(ConnectionManager.java:293)
    at com.sap.conn.jco.rt.DefaultConnectionManager.createFactory(DefaultConnectionManager.java:46)
    at com.sap.conn.jco.rt.ConnectionManager.getFactory(ConnectionManager.java:262)
    at com.sap.conn.jco.rt.RfcDestination.initialize(RfcDestination.java:509)
    at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:533)
    at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:30)
    at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:603)
    at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:27)
    at com.sap.cts.jco.tms.TmsJCoAdapter.initializeJCo(TmsJCoAdapter.java:76)
    at com.sap.cts.jco.tms.TmsJCoAdapter.<init>(TmsJCoAdapter.java:57)
    at com.sap.cts.jco.EpsFileReader.<init>(EpsFileReader.java:76)
    at com.sap.cts.jco.EpsFileReaderController.doImport(EpsFileReaderController.java:90)
    at com.sap.cts.core.ImportManager.execImport(ImportManager.java:102)
    at com.sap.cts.ejb.DeployBean.execImport(DeployBean.java:170)
    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:597)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:47)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
    at com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:204)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:710)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:662)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:322)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:199)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:65)
    at com.sap.engine.services.webservices.servlet.SoapServlet.doPost(SoapServlet.java:61)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: RfcException: [null]
      message: Name or password is incorrect (repeat logon) on DXI mshost strsap31
      Return code: RFC_SYS_EXCEPTION(3)
      error group: 103
      key: RFC_ERROR_LOGON_FAILURE
    at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:219)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1331)
    ... 87 more
    Caused by: RfcException: [DXI|strsap31]
      message: Name or password is incorrect (repeat logon)
      Return code: RFC_SYS_EXCEPTION(3)
      error group: 104
      key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by DXI|strsap31
    at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:2034)
    at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:187)
    ... 88 more
    Caused by: com.sap.conn.rfc.exceptions.RfcGetException: Name or password is incorrect (repeat logon)
    at com.sap.conn.rfc.engine.RfcImp.ab_rfcerror(RfcImp.java:1157)
    at com.sap.conn.rfc.engine.RfcGet.rfcget_run(RfcGet.java:131)
    at com.sap.conn.rfc.engine.RfcGet.ab_rfcget(RfcGet.java:23)
    at com.sap.conn.rfc.engine.RfcRcv.ab_rfcreceive(RfcRcv.java:33)
    at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:1981)
    ... 89 more

    User id missing in client 000

  • SAPJSF user cannot log-on to the User Management Engine.

    We have a newly installed PI 7.0 system.
    SLDCHECK is succussful but if we go to the http://hostname:50100/sld - we are redirected to http://hostname:50100/logon/logonServlet?redirectURL=%2Fwebdynpro%2Fdispatcher%2Fsap.com%2Ftc%7Esld%7Ewd%7Emain%2FMain
    When we check the default.trc file, we see the error: User "SAPJSF" is the communication user for the connection between User Management Engine and the ABAP backend system SIDCLNTxyz. This user cannot log-on to the User Management Engine.
    The SAPJSF user is not locked in SU01.  This user is used by the JCO providers to connect to the gateway service.
    We opened Visual Administrator and navigated to Server0 -> Services -> UM Provider
    We changed the password  property at ume.r3.connection.master.passwd
    We then restarted the ABAP and J2EE engine.  But we still see this error.
    Any help to solve this issue is appreciate.
    Jay Malla

    Hi,
    Please, refer the link below. It says you cannot logon with SAPJSF user to J2EE engine for security reasons.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/4e/225b42eeb66255e10000000a155106/frameset.htm
    Thanks
    R.Murali

  • Adaptive RFC 2 gives error: com/sap/ide/jco/service/internal/R3Service

    Hi,
    I've run into the following problem about NWDS. This happens as I create a Model. It appears there is a new version of the Adaptive RFC Model, which is called Adaptive RFC 2 Model.
    1. Right click on Models, and select Create.
    2. Double Click on Adaptive RFC 2 Model
    3. The error pops up. It says "An error has occurred. See error log for more details. java.lang.NoClassDefFoundError". Then if you click details you get "An error has occurred. See error log for more details. com/sap/ide/jco/service/internal/R3Service "
    If you know which log to have a look, or what this error is about please let me know urgently. Any help if much appreciated.
    Thanks,
    Ogeday Isiklar

    Hi,
    I am also getting same problem. Waiting for solution
    Regards,
    Pradeep Kumar

  • Java.lang.NoClassDefFoundError:Couldnot initialize class com.sap.mw.jco.JCO

    Hi,
    I am having an issue with SAP adapter configuration. It throws below error in log files :
    java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
    JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjcorfc in java.library.path]. java.library.path [opt/apps/Oracle/jdk160_14_R27.6.5-32/jre/lib/i386/client:/opt/apps/Oracle/jdk160_14_R27.6.5-32/jre/lib/i386:/opt/apps/Oracle/jdk160_14_R27.6.5-32/jre/../lib/i386:/opt/apps/Oracle/patch_wls1032/profiles/default/native:/opt/apps/Oracle/patch_jdev1111/profiles/default/native:/opt/apps/Oracle/jdk160_14_R27.6.5-32/jre/lib/i386/client:/opt/apps/Oracle/jdk160_14_R27.6.5-32/jre/lib/i386:/opt/apps/Oracle/jdk160_14_R27.6.5-32/jre/../lib/i386:/opt/apps/Oracle/patch_wls1032/profiles/default/native:/opt/apps/Oracle/patch_jdev1111/profiles/default/native:/opt/apps/Oracle/wlserver_10.3/server/native/linux/i686:/opt/apps/Oracle/wlserver_10.3/server/native/linux/i686/oci920_8:/opt/apps/Oracle/wlserver_10.3/server/native/linux/i686:/opt/apps/Oracle/wlserver_10.3/server/native/linux/i686/oci920_8:/opt/apps/Oracle/Oracle_SOA1/soa/thirdparty/edifecs/XEngine/bin:/opt/apps/Oracle/Oracle_SOA1/soa/thirdparty/edifecs/XEngine/bin]
    java.lang.NoClassDefFoundError: Could not initialize class com.sap.mw.jco.JCO
    Invoking SAP targets from bpel or iwafjca test servlet fails with "java.lang.NoClassDefFoundError: Could not initialize class com.sap.mw.jco.JCO."
    I am able to connect from Application Explorer(AE) and browse through idocs and bapis. I tried to check the class loading pattern for AE using Jconsole :
    1. Started the AE
    2. /opt/apps/Oracle/jdk1.6.0_19/bin/jps
    15279 BseFlashScreen
    3. /opt/apps/Oracle/jdk1.6.0_19/bin/jconsole 15279
    Enabled verbose output on class loading page and connected to SAP target from AE
    4. The verbose output shows below :
    Loaded com.sap.mw.jco.JCO from file:/opt/apps/Oracle/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib/sapjco.jar
    I have added the above path to my LD_LIBRARY_PATH
    LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/${arch}:${MW_HOME}/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib:${MW_HOME}/user_projects/domains/base_domain/lib:${WL_HOME}/server/native/linux/${arch}/oci920_8
    I also added the path to WEBLOGIC_CLASSPATH in commEnv.sh file.
    The sapjco.jar, libsapjcorfc.so and librfccm.so files are also available under below directories
    WL_HOME/server/lib
    MW_HOME/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib
    MW_HOME/user_projects/domains/base_domain/lib
    Any suggestions will be really helpful.
    Regards
    Subhankar

    Hi Manoj,
    I have added the libsapjcorfc.so and librfccm.so files to below locations:
    WL_HOME/server/lib
    MW_HOME/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib
    MW_HOME/user_projects/domains/base_domain/lib
    And also set the LD_LIBRARY_PATH and WEBLOGIC_CLASSPATH in commEnv.sh file.
    Eg:
    LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/${arch}:${MW_HOME}/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib:${MW_HOME}/user_projects/domains/base_domain/lib:${WL_HOME}/server/native/linux/${arch}/oci920_8
    Is there any other location where these need to be added ? I hope library path/system path refers to the WEBLOGIC_CLASSPATH ?
    Regards
    Subhankar

  • SSO between EP and ECC-- JCo RFC Provider- Error-- JCO_ERROR_SERVER_STARTUP

    Hello Everyone
    I am setting Up SSO between my EP 7.0 and my ECC 6.0 system. During the phase JCO RFC PRovider i am giving the following values:
    The following was done;
    1. start Visual Administrator -> Service : Choose JCo RFC Provider
    2. Created JCo RFC provider:
    Program ID: SAPJ2EE_Port
    Gateway host: EPDEV ( host of my EP System)
    Gateway service: sapgw00
    Server Count 5
    Application Server Host: ERP6 ( Host of my ECC System)
    System Number: 00
    Client: 000
    Language: EN
    User: SAPJSF
    Password: ..
    When i click on SET i am getting the error " ERROR When ADDING TO BUNDLE" Check LOG FOR DETAILS".
    I checked the DEFAULTTRACE.TRC and get the following MEssage :
    Date , Time , Message , Severity , Category , Location , Application , User
    03/01/2011 , 3:33:30:101 , Error changing bundle SAPJ2EE_PORT , Error , /System/Server , com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(BundleConfiguration conf) ,  , Administrator
    03/01/2011 , 3:33:30:085 , com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Mar 01 03:33:30 PST 2011.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=SAPJ2EE_PORT GWHOST=EPDEV GWSERV=sapgw00
    ERROR       partner 'EPDEV:sapgw00' not reached
    TIME        Tue Mar 01 03:33:30 2011
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     1
    I have configured my SLD as well. Any suggestions. Please Advise.

    Hi Ahmed,
    Please do check the validity of the certificate.
    Please do cross check these steps again.
    1.     Transaction u2013 STRUSTSSO2 (Trust Manager for Logon Ticket)
    2.     Double Click Owner certificate. It gets reflected under the certificate tab.
    3.                  Choose Format Binary
    4.                  Choose File Path.
    5.                  Enter the File Name
    6.                 saved in local drive.
    You can import into portal as x.509 certificate.
    check this thread -
    Certificate no longer has signature (use restriction)
    Renew certificate via SAP MarketPlace, and install from tcode slicense.  If you are working on a trial version, there is a SAP license request application form. Fill the form with the hardware key. you will get the new license via email. Install using slicense. Then try exporting the certificate.
    Thanks,
    Divya
    Edited by: Divya V on Mar 10, 2011 11:25 AM

  • JCo 3.0 connectivity issues between Java application on NWCE and ERP

    Requirement: We have a Java application that would run on NWCE. This application will be invoked from ERP/SAPGUI via HTML Controller. With SSO enabled, the goal is to pass ERP credentials to CE application. This CE application in turn will use ERP credentials from Logon ticket to connect to ERP and invoke BAPI calls (JCo 3.0 destination)
    System Information:
    CE System: SAP NW CE 7.2 SPS 04
    ERP: SAP ECC 6.04
    Both systems are trusted using X.509 certificates
    Current scnerio:
    1) Destination (CE to ERP) - JCo 3.0 using Authetication method of u201CCurrent User (Logon Ticket)u201D
    - Web application is unable to find the JCo 3.0 destination.
    2) Destination (CE to ERP) - JCo 3.0 using Authetication method of u201CTechnical Useru201D
    - Web application is able to find the JCo destination
    Any assiatance in resolving the issues would be appreciated ....
    Trace Log:
    #2.0 #2011 01 19 14:44:38:756#+0100#Error#com.sap.security.core.server.destinations.provider.DestinationsProviderFrame#
    com.sap.getDestinationProperties()#BC-JAS-SEC#tcsecdestinations~provider#001F2960BE89048C0000000100005BC1#16777250000000004#sap.com/TestJcoWebEar#com.sap.security.core.server.destinations.provider.DestinationsProviderFrame#10207625#182##4286395D23D211E08BA2000001000022#d981f18323b011e0b5eb000001000022#d981f18323b011e0b5eb000001000022#0#Thread[HTTP Worker [@2002275007],5,Dedicated_Application_Thread]#Plain##
    ASJ.dest.pr0023#

    Hi Hemandra,
    This is the Full error message i am getting
    Message:   ASJ.dest.pr0023
    Severity:   Error
    Date:   2012-02-09
    Time:   21:37:25:134
    User:   SUPPLIER
    Category:   /System/Security
    Location:   com.sap.security.core.server.destinations.provider.DestinationsProviderFrame
    Application:   XXXXXXXXXXXXXXXXXXXXXX
    Thread:   Thread[HTTP Worker [@254542764],5,Dedicated_Application_Thread]
    Data Source:   j2ee/cluster/server0/log/system/security.log
    Arguments:   
    Passport User Activity ID:   1d2dfea9533811e1adf3000000dc2fc6
    Message ID:   com.sap.getDestinationProperties()
    Session:   11
    Transaction:   
    Time Zone:   +0530
    Customer Message Component:   BC-JAS-SEC
    Runtime Component:   tcsecdestinations~provider
    Correlation ID:   14430150000000004
    Passport Session:   8703D330533611E19565000000DC2FC6
    Passport Connection:   1d2dfea9533811e1adf3000000dc2fc6
    Passport Connection Counter:   0
    Host:   XXXXX
    System:   XXX
    Instance:   J01
    Node:   server0
    Log ID:   C000AC10088100FF0000000000002BF1
    Regards,
    Srinivas

  • JCO-Java application unable to open a Frontend GUI session

    Hello,
    <P>
    I am having a problem opening a GUI session on a client PC through the JCo java call. It works on some PC's when I am logged in, but not on my PC. But other persons who login on my PC do not have a problem with the application opening a GUI session. I am at a loss. I have had a basis consultant look into this and he could not find a reason for the problem. I have submitted a customer message to SAP and am being told to file this issue in the forum, so here it is. If this is the wrong forum, please let me know which forum would be the correct one.
    </P>
    <P>
    Problem:</br>
    For test purposes, I have created a Java application using the SAP standalone SAPJCO3 vers. 3.0.1. The R/3 backend is 4.6C. The SAPGui version is 7.1 patch level 13 installed on a Windows XP Pro client PC. The application is supposed to start a Frontend GUI session as part of the initial process. This is not working on all PCu2019s for all users. The following are scenarios for two different users on two different PCu2019s, logged on and executing the Java application. The parameters for the Java application are: User, Password, and System Id in this order on the command line after the Java applicationu2019s name. The system Id in our example is PRP in uppercase. This problem happens while connecting to any of our R/3 instances.
    </P>
    <P>
    Testing of the issue:</br>
    Scenario 1:</br>
    User gmcghie: This user is the primary user of his/her PC. This PC has not had its registry entries cleaned up for a long time. Starting the Java application from the Windows command line with the supplied parameters, the program is executed and makes the initial connection with the R/3 backend. When the R/3 system sends back a request to start the GUI session, the SAP Logon is executed and opens on the PC. Nothing seems to happen after this.
    <P>
    Here is the JCO exception from the log file:
    JCoException eDest: (136)com.sap.conn.jco.JCoException: (136) JCO_ERROR_ILLEGAL_STATE: Launching SAP GUI failed, though it was requested (error message: Communication with SAPGUI timed out)
    </P>
    <P>
    When you right click on the SAP Logon icon that is in the Windows System Tray on the PC you see an entry that shows a session for Client 000. This is the wrong client being called by the application. The client being called is 600 in this particular scenario.
    </P>
    <P>
    Here is the connection string sent to backend for scenario 1:</br>
    TYPE=A DEST=PRP USER="gmcghie" PASSWD=********** CLIENT=600 LANG=E ASHOST=10.212.120.53 SYSNR=00 TRACE=1 PCS=1 USE_SAPGUI=2
    </P>
    <P>
    Scenario 2:</br>
    User mshin: This user is the primary user of his/her PC. This PC has had the OS re-installed on it within the last few years, hence the registry is likely more clean. Starting the Java application from the Windows command line with the supplied parameters, the program is executed and makes the initial connection with the R/3 backend. When the R/3 system sends back a request to start the GUI session, the SAP Logon is executed and opens on the PC. The connection is made to Client 600 and the process ends. The screens that appear above for the other scenario are not present when the connection is successful. The log file is not included for this as it was empty because it succeeded.
    </P>
    <P>
    Here is the connection string sent to backend for scenario 2:</br>
    TYPE=A DEST=PRP USER="mshin" PASSWD=********** CLIENT=600 LANG=E ASHOST=10.212.120.53 SYSNR=00 TRACE=1 PCS=1 USE_SAPGUI=2
    </P>
    I have the same issue on my PC as the first scenario.
    <P>The steps I took to try to get this to work are as follows.</br>
    1. Un-installed and re-installed the SAPGui, several times with no change.</br>
    2. Compared the registry settings of SAPGui between working and non-working PCu2019s. These were essentially the same.</br>
    3. Compared the system variables between working and non-working PCu2019s. These were essentially the same.</P>
    It should also be noted that if user u2018gmcghieu2019 from scenario #1 logs into another PC, the program executes correctly (for most other PCs but not all). Finally, if user u2018mshinu2019 from scenario #2 (certain other users as well) logs into Windows on the primary PC for user u2018gmcghieu2019 from scenario #1, and user u2018gmcghieu2019 is used to connect to SAP using the Java program, the program executes correctly. It seems that this would indicate some problem with the useru2019s Windows account on certain PCs.</P>
    Why is the connection information being dropped? How is the process of opening the SAPGui on the frontend done?</P>
    Any help with this issue is greatly appreciated.</P>
    Thanks,</br>
    Mark Shirkey

    Created Customer Message and got answer. There were settings in Windows Registry for starting the SAP Logon Launch Pad which had to have a value of 1.

  • Buttons not enabling for JCO Creation in SLD

    Hi Experts,
    When i logged in into my Webdynpro Content Administrator with administrative rights, all the button like Create JCo Destination, Maintain JCo Destination and Start assigned SLD are getting disabled expect Check SLD Connection Button.
    Moreover, displaying a message : "Connection to System Landscape Directory (SLD) could not be opended successfully." at the bottom of the screen.
    When i click on the Check SLD Connection Button and then Test Connection, it gives again the same message i.e "Connection to System Landscape Directory (SLD) could not be opended successfully."
    Now, When i click on the Check SLD Connection Button and then Start SLD, SLD server is staring and running.
    Another thing is, When i am starting my sld server from logging in into http://<hostname>:<port>/sld, SERVER status is running. I stopped it and again started, then it is starting, but giving an error message as:
    "Failed to send start signal for complete cluster, SLD may still be stopped on other cluster nodes."
    When saving any parameters like profile information, it is not saving and saying error as:"
    Cannot save profile settings CIM_ERR_FAILED: Failed to initialize cluster notification sender."
    My setting are correct in SLD Data Supplier in Visual Administrator. I had filled the host/port/user/password information for both "HTTP Settings" and "CIM Client Generation Settings".
    It went worked well earlier, i come across this problem recently with my sld.
    Another thing that i noticed is when i click on the "CIMClient Test" button, its getting an error message saying "Failed to Generate and Test CIMOMClient Object". But, ealier it came as successfull.
    I have full authorization to use admin tools.
    What might be the problem.
    any help must be appreciated.
    regards
    sunil kumar

    Hi Sunil,
    We just had this issue couple of days before, this has to do with the JMS Provider Authorization. We did the following steps to solve our issue:
    I. Default security configuration of JMS resources is in place (this is by far the most common scenario) and named anonymous users have been created.
    Change the mapping of the "clients" jms role as follows:
    1. Start the Visual Admin
    2. Browse the tree in the left pane
    <SID> -> Server 0 -> Services -> Security Provider
    3. The "Policy Configurations" tab should be selected by default on the right hand side
    4. Select the "service.jms.default.authorization" node from the "Components" list (should be the nineth entry from the top down)
    5. Select the "Security Roles" tab
    6. Select the "clients" node from the security roles list
    7. You should see on the right hand side "Security Roles" list in which the "guests" node is marked
    8. Switch to edit mode by pressing the change button on top (pencil icon). The "Modify" button should now become active
    9. Press the "Modify" button
    10.Select the "all" entry from the "Security Roles" list. The "Groups" pane should show one entry named "Everyone"
    11. Press the "Save" button
    12. Restart the cluster so that JMS and applications using it can reliably reinitialize.
    Check
    Note 971249 - JMSServerSecurityException thrown accessing JMS resources
    for more details.
    Hope this helps!
    Regards,
    Preetha Rethinam

Maybe you are looking for