cancel
Showing results for 
Search instead for 
Did you mean: 

RFC destination SAPSLDAPI does not exist

Former Member
0 Kudos

I use TC SLDCHECK in R/3 and the next message appears:

RFC destination SAPSLDAPI does not exist

=> Create the RFC destination by using transaction SM59!

Summary: Connection to SLD does not work

=> Check SLD function and configurations

Now checking access to the XI Profile

Properties of RFC destination LCRSAPRFC

RFC host: %%RFCSERVER%%

program id: LCRSAPRFC_NONUNICODE

gateway host: srv-xi01-adm

gateway service: sapgw00

Testing the RFC connection to the SLD java client...

RFC ping returned exception with message:

Error opening an RFC connection.

What kind of problems does this will give me and how can I repair it without touching anything that could turn unstable XI?

Accepted Solutions (0)

Answers (8)

Answers (8)

former_member192238
Participant
0 Kudos

LCRSAPRFC and SAPSLDAPI these two RFC destinations are required to connect SLD While creating this make sure that Programme ID is registered server programme.Same programme id must be maintained in j2ee engine

Enter the URL as http://hostname.<domain>.<ext>:port/nwa and Click on configuration Management 􀃆 Infrastructure -> JCo RFC Provider

Check LCRSAPRFC,SAPSLDAPI status should be in running

Regards

Praveen Reddy

Edited by: Maareddy Praveen Reddy on Sep 2, 2011 1:26 PM

Former Member
0 Kudos

Hi,

1) SAPSLDAPI 2) LCRSAPRFC are the standard and mandatory RFC's under TCP/IP type connections need to be created in SM59.

In your case these mandatory RFC connections are missing hence you can see the errors in SLDCHECK .

Basis team should create the above mentioned mandatory RFC connections under TCP/IP type.

Ask your BASIS team to create them , then your issue will be resolved .

Former Member
0 Kudos

1) SLD status is running

2) in sm59 SAPSLDAPI test is working fine

3) unicode test in SAPSLDAPI gives me this information:

"Target is a unicode system (char.size 2)"

4) 3 users found, one has checkbox checked

5) I have already logon to SLD

6) user parameters in su01 are ok (the one that is checked as prim. in the SLDAPICUST)

7) I dont understand that.

All this I try it in XI and its working fine.

Obviously, SLDCHECK here is working fine too.

The problem is in SAP R/3:

1) SLD status is running (same url as before)

2) in TC sm59, SAPSLDAPI doesnt exist in TCP/IP CONNECTIONS

3) read 2

4) No users found on SLDAPICUST

5) I have already logon to SLD by url in an internet explorer

6) read 4

7) I dont understand that.

Is there any problem in here? Must R/3 have users on SLDAPICUST and a SAPSLDAPI connection?

former_member183906
Active Contributor
0 Kudos

Hii.. Follow these steps for SLDCHECK success :

(1) Check status of SLD server and, if required, start the SLD server

(2) Check and, if required, maintain RFC destination SAPSLDAPI via transaction SM59

(3) Unicode consistence check

(4) Check parameters maintained in transaction SLDAPICUST

(5) SLD interactive logon check

(6) Check the user maintained in the SLDAPICUST parameters within transaction SU01

(7) Analysis in JCO Provider of the SLD host J2EE Engine: Destination part

If these all is thru , then SLDCHECK will be throuh. U can take help of basis team in this.

http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm

SudhirT
Active Contributor
0 Kudos

Hi,

Try to execute RZ70. New RFC will be created.Thanks!

Former Member
0 Kudos

How does new RFC would be created in RZ70?

What does Start Data Collection button does in here?

Former Member
0 Kudos

HI

This problem is due to the improper support patch level in ABAP and JAVA.check Note 616485 - XI access to SLD server 6.30 ( extract from below thread).

also check

regards

kummari

Former Member
0 Kudos

Hi,

1.Have you added the configuration of the SAPSLDAPI

in the J2EE Engine Administrator like show in the installation guide under Server -> Services -> JCo RFC provider?

2.Have you entered Registered Server Program option?

in the rfc destination?

3. you can find the configuration in point: 8.1.1 Maintaining the HTTP Address of the SLD Server

of the configuration guide

Refer the note 52959

Regards,

Pradeep A.

Former Member
0 Kudos