ESS JCO ERROR

hai frends
iam configuring ESS in ep.while doing this process in JCO connections for
ex:
SAP_R3_SelfServiceGenerics
SAP_R3_SelfServiceGenerics_MetaData
in first step it is asking for Destination Name and client .
for this it aouto matically the name is comming and for the client iam giving my sap client number .
after configuring JCO connections i tryed test connection . but it is giving error.
like
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed
what is this error and how to solve this error.
i tryed in many ways.
iwas check all the parameters .
like services and host files in both the servers. all these parameters are correct.
and is there any need to create RFC destinations to create in EP server and ECC.
pls help me on this .

hope u added the host name in hosts file in drivers
and the bold and underline one add in the services file in drivers folder with messaging port no
like this
"sapmsE6D 3600/TCP"
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=flag-projects GROUP=SPACE R3NAME=D50 MSSERV= sapmsD50 PCS=1 ERROR The message received isn't from a message server. Are you really connected to the message server? Please check your connection parameters. (flag-projects / sapmsD50) TIME Fri Feb 6 11:03:45 2009 RELEASE 700 COMPONENT MS (message handling interface, multithreaded) VERSION 4 RC -29 MODULE msxxi_mt.c LINE 2543 COUNTER 2
bvr
Edited by: bvr on Feb 6, 2009 6:40 AM
Edited by: bvr on Feb 6, 2009 6:41 AM

Similar Messages

ESS / MSS Error..

Hi All,
I have created all JCO destinations and when i test them , the result is successful
But once i click on ess/mss tab in portals, i get the error..
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_HumanResources_MetaData' in the SLD. No such JCO destination is defined in the SLD.
But i have maintained SAP_R3_HumanResources_MetaData in the SLD.. Actually i have two SAP_R3_HumanResources_MetaData services one is active and another is inactive..
For SAP_R3_HumanResources -- i have used "Logon Ticket" and for SAP_R3_HumanResources_MetaData -- used userid & pwd.
Actually i have to do UserMapping as my portal userid and R/3 userid are different.. Then in this case am i creating JCO destinations correctly.. If not how to do..
Please throw some light into this problem by your valuable suggestions.
Thanks & Regards,
Mahesh.M.R

Hi Mahesh,
Please go through the following thread.
ESS configuration error>
Just might prove useful to you.
Cheers,
Vivek
PS : Please reward points if found useful.

Error while deploying the aplication-jco error

Hello Experts,
i know   thousends of questions in jco error. I have followed that threads , still i am getting an error.
Plz help me out from that error.
My EP server is running on was 6.20,
and xi server is running on was 6.40.
what i have done:
I have downloaded fightslist application from sdn.
i have deployed that application to was 6.40.
i created one technical system for abap.
i configured sld.
i entered service name(sapms147 3600/tcp(this is ides(4.7) serversid and port)) in servicefile in was 6.40 machine.
when maintaing jco connections the following error has come:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=mlbpsap06 GROUP=PUBLIC R3NAME=I47 MSSERV=sapmsI47 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service 'sapmsI47' unknown TIME        Fri Dec 01 15:27:10 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -3 MODULE      ninti.c LINE        494 DETAIL      NiPGetServByName2: service 'sapmsI47' not found SYSTEM CALL getservbyname_r COUNTER     7
My doubts are:
1.where i have to enter service i.e which machine (6.40 or 4.7 machine).
2.while creating technicalsystem which product i have to choose).
3while creating jco connection
    whichone i have to choose either dictinory mata data or applicationdata.
    in message server connection which user id & password i have to give means 4.7 userid or xiserver userid & password.
Plz helpme out from this.
Thanks in advance.

Hello Sai,
NWDS is local means which machine i am using.
My EP 6.0 SP2 in 172....202 but it is reunning on was 6.20.(mlbpsap02)
and here was 6.40 ip is 172.....203 IP ,but XI is installed on this server)(mlbpsap03)
and R/3 ECC ip is 172......201.(mlbpsap01)
no sneak preview edition and all.
I have downloaded application(sample flight) in webdynpro.
and i configured sld in 203(cim test connection is successfull) ip.and also entered the service name(sapmsecc 3600/tcp).After entering the service name i restarted the server
and created technical system for abap (and here selectiong products ecc components are not there.)
in webdynpro content admin while maintaing jco , the above error is coming.
i am unable to find where the problem is
the main thing is ep is not in was 6.40
further what i do
and where i enter the host ip and aliases.

Org.apache.jasper.JasperException; JCO error when Importing SAP Roles in C

