ActiveControl uses the saplogon.ini files (for SAPGUI 730 and earlier, and XML file for SAP GUI 7.40 onwards, on the local PC to determine this list of systems to connect to.

ActiveControl reports the presence of both saplogon.ini and SAPUILandscape.xml files in:

1) Local ActiveControl folder (typically C:\Program Files (x86)\Basis Technologies\ActiveControl)

2) Windows directory

3) Directories stored in the registry by SAP GUI * Current User Local: HKEY_CURRENT_USER\Software\SAP\SAPLogon\ConfigFilesLastUsed\ConnectionConfigFile * Current User Server: HKEY_CURRENT_USER\Software\SAP\SAPLogon\ConfigFilesLastUsed\ConnectionConfigFileOnServer * Local Machine Local: HKEY_LOCAL_MACHINE\Software\SAP\SAPLogon\ConfigFilesLastUsed\ConnectionConfigFile * Local Machine Server: HKEY_LOCAL_MACHINE\Software\SAP\SAPLogon\ConfigFilesLastUsed\ConnectionConfigFileOnServer

4) SAPLOGON_INI_FILE environment variable (saplogon.ini only)

E.g. “C:\Program Files\Basis Technologies\ActiveControl\ActiveControl.exe” “SAPLOGON_INI_FILE=C:\Windows\saplogon.ini”

5) %APPDATA%\SAP\Common folder (XML only) – this is the default location for the ‘local configuration path’.

Please be aware that ActiveControl will continue to look at old saplogon.ini files if the customer moves over to xml config files and the historical ini. file still exists, so users may need to check that both ActiveControl and SAP are using the same configuration files after doing a SAP GUI or ActiveControl upgrade.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment