If someone still experiances issues with Analyze in XL please send me an email and I will be happy to help you resolve the issue via Skype, my email is - email@example.com.
I had this issue today and first I tried to download all versions of SQL_AS_OLEDB.msi that I could possibly find but nothing worked, so then I did the EXACT OPPOSITE of what you just wrote: I replaced MSOLAP with MSOLAP.7 and saved the file. And then it worked!
it worked for me too - great suggestion!
I was also having this issue. When I opened the file it was already formatted with Provider=MSOLAP, I was able to replicate what @Lasselakan did in the file by adding .7, so now it reads Provider=MSOLAP.7 After this change I am able to load the odc file and use analyze in excel... @IlanH what version of excel were you using?
I am using Excel 2016 MSO 16.0.8730.2046 64-bit
and just this morning installed the lastest version of OLEDB
@tarostok Is there any reason why this would be causing an issue? Why would my newer 2016 version of excel require the MSOLAP.7? It is difficult to work with the analyze in excel function if I have to change every odc file I download from the service.
Excel click to run version include adal.dll version with bug in Analyze in Excel scenario.
Every Excel click to run installation will bring this adal.dll version.
To resolve this Excel must update adal.dll with fixed version.
As written in this thread there are 2 possible workarounds
1) Replace Excel click to run adal.dll - this need to be repeated after every Excel click to run update.
2) manually changing MSOLAP to MSOLAP.7 - the reason this work is that msolap.7 is using adal.dll without the bug
Good news: Excel are in the final stages of releasing updates with fixed adal.dll. Should be available by mid Jan.
Sorry for the inconvinience
With my newest Excel 365 Build 8827.2117 Click-and-run (Monthly Channel) it seems to just work now.
Have reinstalled the OLEDB driver from the Power BI website and now it JUST WORKS.
Can anybody confirm this? Or is it a coincidence?