"Key length 40" error only in PBI Desktop "App" version

[leesm1thy]

Hi,

I have a number of PBIX files that return an error message I don't understand when opened in the Power BI Desktop "App" version installed from the Microsoft Store, but work fine in the standard installer version.

The specified key is not a valid size for this algorithm. Parameter name: key Key Length: 40

It makes me nervous to install the very latest version but I will have to at some point.  In all cases the data is being pulled from a SQL Server instance. 

Does anyone know what this error is and how to resolve it?

Thanks in advance.

[Greg_Deckler · Accepted solution]

You could check the Issues forum here:

https://community.powerbi.com/t5/Issues/idb-p/Issues

And if it is not there, then you could post it.

If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".

[v-kelly-msft]

Hi @leesm1thy ，

Try to downgrade the version of desktop to the release in Feb 2020 via below link ,it seems a version incompatibility issue.

https://microsoftapc-my.sharepoint.com/:u:/g/personal/v-kellya_microsoft_com/EXKbx2sMjQxFhboQX1-9GpU...

 
Best Regards,
Kelly

Did I answer your question? Mark my post as a solution!

[Greg_Deckler · Accepted solution]

You could check the Issues forum here:

https://community.powerbi.com/t5/Issues/idb-p/Issues

And if it is not there, then you could post it.

If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".

[leesm1thy · Accepted solution]

For the benefit of Googlers with this same issue, I did indeed (eventually) log the issue with the Power BI support team. The advice given to me was delete everything at the following two paths:

C:\Users\%username%\Microsoft\Power BI Desktop Store App\Cache

C:\Users\%username%\Microsoft\Power BI Desktop Store App\CEF\cache

Doing so resolved my issue where the PQ editor woudn't return anything from a SQL Server database, but I suspect from my own searching on the subject that this error message may present itself in a number of scenarios.