Versions Compared

Version Old Version 27 New Version 28
Changes made by

Darcy Curtin

Darcy Curtin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Some of the common issues seen when NLINK tries to connect to SAP are documented here.

See Test SAP Connectivity with the NMM for more information about the Test Connection tool in the NLINK applications.

Common Errors

  1. Missing User Id / Password

    If you see the following error:

    Code Block
    languagetext
    titleCALL_FUNCTION_SIGNON_INCOMPL
    CoNNector:: SAP XXX CoNNector: Unable to log on to destination YYYY.
Error message:
KEY=CALL_FUNCTION_SIGNON_INCOMPL
Message= Incomplete logon data..


    Solution: Check your user id / password values


  2. Wrong Client

    If you see the following error:

    Code Block
    titleRFC_LOGON_FAILURE
    Key 'RFC_LOGON_FAILURE': Message 'Name or password is incorrect (repeat logon)'

    Solution:

    1. double-check your user id and password (passwords are case-sensitive)

    2. verify that your user id exists in the client you are trying to connect to


  3. Problem connecting to load balanced SAP, Service Unknown

    For outbound SAP connection such as  SAP RFC/BAPI, SAP Query, SAP Transaction or SAP IDOC (IDOC sent from NLINK to SAP) External Systems, if following error occurs

    Code Block
    titleRFC_LOGON_FAILURE
    Key=RFC_COMMUNICATION_FAILURE
Message=
LOCATION    CPIC (TCP/IP) on local host SomeHostName with Unicode
ERROR       service '?' unknown
TIME        Wed Jul 1 10:22:59 2015
RELEASE     721
COMPONENT   NI (network interface)
VERSION     40
RC          -3
DETAIL      NiErrSet
COUNTER     3

    Solution: Specify the actual port value for MSSERV parameter, e.g., MSSERV=3601 instead of MSSERV=sapms01.



  4. Service Unknown / GWSERV not found

    In some cases the IDOC or RFC Listener connections fail to register properly, even if the proper GWSERV parameter is specified:

    Code Block
    languagetext
    titleRFC_COMMUNICATION_FAILURE
    External System: 
CoNNector:: SAP IDOC CoNNector: Could not connect to SAP system. Will retry. SAP47U_IDOC: 
KEY=RFC_COMMUNICATION_FAILURE 
Message= 
ERROR       service ’?’ unknown 
TIME        Fri Sep 10 14:32:59 201 
RELEASE     711 
COMPONENT   NI (network interface) 
VERSION     39 RC          -3 
DETAIL      NiErrSet 
COUNTER     2
 
or
 
External System: 
CoNNector:: SAP IDOC CoNNector: Could not connect to SAP system. Will retry. SAP47U_IDOC: 
KEY=RFC_COMMUNICATION_FAILURE 
Message= 
ERROR       service ‘sapgw01’ unknown 
TIME        Fri Sep 10 14:32:59 201 
RELEASE     711 
COMPONENT   NI (network interface) 
VERSION     39 RC          -3 
MODULE      nixxhsl.cpp 
LINE        665 
DETAIL      NiHsLGetServNo: service name cached as unknown 
COUNTER     1


    Solution: Specify the actual port in the GWSERV parameter, e.g., GWSERV=3301 instead of GWSERV=sapgw01.


  5. WSAENOBUFS: No buffer space available

    When trying to register RFC Listener or IDOC, the connection gets disconnected almost immediately. Get entries in log file similar to the following:

    Code Block
    "SAP RFC Listener CoNNector: Successfully connected to SAP system." 
"CoNNector:: SAP RFC Listener CoNNector: Unable to connect to SAP. Will retry."

KEY=RFC_COMMUNICATION_FAILURE
Message=
ERROR    internal error
TIME    WWW MMM DD HH:MM:SS 201
RELEASE  NNN
COMPONENT  NI(network interface)
VERSION  NN
RC            -1
MODULE        nixxi.cpp
LINE    2781
DETAIL    NiIConnectSocket
SYSTEM CALL connect
ERRNO    10055
ERRNO TEXT WSAENOBUFS: No buffer space available
COUNTER  66722


    Solution: This can be caused by SAP Gateway security rule that blocks requests from an external RFC Server. 


  6. Invalid Parameter

    If you see the following message, 

    Code Block
    languagetext
    titleRFC_INVALID_PARAMETER
    Key 'RFC_INVALID_PARAMETER': 
