SAP Basis Tech Supports

Symptom

You execute the CTC Wizard “PI Adapter Engine initial setup” and receive in configuration step “Synchronize the SLDAccessor” the following message:
Error: Catching SLDException: Failed to initialize ExchangeProfile properties.
Reason: Cannot synchronize the SLDAccessor.
Step: Synchronize the SLDAccessor

The detailed error messages are:
InvokeService:Synchronize the SLDAccessor
Library: sap.com/tc~lm~config~content
…
Execute Java Service
Library: sap.com/com.sap.xi.ctc.app
Class: com.sap.ctc.util.pi.services.ExchangeProfileSetup
Method: void com.sap.ctc.util.pi.services.ExchangeProfileSetup.
synchronizeSLDAccessor()
Stack Trace
com.sap.ctc.util.infra.ConfigLibException: Catching SLDException: ‘Failed to initialize ExchangeProfile properties. Reason: Konnte Konfigurationsdaten (ExchangeProfile/aii.properties) nicht lesen’. Cannot synchronize the SLDAccessor.
at com.sap.ctc.util.pi.services.ExchangeProfileSetup.
synchronizeSLDAccessor(ExchangeProfileSetup.java:777)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.
invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.
invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
…

Other terms

AII, XI, XPI, Exchange Infrastructure

Reason and Prerequisites

The Exchange Profile connection data has been maintained incorrectly or the respective Integration Server is not available. The non-central Adapter Engine has been restarted with this incorrect setup conditions. Therefore some internal static variables have been initialized incorrectly. When the CTC setup is restarted after a reboot and incorrect connection data are entered again (or the Integration Server is still unavailable), the SLDAccessor throws the above exception and the setup is interrupted. It makes no sense to continue.

Solution

Cancel and restart the “PI Adapter Engine initial setup”. Pay attention that you enter the correct Integration Server access data which are:
Integration Server host nameIntegration Server clientIntegration Server system numberPILDUSER namePILDUSER password

Make sure that the PILDUSER is not locked and that the Integration Server is up and running. Pay attention that the host name is resolved in case your non-central AE is in a different network domain. You may check all this by entering the data manually at:
http://: /exchangeProfile –> Connection

Press ‘Set’ after that. If the data is correct, the next screen page displays the Exchange Profile data. Otherwise you find an error message with more details about the problem.