Troubleshooting sign-in for Power BI Desktop

  • Article
  • iv minutes to read

There may be times when you attempt to sign in to Power BI Desktop just come across errors. In that location are 2 master reasons for sign-in trouble: Proxy Authentication errors and Non-HTTPS URL redirect errors.

To determine which problem is causing your sign-in outcome, the showtime step is to contact your administrator and provide diagnostic information so that they tin determine the cause of the result. By tracing bug associated with your sign-in problem, administrators can decide which of the following errors apply to you.

Let's accept a look at each of those bug in plow. At the stop of this article is a discussion on how to capture a trace in Power BI Desktop, which can help track down troubleshooting issues.

Proxy Authentication Required error

The post-obit screen shows an case of the Proxy Authentication Required error.

Sign-in error for Proxy Authentication error

The following exceptions in Ability BI Desktop trace files are associated with this fault:

  • Microsoft.PowerBI.Client.Windows.Services.PowerBIWebException
  • HttpStatusCode: ProxyAuthenticationRequired

When this mistake occurs, the about likely reason is that a proxy authentication server on your network is blocking the web requests issued by Ability BI Desktop.

If your network uses a proxy authentication server, your administrator tin fix this issue by adding the following domains to the allowlist on the proxy authentication server:

  • app.powerbi.com
  • api.powerbi.com
  • domains in the *.analysis.windows.net namespace

For customers who are part of a regime cloud, fixing this issue can be done past adding the post-obit domains to the allowlist on the proxy authentication server:

  • app.powerbigov.us
  • api.powerbigov.usa
  • domains in the *.assay.usgovcloudapi.net namespace

Non-HTTPS URL redirect not supported error

Current versions of Power BI Desktop use the electric current version of the Active Directory Authentication Library (ADAL), which does non allow a redirect to non-secured (not-HTTPS) URLs.

The following exceptions in Power BI Desktop trace files are associated with this error:

  • Microsoft.IdentityModel.Clients.ActiveDirectory.AdalServiceException: Not-HTTPS url redirect is not supported in webview
  • ErrorCode: non_https_redirect_failed

If the ErrorCode: non_https_redirect_failed occurs, it ways that one or more redirect pages or providers in the redirect concatenation is non an HTTPS protected endpoint, or that a certificate issuer of one or more redirects is not among the device'due south trusted roots. All providers in whatsoever sign-in redirect concatenation must utilize an HTTPS URL. To resolve this upshot, contact your administrator and request that secured URLs be used for their authentication sites.

How to collect a trace in Power BI Desktop

To collect a trace in Power BI Desktop, follow these steps:

  1. Enable tracing in Ability BI Desktop by going to File > Options and settings > Options then select Diagnostics from the options in the left pane. In the pane that appears, check the box adjacent to Enable tracing, as shown in the following epitome. You may be required to restart Ability BI Desktop.

    Enable tracing in Power BI Desktop

  2. So follow the steps that reproduce the error. When that occurs, Power BI Desktop adds events to the tracing log, which is kept on the local computer.

  3. Navigate to the Traces folder on your local computer. You can find that folder by selecting the link in the Diagnostics where you lot enabled tracing, shown as Open crash dump/traces folder in the previous prototype. Oft this is found on the local computer in the post-obit location:

    C:\Users/<user proper noun>/AppData/Local/Microsoft/Power BI Desktop/Traces

There may be many trace files in that folder. Make sure you but send the contempo files to your administrator to facilitate quickly identifying the error.

Using default organisation credentials for web proxy

Web requests issued by Ability BI Desktop practice not utilize spider web proxy credentials. In networks that apply a proxy server, Power BI Desktop may non exist able to successfully brand spider web requests.

System or network administrators tin allow the use of default system credentials for web proxy authentication. Administrators tin create a registry entry called UseDefaultCredentialsForProxy, and ready the value to one (1) to enable the use of default arrangement credentials for web proxy hallmark.

The registry entry can be placed in either of the post-obit locations:

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft Power BI Desktop] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Ability BI Desktop]

It is not necessary to accept the registry entry in both locations.

Registry key for using default system credentials

In one case the registry entry is created (a reboot may be necessary) the proxy settings defined in Cyberspace Explorer are used when Power BI Desktop makes spider web requests.

Every bit with any change to proxy or credential settings, there are security implications to creating this registry entry, so administrators must make certain they have configured the Net Explorer proxies correctly before enabling this feature.

Considerations and limitations

There are a collection of security implications that administrators should consider before enabling this capability.

The following recommendations should be followed whenever enabling this feature for clients:

  • But use Negotiation every bit the authentication scheme on the for the proxy server, to ensure just proxy servers that are joined to the Active Directory network are used by the client.
  • Do non use NTLM fallback on clients that use this feature.
  • If users are not on a network with a proxy when this feature is enabled and configured every bit recommended in this department, the process of attempting to contact the proxy server and using default system credentials is not used.
  • Power BI Desktop is not proxy-aware, and thus proxy mechanisms including Azure Awarding Proxy and other proxy services, will non work properly with Ability BI Desktop

Using default arrangement credentials for web proxy