Access to SLD from ABAP fails Transaction SLDCHECK reports errors

Symptom
A disrupted communication between an ABAP system and the System Landscape Directory may
result in various errors in the Exchange Infrastructure or in the Solution Manager. The
connectivity status can be specifically tested by executing transaction SLDCHECK.
The access to SLD from ABAP is discontinued, if SLDCHECK displays red error messages
in its output list. Typical situations are:
RFC ping failed
The first call to function module LCR_LIST_BUSINESS_SYSTEMS terminated with
some exception
Please note that the SLDCHECK section Access to the XI Profile is not covered within this PAS.

Scope
Component: WAS, J2EE, SLD
Validity: J2EE Version >= 6.30 on Windows and Unix platforms and a WAS >=6.40 SP4
Used tools: SLDCHECK, SM59, J2EE Visual Administrator

Analysis
The figures on the following pages give you an overview of the analysis process. The numbers in
braces refer to subsequent sections with detailed information. Start with the execution of
transaction SLDCHECK.

Execute SLDCHECK

SLDCHECK
successful?
no

SLD server
running? (1)

no

Start SLD server (1)

no

Create RFC dest.

SAPSLDAPI in SM59
(2)

yes
SM59:
Dest. SAPSLDAPI
maintained?
(2)
yes

Conn. test in
SM59 ok?

Analysis in JCO
RFC Provider:
Destination
settings (7)

no

yes

SM59:
Unicode settings
consistent? (3)

no

Unicode system?

no

Refer to Non-Unicode
destination (3)

yes

yes

Set Unicode flag

consistent in SM59
yes

SLDAPICUST:
primary destination
maintained? (4)

no

Maintain primary
destination in
SLDAPICUST

yes

Host & port ok?

Maintain correct host

and port

no

yes
SU01: Check &
maintain SLD user (6)

Re-enter password
no

Interactive logon
to SLD ok?

Interactive logon
to SLD ok? (5)

yes

SLDCHECK
successful?

no

Contact SAP
support

yes

no

Analysis in JCO
RFC Provider:
Repository
settings (8)

yes

Problem solved

Analysis in JCO
RFC Provider:
Destination
part (7)

JCO RFC
Provider Service
running?

no

Start JCO RFC

Provider Service

no

Maintain Program ID
case-sensitively

no

Maintain Gateway
parameters
consistently

no

Contact SAP
support

no

Continue

yes

Program ID
maintained and
case ok?

yes

Gateway
parameters
ok?

yes

SM59 Test ok?

yes

SLDCHECK
successful?

yes

Problem solved

Analysis in JCO
RFC Provider:
Repository
settings (8)

Check validity of
Repository logon data
and user authorization

Unicode flag
consistent with Repos.
system?

no

Adjust logon to
Unicode-compatible
repository

no

Contact SAP
support

yes

SLDCHECK
successful?

yes

Problem solved

(1) Check status of SLD server and, if required, start the SLD server
From the SLD main page http://<host>:<port>/sld navigate to Administration (user needs a
LcrAdministrator assigned, you can also use the J2EE Administrator user).

Check the status of the server and start the server if the server in status stopped.
(2) Check and, if required, maintain RFC destination SAPSLDAPI via transaction SM59
Within transaction SM59 TCP/IP connections check whether the RFC destination is maintained
and, if the destination is not maintained, create the RFC destination.

After the maintenance of the RFC destination perform a connection test by using the Test
connection button.

(3) Unicode consistence check

Within transaction SM59 TCP/IP connections -> Special Options check whether the Unicode
settings of the RFC destination are consistent.
If the calling system is an Unicode system (Menu -> System -> Status -> SAP system data area)
set the Unicode flag in the Special Options area, if it is a Non-Unicode system refer to a NonUnicode destination Program ID as Registered Server Program within SM59 (see (2)).

(4) Check parameters maintained in transaction SLDAPICUST

Within transaction SLDAPICUST check whether the connection parameters are maintained
correctly. If the correct user, password, host name and port is maintained and the primary flag is
set to a valid parameter set, re-enter the valid password.

(5) SLD interactive logon check

Try to logon to http://<host>:<port>/sld using the user and password maintained in transaction
SLDAPICUST.
(6) Check the user maintained in the SLDAPICUST parameters within transaction SU01
Within transaction SU01 check the validity of the user and password maintained in SLDAPICUST.
Does this user exist ?
Is its password valid ?
Is this user unlocked ?
Check the validity period of this user.
Check if the role SAP_XI_APPL_SERV_USER is assigned to this user.
(7) Analysis in JCO Provider of the SLD host J2EE Engine: Destination part
Start the J2EE Visual Administrator Tool and navigate to <SYS-ID> -> Server<node> -> Services
-> JCo RFC Provider.

Check whether the JCo RFC Provider service is running and the relevant RFC destination is
running, too. Possibly the service itself as well as the RFC destination has to be started.
Furthermore, verify if the Program ID is maintained correctly, the Program ID has to be
maintained
case-sensitive identical to the Program ID inscribed in transaction SM59. Additionally check
whether the Gateway parameters are set consistently with the parameters maintained in
transaction SM59.

(8) Analysis in JCO Provider of the SLD host J2EE Engine: Repository settings
Start the J2EE Visual Administrator Tool and navigate to <SYS-ID> -> Server<node> -> Services
-> JCo RFC Provider.

Check the validity of the Repository logon data and verify the users authorisation. Check whether
the Unicode flag within the Repository settings are consistent with the Repository system. If the
RFC destination Program ID is pointing to a Non-Unicode RFC destination in transaction SM59,
unset the Unicode flag within the Repository settings and adjust the Repository logon data to a
Non-Unicode repository system.

Further Information
http://service.sap.com/sld

SAP Internal Information

SLD: SAPNet alias /landscape

Configuring the SLD connectivity: SAPNet alias /nw04installation
o Post-Installation Guide - SAP System Landscape Directory
o Installation Guide - SAP Exchange Infrastructure 3.0
o Configuration Guide - SAP XI 3.0