Solution : https://service.sap.com/sap/support/notes/1093054 (SAP Service marketplace login required)
Summary :
This SAP Note identifies the CALL_FUNCTION_OPEN_ERROR which occurs after multiple initiations of RFC connections to an externally started RFC server program, commonly after around 50 attempts. Kernel patch 700 level 125 initiated this issue due to an incorrect implementation in handling child processes. Trace errors such as "out of free process slots" and "Too many open files" are noted. Resolving this requires updating the kernel to level 145 for 700 versions or 89 for 710 versions. Alternatively, setting the profile parameter 'rfc/use_gwstart' to 1 can manage the problem until the patch is applied. Testing this setting on a test environment is advised before deployment.
Key words :
rfc 1646 convid 65281252a cmrc=0 data=0 status=0 saprc=0 rfcexecprogramkernel rfcraiseerrormessage process administration, free process slots [thxxexec, profile parameter rfc/use_gwstart = 1, 19466 downloading sap kernel patches, profile parameter rdisp/wp_auto_restart, abap statements'open dataset, rfc> abap program, rdisp/wp_auto_restart = 24h, rfc server program, error messages mentioned
Related Notes :
| 1150361 | Hanging processes |
| 1140641 | |
| 1121442 | F3V - error 9 during write or read access to a file |
| 1120287 | DATASET_WRITE_ERROR or DATASET_TELL_ERROR under Windows |
| 1088922 | Improvement: Starting RFC servers |