Com.sap.mw.jco.JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND:

Hi All,
I am getting this error while communicating with the back-end BAPI. It says that Field IT_RETURN not a member of TABLES
com.sap.mw.jco.JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND: Field IT_RETURN not a member of TABLES.
Please note that I understand that this erro might come when we do not have required return structure in the BAPI. However I have debugged both the backend R/3 and frontend J2EE code and I am sure from backend BAPI is returning this structure.
To add to my surprise, I am not facing this issue every time. Sometimes this works perfectly fine without giving any error. I am suspecting this to be a communication issue between two layers.
Please suggest your inputs how should I move further to fix this issue.
Regards,
Pravesh

Hi,
Open your RFC in ABAP editor.
Check the import parameters.
Compare them to what you are passing from your JCO call.
You will find the mismatch.
For further reference refer the document [How to Handle Import and Export Parameters of ABAP Function Module (RFC Enabled) In Java|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/608391c6-dc79-2c10-2c8c-c72861822b12?QuickLink=index&overridelayout=true]
Hope this helps!!
Best Regards
Vijay K

Similar Messages

JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND

all experts:
met a question about calling rfc through jco,the following is the detail:
wrote RFC code,parameters are two table,but calling them in JCO,display error:
ex =com.sap.mw.jco.JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND: Field Zxxxx not a member of TABLES
com.sap.mw.jco.JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND: Field Zxxxx not a member of TABLES
what is reason for this message,please help me.
thanks.
Best Regards.
Vera PANG.

Open your RFC in ABAP editor.
Check the import parameters.
Compare them to what you are passing from your JCO call.
You will find the mismatch.
For further reference refer below doc :
[Link|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/608391c6-dc79-2c10-2c8c-c72861822b12?quicklink=index&overridelayout=true]

JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND: ES_BDGT_EXT not a member

Hi Experts,
I am doing some enhancement on existing PDK applications.
and there is a need to change Function module's signature (import, export parmaters)
after making changes there when i try to read values of those fields in java program, i am getting this error.
all the values from changes in existing parameters are getting read in program but newly defined or added EXPORT parameters are not getting read.
tried with invalidating caches also but no help .
when i read outputParameters.getFieldCount() + "," + outputParameters.getNumFields(); it also returns me count as number of parameter as they were earlier rather an updated count.
Any hints?
Regards
Subhash

hi,
still in same case check this the source of message
and what to do
http://help.sap.com/saphelp_nw04/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
bvr
Edited by: bvr on Jan 15, 2009 10:32 AM

SSO issue in the production server,com.sap.mw.jco.JCO$Exception: (103)

com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: This system rejects all logons using SSO tickets
in the production server.....
while testing the jco maintained for Ess applications.
if i go for uidpw method for modeldata destination i am getting the error. in the Ess pages that administrtor not in this peroid(administrator with which id i maintained jco destination)
if i assign one employee to the admin in pa30......for every employee getting the same details of admin)
I guess this problem with modeldata ......i should maintain the usermanagement method for modeldata jco destination is logon ticket.
while maintainig that ping is successfull but getting the above error.
it is the problem with production server.......of E.P
in dev and quality everything is working fine.
plz help me out.
thankyou
swapna

Hi Swapna,
Please check the logon group properties for SAP system in t-code SMLG. If there is any issue with logon group then it might cause for this issue.
Refer to [Click here|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/7.0/portal%20integration/how%20to%20configure%20the%20jco%20destination%20settings.pdf] and [System Landscape Directory Process and JCo Configuration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?QuickLink=index&overridelayout=true]
Hope it will helps
Regards, Arun Jaiswal

Com.sap.mw.jco.JCO$Exception:JCO_ERROR_XML_PARSER

Hi all,
I try to send data from RFC to XI, but I get error in adapter like :
After a value an end tag must follow. That did not happen in "ATTR_SET>- Error: 2006-08-10 11:12:56 GMT+02:00: com.sap.mw.jco.JCO$Exception: (130) JCO_ERROR_XML_PARSER: After a value an end tag must follow. That did not happen in "ATTR_SET>-
I use 3 tables(deep structures)...
Anybody any idea?
Thanks

Thanks for your rapid answer
Very funny thing - after I made cold backup (stopping XI) it started to work(I saw my XML in SXMB_MONI), but when I did this the next time(adding fields to my RFC) the same happened...
Full cache refresh didn't solve the problem...
Any idea?
Thanks a lot

Setting up web Bex in BWsystem:error com.sap.mw.jco.JCO$Exception:Issuer of

Dear SAP Gurus,
I'm facing an error when seting up web Bex in BW system which is based on AS java patch 14 when i run Diagnostics & Support Desk Tool as described in Note 937697 there is only one red signal which is BI Mastersystem
the error is
RFC connection using properties in Portal System Landscape to ABAP backend has failed. Reason:
com.sap.mw.jco.JCO$Exception:Issuer of SSO ticket is not authorized
thanks in advance
Rgds
George Varghese

