topic Re: CALL_FUNCTION_REMOTE_ERROR "connection closed (no data)" in Application Development and Automation Discussions

CALL_FUNCTION_REMOTE_ERROR "connection closed (no data)"

Former Member — Tue, 16 Feb 2016 15:54:55 GMT

Hi Friends,

Need your help in this peculiar kind of situation in which an RFC call from SCM system to R3 system is ending in dump with run time error CALL_FUNCTION_REMOTE_ERROR "connection closed (no data)".

The dump log in SCM system says "The error occurred during an RFC call to another system.In the target system, a short dump has been written as well.More detailed information on the error cause can be found there."

But when I check in R3 system there is no dump. I even tried to debug it but control never reaches to function module it terminates before that.

I checked SM21 in R3 and found this.

"Delete session 001 after error 052". Don't know what error 052 is.

I have attached the dump log.

The most peculiar thing is same RFC runs fine after an hour but only at a particular time interval it fails with the reason mentioned.

I raised to SAP as well they gave their famous reply that this is a custom object we can not help there.

Re: CALL_FUNCTION_REMOTE_ERROR "connection closed (no data)"

michael_kozlowski — Tue, 16 Feb 2016 16:41:15 GMT

Check SAP note 527481 espacially item 10. 527481 - tRFC or qRFC calls are not processed

Re: CALL_FUNCTION_REMOTE_ERROR "connection closed (no data)"

Former Member — Tue, 16 Feb 2016 17:25:05 GMT

Hi Michael,

Thanks for your help.

This is what item 10 says. The only problem we see is we have DB6 as database instead of Oracle.

10. Transaction SM21 displays the following entries every 10 minutes (the affected user is the one under which the outbound scheduler was started):

01:06:34 DIA 000 100 BWREMOTE Q0 2 Stop Workproc 0, PID <PID-Nr>

01:06:34 RD Q0 I Operating system call recv failed (error no. 10054)

01:06:49 WRK 000 Q0 Q Start Workproc 0, Pid <PID-Nr>

01:06:50 DIA 000 100 BWREMOTE R4 7 Delete session 001 after error 052

These entries point to the fact that the main scheduler was terminated abnormally, and that is attempts to process the tRFC or qRFC LUWs 10 minutes later.

One reason for this problem could be too low values for the parameters 'Processes' and 'Sessions' in the database scheme.

The following entry in the file <SID>_ora_<digit>.trc (in the directory

<disk drive >:\oracle\<SID>\saptrace\background) may point to the following error:

ORA-00020: maximum number of processes (<number of processes>) exceeded

In this case, you can check the settings for the Oracle database in accordance with Note 830576.