Skip to Content

Generated internal RFC connection does not work after AS/CS-split - error in SM58

Hello together,

since we have performed the AS/CS split in our ERP System E10 we face problems with some transactions (IW31, IW31) regarding the transactional RFCs to the internal system.

When I look into SM58 I see the entrys with the error: "Error when opening an RFC connection".

The function module is "SHARED_BUFFER_DELETE" and the target system is "ie10cs10_E10_10" which indicates that the target system is the central instance.

But of course the transaction itself is started on the dialogue instance (ie10di31).

When I doubleclick on the target system column in SM58 I come to the internal RFC which is automatically generated.

Trying a connection test shows the following error:

ERROR: Gateway not connected to local R/3

LOCATION: SAP-Gateway on host ie10cs10...... / 3310

COMPONENT: SAP-Gateway

MODULE: gwxxrd.c

RETURN CODE: 726

When I check the internal RFCs in SM59 I can only find another RFC Destination with the name "ie10di31_E10_31" - so this would be the dialogue instance.

I do not understand how the internal RFCs are created automatically and why I see the central instance in the SM58 as target system but only the dialogue instance RFC is visible in SM58 under type "I" connections.

I hope I could explain the issue......your help would be really appreciated.

Thanks a lot in advance and regards

Günter

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2016 at 12:37 PM

    Hi Gunter,

    Make sure you have entries for dialog, central instance and ascs instance details in services files on each host.

    Also you are able to telnet between these host.

    Regards

    Prithviraj

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2016 at 12:42 PM

    Hi Güter,

    I've never done a ASC/SC split, but maybe the instance number of the gateway change to the default 3300?

    Trying a connection test shows the following error:

    ERROR: Gateway not connected to local R/3

    LOCATION: SAP-Gateway on host ie10cs10...... / 3310

    COMPONENT: SAP-Gateway

    MODULE: gwxxrd.c

    RETURN CODE: 726

    change the instance of your gateway to:

    sapgw00

    or

    3300

    Cheers

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 16, 2016 at 09:18 PM

    Hello Günter,

    Whenever an ABAP isntance starts, it creates an internal destination.

    Use the transaction SE16 do see the contents of the table RFCDES.

    You can filter for the type of destination (internal).

    If you see incorrect / old entries (for internal destinations!) there, you should delete them.

    Best regards,

    Isaías

    Add a comment
    10|10000 characters needed characters exceeded

    • Hello Isaias,

      thanks - great to know now that the instance always creates the internal destination pointing to ITSELF!

      I tought that this maybe can be influenced by any (wrong) parameter that causes the internal RFC to be created to the wrong instance.

      The original CI before the split was named "ie10ci10_E10_10" - so only the "ci" was changed to "cs" which is the new CI now - and of course the additional DIs exist.

      So I am quite sure now that the problem is located somewhere in the application as it is the one which creates the SM58 entries containing the wrong destination.

      Hope this is the case and will update the result her.

      Best regards

      Günter

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.