Most common SAP-issues

Updated 10 months ago by Stephanie Krenz

This article lists various mesages from dab Nexus. In the corresponding section, you will find possible causes as well as recommondation on how to rectify the issue.

RfcConnection failed (RFC_LOGON_FAILURE): Name or password is incorrect (repeat logon)

Possible Cause: Wrong User

  • The user name was misspelled or the user doesn't exist.

Recommendation (if you have the authorizations in the SAP system)

  • Check the spelling of the user namen.
  • Check user name in SAP:
    • Call transaction SU01
    • Insert user name and check the spelling
    • Adjust the user name in dab Nexus
  • If the user doesn't exist in SAP:
    • Call transaction SU01
    • Create and save user
    • Insert the user name in dab Nexus

Recommendation (if you have not the authorizations in the SAP system)

  • In this case, your IT team/SAP team can help you.

Possible Cause: Wrong password

  • The password was misspelled or changed in the SAP system.

Recommendation

  • Check the spelling of the password
  • Logon in the SAP system with the corresponding user:
    • If no login is possible:
      • Reset user and password - your IT team/SAP team can help you
      • Insert new password in dab Nexus
    • If login is possible:
      • Check the spelling in dab Nexus again

Possible Cause: Wrong Client

  • The client in dab Nexus was misspelled.

Recommendation

  • Check the client and adjust it in dab Nexus.

Possible Cause: SAP user is locked

  • The user is locked in the SAP system.

Recommendation (if you have the authorizations in the SAP system)

  • Call transaction SU01
  • Insert user and unlock it (Padlock-symbol)
  • Reset the password if necessary

Recommendation (if you have not the authorizations in the SAP system)

  • In this case, your IT team/SAP team can help you. They can unlock the user and reset the password if necessary.

RfcInvoke failed(RFC_ABAP_EXCEPTION): FU_NOT_FOUND

Possible Cause: Function module is misspelled or was installed with another name in the SAP system

  • The name of the function module is misspelled in dab Nexus or the function module was installed with another name in the SAP system.

Recommendation

  • Call transaction SE37
  • Inser the name of the function module and press Enter
  • Press F8 on your keyboard or click on the Scale on the menu line
  • If the message Function module xyz does not exist occurs, the module was not found in the SAP system
  • Shorten the name in the input field and add an asterisk (*), then open the input help F4 and search for the module
  • If the module was found, adjust the name in dab Nexus

Possible Cause: Function module isn't installed in SAP

  • The function module wasn't installed yet.

Recommendation (if you have the authorizations in the SAP system)

  • If the function module could not be found (the search is described in the previous point), you can find all information on installing the SAP AddOn here.

Recommendation (if you have not the authorizations in the SAP system)

  • In this case, your IT team/SAP team can help you. They can install the function module in the SAP system with this article.

Cannot find element 'DELIMITER'

Possible Cause: Certified function module was installed, but Z-module was selected in dab Nexus

  • The certified function module was installed in the SAP system, but the Z-module was selected in dab Nexus.

Recommendation

  • Adjust the settings in dab Nexus from Z-module to Certified Module.

Cannot find element 'PING'

Possible Cause: Z-module was installed, but certified module was selected in dab Nexus

  • The Z-module was installed in the SAP system, but the certified function module was selected in dab Nexus.

Recommendation

  • Adjust the settings in dab Nexus fom Certified Module to Z-module.

Cannot access librfc32.dll. Please put a 32-bit version of librfc32.dll in your SysWow64 folder (typically C:\Windows\SysWow64) or inside the folder C:\Program Files\dabGmbH\neXus\dabSapTunnel

Possible Cause: librfc32.dll is missing

  • The data librfc32.dll could not be found in the directory.

Recommendation

  • Place the file librfc32.dll in the directory C:\Windows\SysWow64 or the directory C:\Program Files\dabGmbH\neXus\dabSapTunnel. All information can be found in this article.

RfcOpenConnection failed (RFC_COMMUNICATION_FAILURE): LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '?' not reached

Possible Cause: IP-adress/Host wrong

  • The IP-adress or the hostname is misspelled.

Recommendation

  • Check the hostname and adjust if necessary.

Possible Cause: Wrong instance number

  • The instance number of the SAP system was misspelled in dab Nexus.

Recommendation

  • Check and adjust the instance number in dab Nexus.

Possible Cause: Problem with network connection

  • There is a network problem and the SAP system cannot be reached.

Recommendation

  • In this case, your IT team/SAP team can help you. They can check and rectify the cause. Afterwards you can test the connection again.

RfcOpenConnection failed (RFC_COMMUNICATION_FAILURE): ERROR service '?' unknown

Possible Cause: SAP system is missing in the services file

  • The entry for the SAP system is missing in the services fileDer Eintrag für das SAP-System fehlt in der services-Datei.

Recommendation

  • Add the SAP system in the services file. You can find more information here.

RfcOpenConnection failed(RFC_LOGON_FAILURE): Select one of the installed languages

Possible Cause: Language is not installed in the SAP system

  • The choosen language is not installed in the SAP system.

Recommendation

  • Change the language to English in dab Nexus, this should be installed by default on the SAP system. Then test the connection again.
  • Alternatively, you can contact your IT team/SAP team if additional languages are to be installed in the SAP system.

No RFC authorization for function module /DABEXP/RFC_SAPCONNECTOR

Possible Cause: No authorizations

  • No authorization to access function module.

Recommendation

  • You find all information in this article, section Authorizations.

SAP System Test failed after retrying with T001: RfcInvoke failed(RFC_ABAP_EXCEPTION): NOT_AUTHORIZED

Possible Cause: No authorization for test table

  • No authorization to access the test table T001.

Recommendation

  • Give the SAP user the required authorization to access the test table.

Possible Cause: No authorization -> Change test table

  • No authorization to access the test table T001.

Recommendation

  • In dab Nexus, change the test table to one that the SAP user can access.

RfcOpenConnection failed (RFC_COMMUNICATION_FAILURE): LOCATION CPIC (TCP/IP) on local host with Unicode ERROR hostname '?' unknown

Possible Cause: DNS doesn't resolve hostname

  • The DNS doesn't resolve the host name.

Recommendation

  • Please contact your IT team in this case.

How did we do?

Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)