Hello experts,
I have installed BOXI 3.1 SP3, Integration kit SP2, BW/BI 7.0 and ECC 6.0 on Windows 2008/64bit.
My goal is to import the roles into CMS from SAP BW/BI but getting the follwoing errors:
JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc
C:\Windows\SysWOW64\sapjcorfc.dll: Can't load AMD 64-bit .dll on a IA 32-bit platform.
java.library.path [C:\Windows\SysWOW64\;D:\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\]
org.apache.jasper.JasperException
I followed the note 1292144 - JCO error when Importing SAP Roles in CMC,but unfortunately without success.
I installed SAP JCo Release 2.1.9 (64bit)
Best regards
Lutz
Edited by: Lutz Heinrich on Aug 12, 2010 4:17 PM

Install the 32bit version of the Java connector. BOBJ is 32bit so even on 64bit Windows you need the 32bit version of the Java Connector.
Regards,
Stratos

JCo error when calling from webmethods sap adapter to SAP BAPI

Hi,
I am getting an error "[SAP.102.9000] JCo error: (104) RFC_ERROR_SYSTEM_FAILURE - connection closed without message (CM_NO_DATA_RECEIVED)" when webmethods sap adapter is calling BAPI in SAP. The BAPI is working fine in SAP.
Can anyone suggest me a possible solution.
Thanks,
Sarath.

BAPI-step by step procedure
http://www.sapgenie.com/abap/bapi/example.htm
list of all BAPI's
http://www.planetsap.com/LIST_ALL_BAPIs.htm

JCO Error in Quality Portal

Hi ,
When i am running WDJ apps in dev portal , it's working fine . But when i am running through QA , it's showing the following JCO error .
Could not create JCO connection .Please ensure that you have nesured RFC destinations and/or logical system name properly for this model .
I tested the JCO in QA and it's working fine . Can anybody help me out regarding this .
And one more question , how to check JCO connections for WDJ apps inside NWDS ?
Thanks a lot .

Hi Jain,
While using RFC Models in the WD application, we maintain JCo dstinations.
These are specifically used to create a JCo Connection between 1 Web Application Server and 1 R/3 System. If any one of them changes, you need to update the same in the JCo destinations created.
The point here is, as you have changed the Dev System to QA System, i.e. your Web Application Server, you will need to create / maintain the JCo Destination with the same name on the Quality System for use of the application.
The JCo connection that you have been testing, is, may be on your developemnt system.
Hope it helps.
Regards,
Alka.

Java portal to bw hana sp08 JCO error

Dear Team
I am facing an issue after BW Hana migration.
Senario:1(BEFORE MIGRATION)
ORACLE DB/ BW NW 7.3+ JAVA PORTAL 7.01, EACH ON SINGLE STACK
HOSTNAME: xxxxx
DOMAIN: xxx.LOCAL
DATABASE: ORACLE11G
SYSTEM : ABAP + JAVA SEPARATE STACKS
PLATFORM: NW 7.3
JAVA 7.01
Senario 2
( MIGRATION ENTIRE ABAP STACK)
HDB/ BW NW 7.3
HOSTNAME: YYYYY
DOMAIN: xxxx.LOCAL
DATABASE: HDB SP08
SYSTEM : ABAP
PLATFORM: NW 7.3
Migrated only Abap stack and Java portal still runs with older database(oracle)in Older system(Xxxxx). I did the re-deployment on java portal with new HANA db configuration and it was success but.
When connecting Jco it is throwing error
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
only the issue with Jco rest of all connectivity working fine, anybody face the same issue ?

Hi,
Issue got resolved .
OOPS N BUGS !!!: Java portal to bw hana JCO error / Connection failed. Make sure that Single Sign-On is configured corre…
Thanks
Yoonus

ESS - CL_PT_ARQ_BLOP_ADAPTER error

Hi Gurus,
I am facing problem when sending leave in ESS, the error is as follows:
Exception/error 262144 triggered in method MAINTAIN_TIMEDATA, class CL_PT_ARQ_BLOP_ADAPTER.
This is happening in only one user not everyone. What could be the reason for this?
Regards,
Priya

Hi,
I tried giving SAP_ALL rights to the user, then also the same error is coming.
Regards,
Priya

ERP2004: ESS JCO session handling in Web Dynpro apps?

