AADSTS50011: Error occured when some users want to access Azure Analysis Service via Excel

Joko Himawan 46

Hello,

I got the report from user that want to access Azure Analysis Service via Excel that an error has occured. From what I've read it has something to do with Azure Active Directory, but I can't find the solution yet (many of the documentations suggested to put the url on 'App Registration', however I can't find the application).

This is the detail of the error when some users wants to access AAS via Excel:

(Edit: I got additional information from the user, that there is an Office365 issue for some users (can't login). Is it relevant AADSTS50011's error?)

Any information and assistance, will be much appreciated. Thanks!

MarekSuwart 6 Reputation points

2021-07-05T15:52:30.03+00:00

the same issue here, but when logging in throught ssms on our servers :/ - libraries updated. Cant figure out that is the problem
Joko Himawan 46 Reputation points

2021-07-06T08:34:21.38+00:00

Hi @MarekSuwart . Probably updating your SSMS' version to the latest would help? Hope this will help you
MarekSuwart 6 Reputation points

2021-07-06T08:57:11.17+00:00

Exactly this is what it finally realized yesterday, there was an SSMS form 2018 installed, installing the newest one, solve the issue ;)
Anshul Kumar (MINDTREE LIMITED) 6 Reputation points

2021-10-07T17:31:31.187+00:00

Hi, if the posted answer resolves your question, please mark it as the answer by clicking the check mark. Doing so helps others find answers to their questions.

15 answers

Tony Valentine 116 Reputation points

2021-07-08T19:19:45.507+00:00

This is an epic disaster. We have customers that use our models via Excel that are in the "Semi-Annual Enterprise Channel" that fail. These are multi-billion dollar companies so it's not exactly easy to get them go through their IT departments to get this resolved. How can you roll out these changes prior to all Office update channels having the change?!? Rollback now!!
Please sign in to rate this answer.

3 people found this answer helpful.
Lasse Matthias 1 Reputation point

2021-07-08T20:55:14.263+00:00

My thoughts exactly.
Sign in to comment
Ole Thomsen 16 Reputation points

2021-07-05T10:03:03.117+00:00

We have exactly same problem with Azure Analysis Services Client, starting saturday.

Upgrading the libraries did not solve it.
Please sign in to rate this answer.

2 people found this answer helpful.
Joko Himawan 46 Reputation points

2021-07-05T11:20:16.573+00:00

Hi @Ole Thomsen . After you installed/upgrade three of the client libraries, if you access the Analysis Service via Excel, you can replace the AS OLEDB in Microsoft Office directory with copying the AS OLEDB from MSOLAP.

Copy from: C:\Program Files\Microsoft Analysis Services\AS OLEDB\140 (after you installed the MSOLAP)

To: C:\Program Files\Microsoft Office\root\vfs\ProgramFilesX64\Microsoft Analysis Services\AS OLEDB\140\ (replace the existing folder and it's contain with the one from MSOLAP)

Don't forget to make a backup of AS OLEDB folder from Office's directory. (Just in case something happens)

I hope it will help.

Ole Thomsen 16 Reputation points

2021-07-05T12:08:45.48+00:00

Thanks a lot, that works!

Cedric FK_finelog 206 Reputation points

2021-07-06T07:10:43.307+00:00

Hi @AmanpreetSingh-MSFT ,
the solution provide by @Joko Himawan work well (copying manually in Office folder) now my question is what are we supposed to do in a company where users don't have rights to to this kind of things and mostly when Office updates follow some company rules.
What are we supposed to "update" to get the things back in order.

Moreover, having this error now from multiple different clients looks like it's more a change in Azure Analysis Service side which introduce this connectivity issue with certain Office versions.

Regards
Cedric

Ole Thomsen 16 Reputation points

2021-07-06T07:58:04.323+00:00

@Cedric FK_finelog I totally agree. Whatever Microsoft did in their backend during the weekend, they should roll back.

We have raised a ticket with Microsoft.

Tony Valentine 116 Reputation points

2021-07-07T15:45:28.74+00:00

Same problem here. This is an outage for our customers. Please roll back the weekend change MSFT!
Sign in to comment
Koppenol, Steven 11 Reputation points

2021-07-05T14:26:10.233+00:00

Updating office (2019) did not work for me. After updating office and the client libraries, I looked into the folder mentioned by coenenp-6641 and found that that was still out of date.

Manually copying the entire folder from C:\Program Files\Microsoft Analysis Services\AS OLEDB\140 to C:\Program Files\Microsoft Office\root\vfs\ProgramFilesX64\Microsoft Analysis Services\AS OLEDB\140 solved the issue
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment
Valer Simina 16 Reputation points

2021-07-07T11:08:59.76+00:00

Hello,

We have the same issue (same app ID) while trying to deploy models to AZURE Analysis Services Server using Visual Studio. We have updated all OLEDB drivers, without any luck.

This seems to be a widespread issue.

Are there any updates?
Please sign in to rate this answer.

2 people found this answer helpful.
MarekSuwart 6 Reputation points

2021-07-07T11:27:51.727+00:00

it seems like you also need to update the whole studio , i had similar issue with SSMS version 17 , updatig libraries didn solve the issue, only updating SSMS to latest versin (18) did the job

IdahoSkiGirl 6 Reputation points

2021-07-07T13:00:06.723+00:00

I am still having the same issue as you. All libraries/drivers are updated. I have manually copied the folder (as suggested above). My VS version and my SSMS versions are both up to date. I spent most of yesterday just thinking I was losing my mind, glad to know I am not alone. I'll report back if I find a solution!

Valer Simina 16 Reputation points

2021-07-07T14:16:27.273+00:00

IIf it helps, my Excel and SSMS were working fine prior to updating the drivers and still do. My only beef is with Visual Studio model deployment.

Valer Simina 16 Reputation points

2021-07-07T14:16:46.49+00:00

Thanks for the suggestion, I have tried updating Visual Studio 2017 to the latest version, but again without any luck. Will try it on VS 2019 and report back.

IdahoSkiGirl 6 Reputation points

2021-07-07T20:05:06.857+00:00

@Valer Simina I have a solution that worked for me - do you ever use Tabular Editor? My coworker does and suggested I try it - I opened my .bim file in tabular editor and deployed without issue.

Valer Simina 16 Reputation points

2021-07-12T13:28:14.12+00:00

Hi,

I have tried tabular editor but it didn't work for me (something related to the security users.)

What did work for me is installing the latest SSDT (https://go.microsoft.com/fwlink/?linkid=2161172) see and alone installer. Now I can apply continue my work using Visual Studio 2017.
Sign in to comment
AJ 16 Reputation points

2021-07-07T15:55:47.31+00:00
Facing the same issue since couple of days. Raised a ticket with Microsoft and this was the reply I got:

We are retiring the old client libs because of TLS 1.2 and insecure redirects. At the end of June 2021, AAD will stop accepting insecure connections.

So here the action plan :

Update SSMS to 18.9.1.
https://learn.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15

Update AS Client Libraries to latest and restart local machine.
https://learn.microsoft.com/en-us/analysis-services/client-libraries?view=asallproducts-allversions

Our client libraries were already up-to-date. We have updated SSMS to 18.9.1 now but still the error persists.
Please sign in to rate this answer.

2 people found this answer helpful.
Felipe Souza 1 Reputation point

2021-07-07T21:40:49.09+00:00

@AJ Did you solve the problem? Is Updated Office a final solution?

AJ 16 Reputation points

2021-07-08T07:09:06.34+00:00

nope, it did not work

Ella Calais 1 Reputation point

2021-11-10T13:44:12.71+00:00

@AJ Hi! Did you get this issue resolved? Several months have passed and I'm curious if you've come up with a solution :)
Sign in to comment