WD JCO : Client not connected in repository call

[Former Member]

Hi,

I'm getting the JCO_ERROR_COMMUNICATION error while initializing JCo connections. I'm able to successfully test and ping connections from WD content admin, but fails to start the WebDynpro application with the error given below.

Has anyone came across this error?.

Thanks,

Dharani.

exception detail:

com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call

at com.sap.mw.jco.JCO$Repository.getVersion(JCO.java:19715)

at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:20055)

at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:19776)

at com.sap.mw.jco.JCO$Repository.getFunctionInterface(JCO.java:19890)

at com.sap.mw.jco.JCO$BasicRepository.getFunctionTemplate(JCO.java:18958)

[Former Member]

Hi,

Can you please explain me how to do this as I am very confused.

Create a Z_RFC_DD_MDI is a role or what?

. Create a Z_RFC_DD_MDI authorization (you can also select a different name) for the S_RFC authorization object of the AAAB class with the following instances:

Activity: 16

Name of the RFC object to be protected: RFC1, RFC2, SDDO, SDIFRUNTIME, SG00, SRFC, SYST, SYSU, SIFD, SIMG, SDNT

Type of RFC object to be protected: FUGR

1. Create a Z_DDIC_MDI profile (you can also select a different name) and insert the Z_RFC_DD_MDI authorization into this.

Thank you very much

sun

[Former Member]

hi all

while testing JCO connection iam getting such types of error

can anybody solve this.

com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call

Regards

Hameem

[Former Member]

try to ping ur JCO destination and check for the following step.

1) you need Message server entry in services file

C:\Windows\system32\drivers\etc\services

pattern:

sapms<SID> 36<nr>/tcp

2) in SMLG, log on group attribute is ext-RFC enabled

[Former Member]

Here is the solution from SAP note:677732 for this issue:

Reason and Prerequisites

The SAP S_DDIC_MDI profile that contains the minimum authorizations for accessing the DDIC using MDI does not yet exist in the R/3 System. This profile is not normally available in 4.6C and 4.6D, but it is available as of a particular Support Package in 6.10 or 6.20.

Solution

1. Create a Z_RFC_DD_MDI authorization (you can also select a different name) for the S_RFC authorization object of the AAAB class with the following instances:

Activity: 16

Name of the RFC object to be protected: RFC1, RFC2, SDDO, SDIFRUNTIME, SG00, SRFC, SYST, SYSU, SIFD, SIMG, SDNT

Type of RFC object to be protected: FUGR

1. Create a Z_DDIC_MDI profile (you can also select a different name) and insert the Z_RFC_DD_MDI authorization into this.

[Former Member]

Hi there,

We are running: Release 700 level 0011 support package SAPKW70011

Thank you for the quick response.

I will try the solution and let you know.

Many thanks

Jo-lize