Solution : https://service.sap.com/sap/support/notes/676938 (SAP Service marketplace login required)
Summary :
Following the importation of the RFCEXEC program as outlined in SAP note 618516, users encounter specific issues. First, despite correctly setting the RFCEXEC_SEC_FILE_PATH environment variable, the system fails to open the rfcexec.sec file, reporting a file access error. Additionally, terminating the rfcexec either through '/n' command in RFC server sessions or by canceling in registered server instances leads to system crashes; UNIX systems report a core dump, while Windows NT systems show an ACCESS_VIOLATION error. These issues stem from flaws in both the rfcexec program and the RFC library. Updating to the latest versions as per SAP notes 27517 and 413708 for RFCEXEC and RFC library respectively is recommended to resolve these anomalies.
Key words :
ms windows platforms, rfcexec_sec_file_path environment variable, terminate rfcexec intentionally, open file rfcexec, started rfc server, secng file, rfcexec_sec_file_path path, registered server, rfcexec program, terms rfcexec
Related Notes :
| 618516 | Security-related enhancement of RFCEXEC program |
| 413708 | Current RFC library |
| 27517 | Installing RFCSDK |