Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
pbiwork
Frequent Visitor

"Unable to open document" message when attempting to open report in Power BI Desktop from PBIRS

Hello, we are using the March 2018 version of Power BI Report Server and Power BI Desktop. When we log in to PBIRS and click the "Edit in Power BI Desktop" option for a report, Power BI Desktop opens and presents this message: "Unable to open document Unexpected error encountered".

 

Any idea what might be causing this?

3 REPLIES 3
Psychemedics
Regular Visitor

We noticed that the issue consistently occurred based upon the Operating System of the workstation to which we download the Desktop App and the PBIX, as follows:

 

Original PBIX created on a Win 8 64 bit workstation with Report Server Desktop Application (Jan 2019).  Report uploaded to Report Server (Jan 2019) release.

 

Here's the reproducible behavior we experienced when downloading the Desktop App and the Report from Report Server (Jan 2019):

Workstation Win 7 64 bit            Unable to open document error.

Workstation Win 10 32 bit          Unable to open document error.

Workstation Win 10 64 bit          All works fine. 

 

Our takeaway is that PBI Desktop is unreliable/inconsistent unless we are using it with Win 10 64 bit.

 

 

 

 

 

Alexandru
New Member

Hello,
I don't know if this will help you or not, given the late response. I had a similar issue with our PowerBI Report Server, but it became active after disabling TLS 1.0. WHen left only with TLS 1.2 we could no longer:
a) acces an already existing report in PowerBI reportServer
b) uplod a new report using PowerBI report server upload butto
c) save a report to desktop using PowerBI Desktop Version
d) upload a new report to PowerBi report Server using power BI desktop.
I have to mention that both PowerBi Report Server and PowerBi Destopk were the March 2018 edition.
So we got help from Microsoft. Turns out that this is an .net Framework issue. It seems that if you use a .Net Framework higher than 3.5 you have to manually create some registration keys 

For your case you should see what TLS version you have enabled.

 

Resolution:
We solved the problem by adding two registry keys SchUseStrongCrypto and SystemDefaulTlsVersion. These keys are used during Report Services communication but not part of any direct code within the Reporting Services product. The TLS/SSL communication occurs within the Operating System negotiation between client and server. Any application installed on the server can make use of these new keys. In client side, the keys are supported and part of the .NET Framework 3.5 patches but are not forced to be enabled so they need to be enabled/updated where needed.
WHat we did:

1) Open Regedit

2) go to the following paths(see bellow) and add the encryption keys. You need to add them in the latestes .NetFramework version folders. In total you will have to add 4 reg keys: 2 for the SYSTEMDEFAULTTLSVERSIONS and 2 for the SCHUSESTRONGCRYPTO

Be sure to set the default value to 1.

 

SYSTEMDEFAULTTLSVERSIONS
========================================================================
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\<version>]
“SystemDefaultTlsVersions”=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\<version>]
“SystemDefaultTlsVersions”=dword:00000001  

SCHUSESTRONGCRYPTO
======================================================================
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\<version>]
“SchUseStrongCrypto”=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\<version>] 
“SchUseStrongCrypto”=dword:00000001


Applied these keys to the most recent .NET Framework available in the machine

"

example for SCHUSESTRONGCRYPTO

1) Open Regedit.

2) In the left Nav Form expapnd the following folders:

    I. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\<version>]

         a) Expand HKEY_LOCAL_MACHINE folder

         b) expand SOFTWARE folder

         c) expand Microsoft folder

         d) expand .NETFramework

         e) right click the folder for the latest version(mine was 4.0.30319) 

          f)  click NEW/ DWORD

          g) rename the new file as "SCHUSESTRONGCRYPTO"

          h) open it

          i) set the "valueData" to "1"

     II.  [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\<version>] 

         a) Expand HKEY_LOCAL_MACHINE folder

         b) expand SOFTWARE folder

         c) expand WOW6432Node folder

         d) expand Microsoft folder

         e) expand .NETFramework

         f) right click the folder for the latest version(mine was 4.5.50709) 

          g)  click NEW/ DWORD

          h) rename the new file as "SCHUSESTRONGCRYPTO"

          i) open it

          i) set the "valueData" to "1"

Do the exact same thing for SYSTEMDEFAULTTLSVERSIONS

 

 

Anonymous
Not applicable

Hmm... I think this is an security issue at the internet explorer. 

Please open the website locally on the server and ensure that the portal website is registered in the local intranet zone 

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.