How to resolve iNetConnector SAPLOGON_ID not found in saplogon.ini error message

Previous  Home  Next

When encountering error message of "iNetConnector 'SAPLOGON_ID 'SAP SYSTEM' not found in saplogon.ini, RFC ERROR PROGRAM" similar to the one shown in below screenshot, please follow the given instructions.





Note: If user is using Process Runner version 4.20.108.XXXX and above then XML Configuration file will be handled automatically. The XML file generated by SAP GUI 740 is compatible with Process Runner version 4.20.108.XXXX and above. If you are using Process Runner version below 4.20.108.XXXX, then please follow steps mentioned below in order to map the saplogon.ini file path in iNETConnector window of Process Runner.


It is always recommended to update the Process Runner to the latest version. Click here to download the updated version of Process Runner.



Background Information/Cause:

This error is due to Process Runner not being able to communicate with the SAP System Server and usually occurs when you have more than one saplogon.ini file in your SAP system. It is necessary to ensure that the 'saplogon.ini' file path of SAP system and Process Runner are same.


Suggested Solutions:

The most recommended solution towards this error is to download the updated version of Process Runner. Whereas following are the generic steps to solve such issue in the versions of Process Runner which are below 4.20.108.XXXX


A) Verify Local Config file path

Please check the saplogon.ini file path in SAP system and make sure it is same as in Process Runner iNetConnector saplogon.ini file path.




hmtoggle_arrow1Check saplogon.ini file path in SAP


hmtoggle_arrow1Check saplogon.ini file path in Process Runner


B)  Saplogon.ini Troubleshooting

Search for the saplogon.ini file on your system.

i.Open the Start menu by clicking on Start button or pressing Windows logo key.

ii.Type CMD to open Command Prompt.

iii.Switch to the root-search-folder (go to C: drive by using cd\ command and hit Enter)

iv.Type dir saplogon.ini/s/a  and hit Enter to use the path of saplogon.ini file present on your system.


Start Process Runner and click on Logon Pad. In the iNetConnector window click on Advanced tab and make sure that "saplogon.ini" path is same as found in the above step. If not, browse and change the path.



After providing the path click on “Server/Group” tab and verify whether you are getting the correct list of SAP system or not.


Please note that there could be instances where the newly added SAP system is not displayed in iNETConnector list even if the path of saplogon.ini file "C:\Windows\saplogon.ini" is same in both Process Runner iNetConnector window and SAP Logon Options. This usually happens when user manually adds SAP system in SAP front end leading to auto creation of saplogon.ini file in %APPDDATA%\Roaming\SAP\Common folder. In this situation, follow the below mentioned workarounds to resolve the issue.


i.Check for the saplogon.ini file in the roaming user application directory ( %APPDDATA%\Roaming\SAP\Common) and if file exist then map this in iNETConnector->Advance tab.


After updating this path if you still encounter "SAPLOGON_ID not found" error  in Process Runner during login to SAP then follow the below solution.


ii.Contact your IT Administrator to update C:\Windows\saplogon.ini file.



C) Other Options

1.If the above solutions do not work then upgrade Process Runner to latest version which would provide you with 'Logon Method' option to resolve this issue. This option automatically switches between methods to sort the above issue . User can map any saplogon.ini file in iNETConnector of Process Runner which may or not match with that present in SAP logon pad.


Expand the 'Advanced SAP Logon properties' section to know more on the Logon Method option present under  'Logon.ini values' tab.


Note: Also refer to SAP System list does not match if SAP systems available via SAP GUI are different from SAP systems available in Process Runner iNETConnector.


2.If the above suggestions do not help then ,please contact us at with the error screenshot and an explanation of what you have already tried.




How to resolve server does not support scripting issue