Message 'Parameter ASHOST, GWHOST or MSHOST is missing.'


    Solution: Check the format, spelling and completeness of the parameters in your SAPNWRFC.INI file. Refer to the sample file for correct entries. Make sure value specified for "DEST" is not same as SAP System ID. For example if SAP System ID is "AB2" and value for "DEST" in SAPNWRFC.INI is specified as "AB2" it can cause this error.

  7. NLINK cannot process received IDOC

    NLINK cannot process received IDOC. IT cannot resolve IDOC Type or Message Type properly, Event log shows IDOC Type '           ?????????????' 

    Solution: In SAP transaction SM59, make sure corresponding RFC Destination is setup to use Unicode

  8. IDOC (receiving) disconnecting few seconds after reconnect
    When using IDOC or RFC Listener, the NLINK connection to SAP is broken with ABAP_RUNTIME_FAILURE, "external RFC Client not supported. NLINK reconnects but gets disconnected after few seconds with error

    Solution: In SAP transaction SM59, make sure corresponding RFC Destination is setup to use Unicode

     

  9. RFC Listener or IDOC (receiving) disconnecting immediately after reconnect

    When using IDOC or RFC Listener, the NLINK connection to SAP is broken (with RFC_COMMUNICATION_FAILURE  error) as soon as reconnected message. Or on NLINK 6.0.0.140 (or earlier) NLINK crashes when using RFC Listener or IDOC connector (to receive IDOC). If you look at dev_rfc.trc or NLINK logs you can find message "registration of tp * from host * not allowed". NLINK 6.0.0.140 (or earlier) crash at start up with this issue. NLINK 6.0.0.142 (or later) reconnection attempts at start up may see many connect / disconnect messages. 

    Solution:If the SAP Gateway is setup to block incoming RFC function registration then SAP Gateway will allow connection to be established but breaks connection as soon as RFC function registration is attempted.  Check and make sure SAP Gateway allows connections to NLINK connections. 


  10. RFC Listener or IDOC (receiving) NLINK logs show connection as registered but cannot see connection in SAP
    When using IDOC or RFC Listener, the NLINK logs show that connection is established but the connection cannot be found in SMGW→Logged on Clients. Also the connection test from SM59 fails

    Solution: This can occur if SAP Gateway is not correctly specified in SAP SM59 transaction. Make sure proper Gateway options are specified.


  11. Cannot Launch SAPGUI for Debugging

    When trying to step into ABAP code for debugging, get an error ”SYSTEM_PREPARE_ATTACH_GUI not found”.

    Solution: To use RFC with SAPGUI, the new library needs at least the following support packs to be installed:

    1. SAP_BASIS     46C     SAPKB46C58

    2. SAP_BASIS     620     SAPKB62066

    3. SAP_BASIS     640     SAPKB64025

    4. SAP_BASIS     700     SAPKB70020

    5. SAP_BASIS     701     SAPKB70103

    6. SAP_BASIS     710     SAPKB71008

    7. SAP_BASIS     711     SAPKB71102


  12. Can Connect via SAPGUI but not via NLINK

    If you can connect from the NLINK machine via SAPGUI but not via NLINK, and you see the following error, check that ports 33xx are open.

    Code Block
    Key 'RFC_COMMUNICATION_FAILURE':
Message ' LOCATION    CPIC (TCP/IP) on local host with Unicode 
ERROR       partner '111.22.333.44:33xx' not reached


    Solution: The following ports must be open (where ## is the SAP system number):

    1. GUI (dispatcher, sapdp##): 32##

    2. RFC (gateway, sapgw##): 33##

    3. Load Balancing (message server, sapms##): 36##

  13. NLINK IDOC CoNNector (SAP→NLINK) does not register even though SAP is destination is correct


    When NLINK is configured to receive IDOCs from SAP, NLINK fails to register. At start up see message "Could not connect ot SAP, will retry after x seconds"

    Solution: Check the logs folder for any messages. This can occur if the SAP user ID and Password are not correct for SAP system. For NLINK IDOC CoNNector, at start up NLINK reads IDOC RFC meta information from SAP, if the credentials are not correct then incorrect message is displayed. 

  14. NLINK RFC Listener, no data is received from SAP 
    Configured meta-database to match the SAP CALL FUNCTION, but not getting data in NLINK.

    Solution: Check to make sure parameter name and case match exactly to what is configured in SAP. Also for parameters sent from SAP → NLINK they need to be marked as "EXPORTING" in SAP. Corresponding parameters in NLINK should be "IMPORT" parameters. In NCM, Parameter names are Message Format Table Attributes. The case for field names for each parameter also has to match in SAP as well as NLINK meta-database. The field names are configured as Message Format Field Attributes.

  15. NLINK RFC Listener, "Function XYZ not found" error in SAP
    Configured SAP System ID (3 character ID) should exactly match the SAP System ID from where request is sent. Even with incorrect SAP System ID, the connection test from SM59 will work. The SMGW→Logged on Clients will also look fine. But when request is sent from SAP the request fails because SAP System ID does not match.

    If there are other functions are working from same SAP system, then make sure meta-database is configured to receive remote function in question. Corresponding Event Attribute in NLINK meta-database should match the request.

    Solution: Check to make sure SAP System ID is correct. To verify the SAP System ID from the SAP GUI, look in the popup menu at the bottom right of the screen:


    If you do not see the popup menu, look for a small triangle in the bottom right corner. Click it to slide open the information tray.


    To verify the list of functions registered in SAP, run the Extras >> Function List test from SM59.

  16. NLINK IDoc or RFC Listener disallowed from registration due to gateway security
    The SAP secinfo and/or reginfo settings in the SAP System Gateway may not be configured to allow the NLINK Server to register. This is a matter for the SAP BASIS / security administrators. SAP Note 1408081 may be helpful.

    Code Block
    titleError Message in NMM if IP address in reginfo is incorrect
    SAP IDOC callback terminated because of connection issue. Will try to reconnect in 900 seconds.
This can be caused by network disruption.
 
OR
 
SAP gateway disconnecting RFC connections because of authorization.
'SAP IDOC' (17), SAP 'saphostname', SAP System Id 'ABC', Program_ID ''.
 
KEY=RFC_COMMUNICATION_FAILURE
Message=
LOCATION    SAP-Gateway on host somesaphostname / sapgwxx
ERROR       registration of tp registering_program_id from PROXY host
            123.456.789.000 not allowed
TIME        Wed Jun 27 12:49:36 2018
RELEASE     742
COMPONENT   SAP-Gateway
VERSION     2
RC          756
MODULE      D:/depot/bas/742_REL/src/krn/si/gw/gwxxrd.c
LINE        3619
COUNTER     867964


...