cancel
Showing results for 
Search instead for 
Did you mean: 

CALL_FUNCTION_REMOTE_ERROR

Former Member
0 Kudos

Hello Gurus ,

We got more than 2000 CALL_FUNCTION_REMOTE_ERROR  dumps in our production system.

In error analysis , we can see

Error analysis

    An error occurred when executing a REMOTE FUNCTION CALL.

    It was logged under the name " "

    on the called page.

    Last error logged in SAP kernel

All the dumps occured fort he same program , but there was no recent code change in the program.

What could be the root cause for this?

Regards,

Vrinda

Accepted Solutions (1)

Accepted Solutions (1)

JPReyes
Active Contributor
0 Kudos

Can you post the complete shortdump?

Regards, JP

Former Member
0 Kudos

Hello,

PFB details :

Category               ABAP Programming Error

Runtime Errors         CALL_FUNCTION_REMOTE_ERROR

ABAP Program           SAPLXDK0

Application Component  Not Assigned

Date and Time          15.08.2016 09:52:31

Short text

     "timeout during accept / CPIC-CALL: 'ThSAPCMRCV' : cmRc=27 thRc=751#Timeout

What happened?

     Error in the ABAP Application Program

     The current ABAP program "SAPLXDK0" had to be terminated because it has

     come across a statement that unfortunately cannot be executed.

     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.

What can you do?

     Note down which actions and inputs caused the error.

     To process the problem further, contact you SAP system

     administrator.

     Using Transaction ST22 for ABAP Dump Analysis, you can look at and manage termination messages, and you can also

keep them for a long time.

Error analysis

    An error occurred when executing a REMOTE FUNCTION CA

    It was logged under the name " "

    on the called page.

    Last error logged in SAP kernel

    Component............ "SAP-Gateway"

    Place................ "SAP-Gateway on host

*******************************************

    Version.............. 2

    Error code........... 751

    Error text........... "timeout during accept"

    Description.......... " "

    System call.......... " "

    Module............... "gwxxrd.c"

    Line................. 5146

    The error reported by the operating system is:

    Error number..... " "

    Error text....... " "

How to correct the error

    Please refer to the notes described in the

    short dump.

System environment

    SAP Release..... 702

    SAP Basis Level. 0012

    Application server... ***

    Network address...... *****

    Operating system..... "Windows NT"

    Release.............. "6.1"

    Hardware type........ "32x AMD64 Level"

    Character length.... 16 Bits

    Pointer length....... 64 Bits

    Work process number.. 1

    Shortdump setting.... "full"

    Database server... "TCP: "

    Database type..... "MSSQL"

Database name.....

Database user ID.. ""

Terminal.......... " "

Char.set.... "C"

SAP kernel....... 721

created (date)... "Jun 24 2014 03:32:15"

create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"

Database version. "SQL_Server_9.00 "

Patch level. 313

Patch text.. " "

Database............. "MSSQL 9.00.2047 or higher"

SAP database version. 721

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

  NT 6.0, Windows NT 6.1, Windows NT 6.2, Windows NT 6.3"

Memory consumption

Roll.... 0

EM...... 25138752

Heap.... 0

Page.... 131072

MM Used. 24229408

MM Free. 905552

User and Transaction

    Client.............. 900

    User................ "JS_ADMIN_CA"

    Language key........ "E"

    Transaction......... " "

    Transaction ID...... "E7B162E6282FF17680DA0017A477AC12"

    EPP Whole Context ID.... "0017A477AC121ED68DC48679696A00D9"

    EPP Connection ID....... "60BA62E65C58F1D280DA0017A477AC12"

    EPP Caller Counter...... 1

    Program............. "SAPLXDK0"

    Screen.............. "SAPMSSY1 3004"

    Screen Line......... 2

    Debugger Active..... "none"

Server-Side Connection Information

    Information on caller of Remote Function Call (RFC):

    System..............

    Installation Number. " "

    Database Release.... 702

    Kernel Release...... 721

Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

Call Type........... "asynchronous with reply and non-transactional (emode 0,

imode 0)"

Inbound TID.........." "

Inbound Queue Name..." "

Outbound TID........." "

Outbound Queue Name.." "

Client.............. 900

User................ "JS_ADMIN_CA"

Transaction......... " "

Call Program........."SAPLSPTA_NEW"

Function Module..... "SPTA_RFC_INVOKE_INTERNAL"

Call Destination....

Source Server.......

Source IP Address... "10.196.60.7"

Additional information on RFC logon:

Trusted Relationship " "

Logon Return Code... 0

Trusted Return Code. 0

Note:

- For Releases < 4.0, information on the RFC caller not available.

- The installation number is available from caller Release > 700

Additional information on RFC logon:

Trusted Relationship " "

Logon Return Code... 0

Trusted Return Code. 0

Note: For releases < 4.0, information on the RFC caller are often

only partially available.

ormation on where terminated

Termination occurred in the ABAP program "SAPLXDK0" - in "EXIT_SAPLADK0_003".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 1410

of the (Include) program "ZALT_WIP_E0012_F01".

Regards,

Vrinda

Former Member
0 Kudos

Hello,

During the time of dump , i Can see the below entries in gateway logs as well.

GwICheckAccept: delete conversation 51316924 (conn=331) in state SEND_DO_ACCEPT, due to accept timeout of 60 seconds

GwICheckAccept: delete conversation 51319928 (conn=266) in state SEND_DO_ACCEPT, due to accept timeout of 60 seconds

GwICheckAccept: delete conversation 51325929 (conn=1093) in state SEND_DO_ACCEPT, due to accept timeout of 60 seconds

GwICheckAccept: delete conversation 50325929 (conn=723) in state SEND_DO_ACCEPT, due to accept timeout of 60 seconds

*****************************************************************************

*

*  LOCATION    SAP-Gateway on host

*              sapgw10

*  ERROR       Conversation 51325929 not found

*

*  TIME        Mon Aug 15 08:41:02 2016

*  RELEASE     721

*  COMPONENT   SAP-Gateway

*  VERSION     2

*  RC          728

*  MODULE      gwxxconn.c

*  LINE        971

*  COUNTER     159320

*

Regards,

Vrinda

Former Member
0 Kudos

Hi,

Could you check the OSS note? it seems that it is related to timeout short dumps. Hope it will solve your issue.

2034087 - GW: "Timeout during accept" error message in trace file

Regards,

Ganesan

raquel_gomez
Employee
Employee

Hi Vrinda,

Return code rc=751 on the Gateway points to a timeout when accepting a connection [Timeout when logging on], and the only related prameter is 'gw/accept_timeout'.

See Notes:

  1950467 - GW: Parameter gw/accept_timeout does not work

  2034087 - GW: "Timeout during accept" error message in trace file

Regards,
Raquel

Answers (0)