thanks Deepika ,unfortunately I posted this a Long back ,time limit was very less ,we were not in a situation to do more R&D on that,it will be a Waste of time ,what I did is that I uninstall ed SAP and installed again with latest available Patches and we were succeed
thanks
George Varghese

Failure in Model Create Step: com.sap.mw.jco.JCO$Exception: Missing R3NAME=

Hi,
I am running NW04sp10 and am trying to connect my WebDynPro to my R/3 backend app server - am running through the FlightChecking example using DevStudio 2.0.10.
Have successfully created my meta + app data JCo's, they test and ping OK from the Content Manager. SLD is fine, connecting happily to the NW and R/3 boxes. One is message server, one central instance.
When the 'create model' wizard tries to build the java proxies though, it comes back with this:
[Fatal]:     com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
Can anyone help?
Cheers guys,
Andy

Hi Wael,
I'm using the tutorial 'Handling Transactions with BAPIs in Web Dynpro' [part of SAP Online Help].
The BAPI does work in se37, it's just a standard SAP delivered BAPI, and I've tried a few different ones to make sure it wasn't a BAPI specific problem.
In the content admin I've navigated through the local/FlightChecking/Applications/FlightCheckingComp and then used the wizard to add the 2 JCOs [I've kept the default names for now after your previous advice]
The data is like this:
WD_MODELDATA_DEST:
Name                  WD_MODELDATA_DEST
Client                800
J2EE Cluster Name     NW1 on chippy
USER                  USER1
Password              <password>
Application Server    nero
System ID             00
WD_RFC_METADATA_DEST:
Name                  WD_RFC_MODELDATA_DEST
Client                020
J2EE Cluster Name     NW1 on chippy
USER                  USER1
Password              <password>
Application Server    chippy
System name           NW1
Logon Group           PUBLIC
My landscape here is of 2 servers:
'Nero'    SAP r/3 4.7 Application Server System ID ACI
'Chippy' SAP WebAS640 NW04 System ID NW1 ABAP+J2EE stack
The JCOs 'test' and 'ping' successfully. My WD_RFC_METADATA_DEST connection is to a message server, the WD_MODEL_DEST is to a central instance.
Here's the full log from the create model wizard [I used a random BAPI for testing, BAPI_GET_PAYSLIP, so don't worry about that]:
[Warning]:     Creating a connection with Metamodel language <en_GB> failed. Continuing with language <EN>
[Fatal]:     com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
[Info]:     Creating Model: FlightChecking
[Info]:     Creating Model Class: Bapi_Get_Payslip_Input
[Info]:     Creating Model Class: Bapi_Get_Payslip_Output
[Info]:     Creating Model Class: Bapireturn1
[Info]:     Creating Model Relation: Bapi_Get_Payslip_Output:Return
[Info]:     Creating Model Class Property: Type
[Info]:     Creating Model Class Property: Id
[Info]:     Creating Model Class Property: Number
[Info]:     Creating Model Class Property: Message
[Info]:     Creating Model Class Property: Log_No
[Info]:     Creating Model Class Property: Log_Msg_No
[Info]:     Creating Model Class Property: Message_V1
[Info]:     Creating Model Class Property: Message_V2
[Info]:     Creating Model Class Property: Message_V3
[Info]:     Creating Model Class Property: Message_V4
[Info]:     Creating Model Class Property: Employeenumber
[Info]:     Creating Model Class Property: Payslipvariant
[Info]:     Creating Model Class Property: Sequencenumber
[Info]:     Creating Model Class: Bapi7004_Payslip
[Info]:     Creating Model Relation: Bapi_Get_Payslip_Input:Payslip
[Info]:     Creating Model Class Property: Format_Col
[Info]:     Creating Model Class Property: Text_Col
[Info]:     Creating Model Relation: Bapi_Get_Payslip_Output:Payslip
[Info]:     Creating Model Relation: Bapi_Get_Payslip_Input:Output:Bapi_Get_Payslip_Output
So it seems to actually be able to retrieve the metadata for the BAPIs, but not to make the relevant JCo's. I've not gone on and completed the tutorial, assuming it won't work until I can sort out the above 'fatal' error.
Thanks again for all of your good advice.
Cheers,
Andy

Com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP

For reason to change server IP address,
EP: 192.168.2.21 to 192.168.2.41
BW:192.168.2.22 to 192.168.2.42
and fix system by steps:
1,logon bw system,using tcode sm59 to modify tcp/ip connection.
2,logon ep system using visual administrator,and modified jco parameters.
3,logon ep system using ie,and modified sld,datasupplier.
4,restart bw and ep system.
after changed,the BEx Web did not work,
enter Maintain Jco destination
select jco destination: mete_data
click test
raise the error:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=B MSHOST=bw GROUP=public R3NAME=BW1 MSSERV=sapmsBW1 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '192.168.2.22:sapgw00' not reached TIME Tue Dec 18 15:39:34 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nibuf.cpp LINE 4601 DETAIL NiBufIConnect: connection pending after 60000ms SYSTEM CALL connect ERRNO 55 ERRNO TEXT A connect operation on a socket is not complete. COUNTER 1
would someone tell me how to resolve this problem.
regards

