Access To SLD From ABAP Fails 
Problem Description
Transaction SLDCHECK reports errors.
A disrupted communication between an ABAP system and the System Landscape Directory (SLD) 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.
|
Scenario Type: |
Error analysis |
|
NetWeaver Component: |
Web AS Java J2EE Engine SLD |
|
Validity: |
J2EE Engine >= 6.30 on Windows and Unix platforms Web AS >=6.40 SP4 |
Decision Roadmap
Prerequisites
-
Main Tools
· SLDCHECK
· SM59
· Visual Administrator
Analysis
The figures on the following pages give you an overview of the analysis process. The numbers in brackets refer to subsequent sections with detailed information. Start with the execution of transaction SLDCHECK.
(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 (the 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 has the 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 (see System ® Status ® SAP system dataarea) set the Unicode flag in the Special Options area, if it is a Non-Unicode system refer to a Non-Unicode 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 are maintained and the primary flag is set to a valid parameter set, re-enter the valid password.
(5) SLD interactive logon check
Try to log-on 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 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 and navigate to <SYS-ID> ® Server<node> ® Services ® JCo RFC Provider.
Check the validity of the Repository logon data and verify the users’ authorization. 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.
Additional Information
http://service.sap.com/sld