Hello,
we run ESS/MSS Web Dynpro scenarios, running on WAS 6.40, SP12 in
Enterprise Portal EP6 SP2 Patch 32. Our go live will be with > 1000 ESS users.
1. When will the sessions in R/3 backend system be terminated by the
Web Dynpro Application?
How is the session handling in FPM (Floor Plan Manager) implemented?
2. Are there any recommendations regarding the JCO connection settings
in Web Dynpro Content Administrator (Maximum Pool Size, Maximum Connections,
Connection Timeout, Maximum Wait Time) to reduce / optimize the load for the
backend system? I found a documentation in SDN but it is not
specific for ESS / MSS based on Web Dynpro.
Background of questions above: The customer is worry about the load on
SAP R/3 backend side: too much current users in the R/3 backend system,
possibly bad performance etc. because the JCO sessions are open a long time.
Are there any experiences with customers running productive ESS / MSS scenarios
based on Web Dynpro?
Thanks & Best regards,
Daniel

Hi,
1. For best practices on JCO settings follow the tutorial below and do it accordingly for your no of users. YOu might have to do some trial and error procedure.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3103eb90-0201-0010-71af-be6f4a6f61d1
2. For standards, security settings, cache management etc, SAP will give a TODO list after a remote audit of your project.
regds,
Sukanta Rudra

ESS + JCO + Multiple backend support

XSS with multiple backends
Hi All, we have a portal running with the standard ESS business package u2013 we use the system for demo purposes, and would like to be able to connect to different backend systems u2013 depending on the user.
IE, user XX connects to system DP4 and user YY connects to system ID4 u2013 is this possible?
My own approach was:
I made 2 delta copies of the of the standard ESS role to two folders u2013 XX and YY
XX I didnu2019t change, and therefore it used the standard SAP_R3_HumanResources JCO connection, which points to system DP4.
Then in the folder YY, I changed the WebDynpro iView parameter to:
sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:ID4&sap-wd-arfc-useSys=SAP_R3_HumanResources:ID4
and in the Webdynpro Content administrator I created these systems and called them:
SAP_R3_HumanResources_MetaDataID4 u2013 as the guide from sap descripes.
This did however not seem to work, as metadata was still readout from DP4 while application data was Read out from ID4.
Then I noticed that the application eg. WhoIsWho also refers to som additional applications, such as
Xssfpmutil and so on u2013 and they use the JCO: SAP_R3_SelfServiceGenerics, so I created a
SAP_R3_SelfServiceGenericsID4, and added this to the parameter string, so I know looks like:
sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:ID4&sap-wd-arfc-useSys=SAP_R3_HumanResources:ID4&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:ID4&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:ID4
But this doesnu2019t work, some of the data is still read from Dp4 instead of ID4
So my question is u2013 is it possible to use ESS with two backends, or is this not supported?
Help is MUCH appreciated
Br Ronni

Hi stuart!
I made two copies of the standard ESS role
ESS_XX and ESS_YY, and then i changed i iview parameters for each iview
(by breaking the deltalink in both roles),
giving them the following application parameter:
sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:ID4&sap-wd-arfc-useSys=SAP_R3_HumanResources:ID4&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:ID4&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:ID4
But the problem is that while the user YY gets modeldata form system YY the user gets metadata from system XX
(assuming he is created on system XX, if not we get an error).
so i guess the parameters somehow dont match.
Has anyone used the same portal for different backends with sucess?
Br Ronni

Using JCO error Wrong repository version = 0 encountered.

Hi Guru,
We convert our existing Java Jco program to call RFC Sender adapter and XI should forward the request to RFC receiver adapter to our ECC.
We found that when we create client connection using gwhost, gwserv and tpname which is config in RFC sender adapter.
In our Java program throw error in the step of mRepository.getFunctionTemplate.
The error is "Wrong repository version = 0 encountered.".
It seems the program can not access function template from repository.
Anyone have this experience before, please advise
Thanks you.

It's working now.
For your knowledge, it seems it was something wrong inside the jrfc.jar.
The problem is not exactly the same but the solution is to apply OSS note 816491.

Jco: Error Connecting using sapgw04

Hi,
I have a problem using Jco to connect to a SAP-System.
I'm trying to connect to SAP using the following configuartions:
 sysnr: 04
 GWServ: sapgw00
 GWHost: XXX.YYY.com
 ASHost: XXX.YYY.com
The code to create a repository for this configuration is:
 JCO.addClientPool(poolname, maxpoolsize, "538", "username", "password", "DE",
 "XXX.YYY.com", "04", "XXX.YYY.com", "sapgw00");
When I use this pool to get a function I get an Exception:
com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template '[FUNCTIONNAME]'
caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect from SAP gateway to RFC server failed
Connect_PM
 GWHOST=XXX.YYY.com , GWSERV=sapgw00, ASHOST=XXX.YYY.com , SYSNR=04
