JR54388: ABAP STAGE RUNTIME (DS JOB) FAILS TO CONNECT TO SAP IF ANONYMOUS LOGON IS NOT PERMITTED.

APAR status

• Closed as program error.

Error description

• ABAP stage runtime fails to connect to SAP if anonymous logon is
  not permitted. The other stages (BAPI and IDOC) and the IDOC
  RFC Manager don't have the issue.
  The error in the job log is:
  Fatal Error: Fatal: ABAP_E_00188`:`SAP Logon failed : SAP Error:
  Opening connection RC: 3, Error key:
  CALL_FUNCTION_SIGNON_INCOMPL Error Message: Incomplete logon
  data.
  

Local fix

• Before connecting to SAP with a regular logon with user and
  password, the stages try to do an anonymous logon with the
  purpose of getting the SAP Server code page (as to be able to
  display an intelligible message to the user in case the regular
  logon fails).
  When the SAP Server has the profile parameter
  auth/rfc_authority_check set to a value more restrictive than
  the default 1 (for example 9), anonymous logon may not be
  permitted.
  The workaround is to set this parameter back to the default 1.
  

Problem summary

• ABAP stage runtime fails to connect to SAP if anonymous logon is
   not permitted. The error in the ABAP job log is:
  Fatal Error: Fatal: ABAP_E_00188`:`SAP Logon failed : SAP Error:
  Opening connection RC: 3, Error key:
  CALL_FUNCTION_SIGNON_INCOMPL Error Message: Incomplete logon
  data.
  The other stages (BAPI and IDOC) and the IDOC RFC Manager don't
  have the issue.
  
  Same issue was previously reported and fixed for the Client side
  (GUI) in APAR JR54109
  

Problem conclusion

• CAUSE:
  Before connecting to SAP with a regular logon with user and
  password, the stage tries to do an anonymous logon with the
  purpose of getting the SAP Server code page (as to be able to
  display an intelligible message to the user in case the regular
  logon fails).
  When the SAP Server has the profile parameter
  auth/rfc_authority_check set to a value more restrictive than
  the default 1 (for example 9), anonymous logon may not be
  permitted.
  The workaround is to set this parameter back to the default 1.
  
  RESOLUTION:
  Implemented a code fix, where if the initial anonymous logon
  fails, we continue with the regular logon (with the risk of
  getting an un-intelligible detail message if the regular logon
  fails).
  If the regular logon fails the user will still be getting an
  error message "Unable to connect to the SAP System" and the
  error key, but the detail message (eg. "Incorrect user or
  password") may be unable to display.
  
  Code fix: continue with regular logon assuming non-unicode SAP
  Server until getting the connection attributes.
  
  Fix available as a patch for releases 70, 71, 80.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IS PACK FOR SAP

• Fixed component ID

  5724Q5500

Applicable component levels

• R700 PSY

     UP

• R710 PSY

     UP

• R800 PSY

     UP