Troubleshoot opening Power BI Desktop
This article describes and provides a remedy for a number of circumstances where Power BI cannot open.
Resolve issues with opening encrypted PBIX files
You cannot open encrypted PBIX files using a Power BI Desktop version that does not support information protection.
If you need to continue using Power BI Desktop, the recommended resolution is to update it to a version that supports information protection. You can download the latest version of Power BI Desktop (this link is a direct download link to the installation executable). The latest version of Power BI Desktop supports information protection and can decrypt and open any encrypted PBIX file.
Resolve issues with the On-premises data gateway and Power BI Desktop
In Power BI Desktop, users who installed and are running previous versions of the Power BI On-premises data gateway can be blocked from opening Power BI Desktop, because of administrative policy restrictions that the Power BI on-premises gateway placed on named pipes on the local machine.
You have three options to resolve the issue associated with the On-premises data gateway, and to enable Power BI Desktop to open:
Resolution 1: Install the latest version of Power BI On-premises data gateway
The latest version of the Power BI On-premises data gateway doesn't place named pipe restrictions on the local machine, and allows Power BI Desktop to open properly. If you need to continue using Power BI On-premises data gateway, the recommended resolution is to update it. You can download the latest version of Power BI On-premises data gateway. The link is a direct download link to the installation executable.
Resolution 2: Uninstall or stop the Power BI On-premises data gateway Microsoft service
You can uninstall the Power BI On-premises data gateway if you no longer need it. Or you can stop the Power BI On-premises data gateway Microsoft service, which removes the policy restriction and allows Power BI Desktop to open.
Resolution 3: Run Power BI Desktop with administrator privilege
You can instead successfully launch Power BI Desktop as administrator, which also allows Power BI Desktop to successfully open. It's still recommended that you install the latest version of Power BI On-premises data gateway, as described earlier.
Power BI Desktop is engineered as a multiprocess architecture, and several of these processes communicate using Windows named pipes. There may be other processes that interfere with those named pipes. The most common reason for such interference is security, including situations where antivirus software or firewalls may block the pipes or redirect traffic to a specific port. Opening Power BI Desktop with administrator privilege may resolve that issue. If you can't open with administrator privilege, ask your administrator to determine which security rules are preventing named pipes from properly communicating. Then, add Power BI Desktop and its respective subprocesses to allow lists.
Resolve issues when connecting to SQL Server
When you attempt to connect to a SQL Server database, you may come across an error message similar to the following text:
"An error happened while reading data from the provider:
'Could not load file or assembly 'System.EnterpriseServices, Version=126.96.36.199, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxx' or one of its dependencies.
Either a required impersonation level was not provided, or the provided impersonation level is invalid. (Exception from HRESULT: 0x80070542)'"
You can often resolve the issue if you open Power BI Desktop as an administrator before you make the SQL Server connection.
After you open Power BI Desktop as an administrator and establish the connection, the required DLLs are registered properly. After that, opening Power BI Desktop as an administrator isn't necessary. In cases where you are connecting to SQL server with alternate windows credentials, you will have to open Power BI Desktop as an administrator every time you connect.
"Unable to sign in" issue
You may see a message similar to this:
"Unable to sign in. Sorry, we encountered an error while trying to sign you in. Details: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."
Solution: You need to uncheck the Enable certification revocation check. See Certificate revocation check, Power BI Desktop for details.
Get help with other launch issues
We strive to cover as many issues that occur with Power BI Desktop as possible. We regularly look at issues that may be affecting many customers, and include them in our articles.
If the issue with opening Power BI Desktop isn't associated with the On-premises data gateway, or when the previous resolutions don't work, you can submit a support incident to Power BI support (https://support.powerbi.com) to help identify and solve your issue.
Should you come across other issues in the future with Power BI Desktop, it's helpful to turn on tracing and gather log files. Log files may help to isolate and identify the issue. To turn on tracing, choose File > Options and settings > Options, select Diagnostics, and then select Enable tracing. Power BI Desktop must be running to set this option, but it's helpful for future issues associated with opening Power BI Desktop.