LOCATION
 SAP-Gateway on host h33e / sapgw00
ERROR partner not reached
 (host XXX.YYY.com , service sapgw04)
The strange thing is the sapgw04 in the error-message.
Somehow JCO wants to use sapgw04 to connect to the RFC-Server. Is this an error in the SAP-Configuration or do I have to change the configuration of Jco?
How can I tell Jco not to use sapgw04 but sapgw00?
Any help would be appreciated!
Thanks
Torsten

Hi Torsten,
please check how you log on to your system. You are giving a system number 04, which corresponds to sapgw04. I'm not sure why the method needs all the information, seems to be duplicate to me (please comment if I'm wrong); it should be sufficient to use:
addClientPool(String key,
 int max_connections,
 String client,
 String user,
 String passwd,
 String lang,
 String ashost,
 String sysnr)
If you don't want to use sapgw04, just specify "00" for the sysnr.
Hope this helps, harald

WebSphere Integration with ESS/MSS Error

Hi All,
We are trying to setup a scenario where we embed the SAP Portal within WebSphere portlets. Plan is that we would have WebSphere link to the ESS HomePage. We have setup a URL alias in the web-inf with nested_window=1. The websphere guys are using the the WebSphere clipper to create the portlets but this is giving us javascript errors (e.g. Access Denied, etc). This means when we click on any of the ESS framework links e.g. Personal Data the webdynpro spinner comes up and nothing happens i.e. they screen does not change.
Any thoughts on what might be the issue? Is the Clipper the best tool to use?

Hi Mendonca,
Error is due to mis match of patches.
Check with SAP_HR and EA_HR patches. Try to maintaine the patches to 26 patch. By this u can resolve the issues.
That means Patches from Java side and Backend side need to be maintained at there same levels.
Regards,
kishore.

JCO Error - SAP ER

Dear all,
I'm facing this issue during the SAP reconciliation.
Could you please help me?
[2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] ================= Start Stack Trace =======================
[2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] oracle.iam.connectors.sap.common.parser.SAPIDOCListener$ThrowableListener : serverExceptionOccurred
[2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
[2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] Description : (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
[2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable. (raised by system hgrs-hbk-s0340|a_rfc)[[
 at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:664)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2443)
 at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
 at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
 at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
 at java.lang.Thread.run(Thread.java:736)
Caused by: RfcException: [hgrs-hbk-s0340|a_rfc]
message: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
Return code: RFC_FAILURE(1)
error group: 104
key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by hgrs-hbk-s0340|a_rfc
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2832)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2646)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2537)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2358)
 ... 4 more
Caused by: RfcException: [hgrs-hbk-s0340|a_rfc]
message: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
Return code: RFC_FAILURE(1)
error group: 104
key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by hgrs-hbk-s0340|a_rfc
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3378)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2827)
 ... 7 more
Caused by: com.sap.conn.idoc.IDocRuntimeException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
 at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:240)
 at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3349)
 ... 8 more
Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
 at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:126)
 at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
 at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
 at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:143)
 at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.createIDocDocumentList(DefaultJCoIDocServerWorker.java:301)
 at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:199)
 ... 10 more
[2012-09-18T13:54:32.482+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] ================= End Stack Trace =======================

Hi Arun,
I did that step as well,
4.copy the Sapjco3.jar into the "CIA" directory of mercury folder and copy the sapjco.dll into the c:\windows\system32 file.
Any clues?
why this error?

Jco error

Hi Friends,
Itu2019s a support issue. Messages have failed in integration engine and inbound queues
I am getting different errors in different areas of xiu2014
In Integration engine Problem while determining receivers using interface mapping u201CCommunication failureu201D during JCO CALL
Similarly another error in other message in Integration engine unable to find URL for adapter engine.
In SMQ2 error is XI Error JCO_SYSTEM_FAILURE.MAPPING: Queue stopped.
Pls help !!

As suggested by Prateek, please check whether the SM59 destination AI_RUNTIME_JCOSERVER is working or not. If this is not working, search for AI_RUNTIME_ZX2 in smgw=>Goto=>Logged on Clients.
If you find the program ID AI_RUNTIME_ZX2 in TP name column and still have issue, please ensure that the user-id id PI_JCO_USER is not locked or the password has not been changed.
If you can not find the AI_RUNTIME_ZX2 in TP Name column, that means there is an issue with JCo RFC provider. In Visual Admin(PI 7.0) / NWA (PI 7.1), do the necessary stuff which makes the program ids to appear in smgw logged on clients. Basis should know about this.
Hope this helps.

ESS JCO ERROR

Similar Messages

Maybe you are looking for