KNOWLEDGE BASE

Errors: "Invalid Username or Password" or "Database error 0x80040E4D: Authorization failed" When Connecting to SAP BW


Published: 27 Dec 2016
Last Modified Date: 04 Sep 2018

Issue

When attempting to connect to SAP BW, the following errors might occur:
 
"Invalid Username or Password"

Or

"Database error 0x80040E4D: Authorization failed"

Environment

  • Tableau Desktop 
  • SAP NetWeaver Business Warehouse

Resolution

Option 1:
 If SAP is using default ports, ensure that ports 3200 and 3300 are open.
  • 3200 is the dispatcher port, used by SAP GUI (SAP Logon).
  • 3300 is the gateway port, used by any application that relies on the saplogon.ini file.
Additionally, work with your IT team to ensure that no internal firewalls are blocking additional ports. 

Option 2:
Work with your Database Administrator to perform the following steps: 
  1. Open SAP Logon
  2. Right-click on the Connection and select Properties.
  3. Access the Network tab and uncheck Activate Secure Network Communication.
Option 3:
Work with your Database Administrator to ensure that the credentials used do not conflict with the SAP BW minimum number of special characters for passwords requirement. This requirement is set by your database administrator. 

Option 4:
When using both SSO and Kerberos
  • Make sure that SAP BW is configured for SSO. See Configure Single Sign On for SAP BW for more information.
  • Confirm that Kerberos is using a single-hop token which transmits the logged-in user's credentials, and not a double-hop which is passing different login credentials.

Cause

One of the following:
The ports needed by SAP were blocked
SAP needed to be configured to allow SNC
The credentials used conflicted with the minimum requirement for special characters in SAP password set by your database administrator.

Additional Information

Profile Parameters for Logon and Password (Login Parameters) by SAP

Note: The above blog post is hosted on a third-party website. Please note that while we make every effort to keep references to third-party content accurate and up to date, the information we provide here might change without notice.

Did this article resolve the issue?