We use ACL directlink to dump SAP data on a regular basis.

There was an annoying error that always happened:

Time, SAP-REL 730,0,526 RFC-VER 3 1478436 MT-SL
T:1356 Error in program ‘ACLWin’: ======> Start ‘sapgui’ failed.
T:1356 Error in program ‘ACLWin’: <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
T:1356 Error in program ‘ACLWin’: <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
T:1356 Error in program ‘ACLWin’: <* RfcCallReceive [1] : returns 3:RFC_SYS_EXCEPTION
T:1356 Error in program ‘ACLWin’: ======>

>>> RfcOpenEx …
Got following connect_param string:
TYPE=3 CLIENT=400 USER=****** PASSWD=******* LANG=EN DEST=XXX USE_SAPGUI=0
Read environment variable RFC_INI
Got following contents from saprfc.ini:
DEST=XXX TYPE=A ASHOST=XXX SYSNR=15 RFC_TRACE=0 ABAP_DEBUG=0 USE_SAPGUI=2
<<< RfcOpenEx failed

I recently came to the solution: change USE_SAPGUI = 1 (ON) from  USE_SAPGUI=2 (invisible SAP_GUI after each RFC) in saprfc.ini (check Windows environment variable RFC_INI to find out where this file is located in your system).

I believe the problem was that there were too many invisible SAP GUI opened(invisible though) which reached Windows limit so new SAP GUI could not be opened anymore. USE_SAPGUI=1 (On) alleviates the issue.

 

ACL direct link failure
Tagged on:                     

Leave a Reply

Your email address will not be published. Required fields are marked *

30 − = 20

This site uses Akismet to reduce spam. Learn how your comment data is processed.