Hi,
It seems that the SAP gateway host is deactivated or the TCP/IP port 33xx (where xx corresponds to the system number) is not open.
First try pinging <IP address>. If there is no reply, then Boot SAP Gateway host required.
Check whether the TCP/IP port 33xx is open (where xx corresponds to the system number) and start the SAP gateway
The TCP/IP port is also partially defined in the services file as an sapgw<SID> or sapgwxx entry (where xx corresponds to the system number). The services file is in the Windows directory or in WinNT/System32/drivers/etc.
Hope this helps.
Regards
Srinivasan T

Failed to transform XML-RFC to RFC:com.sap.mw.jco.JCO$Exception: (130)

Hi All,
I am working on Rfc-SOAP scenario.
I am getting error in SAP, there is no error in SXMB_MONI, responce is successfull and correct from SOAP.
In SAP Dump is saying following
Runtime Error CALL_FUNCTION_REMOTE_ERROR
Date and Time 08/07/2007 09:14:14
"failed to transform XML-RFC to RFC:com.sap.mw.jco.JCO$Exception: (130)
Please guide
Regards

Hi Rohan !!
Check this threads:
- /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
- CALL_FUNCTION_REMOTE_ERROR
to see if you have correctly configured the RFC Sender, and the possible cause of error.
Regards,
Matias.

Com.sap.mw.jco.JCO$Exception starting the J2EE server 620

We are using J2EE 620 pl26, with the latest JCO, but often trying to acces the J2EE services like Mobile Engine Webconsole 21 or the WebEnabled Sapconsole 640 we recive the message:
'Dispatche runningbut no server connected'.
The J2EE dispatcher and server are started at Sap startup. Just after that time the J2EE is working fine, but after some time the J2EE server get down.
We found this message into the J2EE console_logs:
"RFCEngine: Server startup error, stopping "SAPProfile:F:\usr\sap\CAM\SYS\profile\CAM_DVEBMGS00_itmif089" :
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Fri Oct 15 09:58:20 CEST 2004.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 2 seconds.
Could not establish the lcom accepted connection: lcomListenCreate failed with rc 9"
We do not find any Oss notes for that.
Any advise is wellcome.
Regards

Hi Mauro,
normally when you apply a new SAP Kernel a frfclib.sar file is delivered. This frfclib file need to be copied to the J2EE directory /os_libs and need to be extracted there. This frfclib version must always match to the SAP Kernel version.
Ciao
tc

Com.sap.mw.jco.JCO$Exception: How to resolve this ???

Hi all
I am facing the following error while the Portal Loads the Logon Page.
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Dec 20 15:55:17 GMT 2005.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect_PM TPNAME=SAP.CCMS.J2EE.XPD, GWHOST=box4.manor.sap.point, GWSERV=sapgw00
ERROR internal error
(this retcode should be handled by caller of NI-layer)
TIME Tue Dec 20 15:55:16 2005
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -8
MODULE nixx.c
LINE 666
COUNTER 28
FYI :
1. I have customized the LOGON PAR
2. Imported a new Package into the Logon JSP file
3. The imported new Package has been added in the Class Build Path of the PAR Project
4. The Imported Package does the JCO connection and disconnection
Thanks
Kay

Hello Kay,
have you checked you services file for an Entry with
3300/tcp sapgw00
Regards
Gregor

Com.sap.mw.jco.JCO$Exception: Group NSPLOGON not found

Hi All,
I was trying to access a RFC from R3. While trying to create a JCO in SLD. Got the following error.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=minisap GROUP=NSPLOGON R3NAME=NSP MSSERV=sapmsNSP PCS=1 ERROR Group NSPLOGON not found TIME Tue Oct 19 22:43:38 2010 RELEASE 720 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 4575 DETAIL LgIGroupX COUNTER 1
Initially i was not able to find any Logon Group for the server. (Transaction - SMLG). I created a Logon Group and saved it. But while trying to test the connection, it is throwing this error.
Is there any step missed out in this. Please do help me in resolving this error.
Thanks and Regards,
Divya

Solved by myself.
Divya

Error: com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: Open file 'C:

We are seting up new initial loads for our quality system and we have setup up the repositories. When we try to load the initial load for SAP quality system we get the below error in all the readin pass's.
I am able to connect to PROD and DEV systems but i only have problem in QA system.
Error Initializing SAP connection with parameters:
com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: Open file 'C:\WINDOWS\sapmsg.ini' failed
Error Init failed
Did i miss something due to which we are getting error's.
Edited by: ARUN KUMAR AKUTHOTA on Sep 1, 2011 9:40 PM

Thanks Martin for your reply. I am not testing these in SAP IDM Quality environment.
When i connect to SAP PROD or DEV systems to QA IDM i am able to pull the needed information.
When i do the same to SAP QA systems i cannot do that and i get the above error.
I have also searched this file in PROD and QA and i dont see this file existing in the system.

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

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.

Com.sap.mw.jco.JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND:

Similar Messages

Maybe you are looking for