Forum Discussion
SSMS 19 Bug - Error logging into XMLA Endpoint
Now that SSMS 19.0 has been released to the public, I continue to have trouble logging into the XMLA endpoint with SSMS. It works fine in SSMS 18. But when I try to log in to the XMLA endpoint in SSMS 19, I get a very lengthy error. This happens on multiple machines.
UNABLE TO OBTAIN AUTHENTICATION TOKEN USING THE CREDENTIALS PROVIDED
THERE WAS AN ERROR PARSING WS-TRUST RESPONSE FROM THE ENDPOINT
This never was and still isn't a problem in SSMS 18.
I already tried uninstalling and reinstalling a few times, and reinstalling/upgrading my ADO/OLEDB/ASP components (all the ones required) to the latest versions.
Is my Azure account messed up? Or does SSMS 19 not support XMLA Endpoint (yet)?
I have resolved the issue with the help of the Microsoft Power BI support team. You need to create an environment variable on your Windows PC (easiest way is to type "Edit the system environment variables" in the Start menu).
The variable should be named "MS_AS_EnforceAdalUsage", and the value should be set to "1". Then restart SSMS 19, and login to Power BI XMLA endpoint works.
The support engineer said this is a bug in SSMS and will be fixed in the next update to SSMS 19 (current at time of writing is 19.0.1)
19 Replies
I have resolved the issue with the help of the Microsoft Power BI support team. You need to create an environment variable on your Windows PC (easiest way is to type "Edit the system environment variables" in the Start menu).
The variable should be named "MS_AS_EnforceAdalUsage", and the value should be set to "1". Then restart SSMS 19, and login to Power BI XMLA endpoint works.
The support engineer said this is a bug in SSMS and will be fixed in the next update to SSMS 19 (current at time of writing is 19.0.1)
thank you very much AnonymousPerson I'll give it a try
AnonymousPerson it works for me also
it's a bug at the end of the day
This is the answer I needed, thanks AnonymousPerson!
Had this problem on Windows 11 fresh install and the newest SSMS 19.1.56.0 when connecting to Azure Analysis Services. Trick with MS_AS_EnforceAdalUsage fix the issue. Thanks a lot AnonymousPerson!
Encountered the same bug when connecting to Azure analysis services from SSMS v19.1
The fix with the environment variable worked 🙂I guess I will submit a case to Power BI support because the SSMS team is refusing to own this so far. I'll report back if I discover anything.
It would be great AnonymousPerson. MSFT seems not taking care about it, at least in the official post of SSMS 19.0
Hi GilbertQ
I tried running SSMS 19 as an admin and logging into the XMLA endpoint.
I do it exactly the same way in SSMS 18 and SSMS 19.
In SSMS 18 I can log right in (after passing MFA)
In SSMS 19 I get the error:
TITLE: Connect to Server ------------------------------ Cannot connect to powerbi://api.powerbi.com/v1.0/myorg/Operations. ------------------------------ ADDITIONAL INFORMATION: Unable to obtain authentication token using the credentials provided. (Microsoft.AnalysisServices.AdomdClient) ------------------------------ There was an error parsing WS-Trust response from the endpoint. This may occur if there is an issue with your ADFS configuration.Can anybody verify that XMLA endpoint is working in SSMS 19? I've scoured the documentation and I don't see anything about any breaking changes or known limitations in SSMS 19. It's weird.
Yeah that appears to be an error with SSMS 19.0
I am sure that this will be reported and a fix sent out soon!
AnonymousPerson is that a PPU, Premium capacity or embeeded? facing same issue on PPU and embedded not a capacity... it seems... those are on 2 different tenants so I cannot be 100% sure it's not "tenant based issue"
Same issue here 18.x works fine, 19.x fails trying windows auth, 19.01 does not fix the issue (not listed in the bug fixes either).
John
AnonymousPerson I had same answer from microsoft. they're not considering as a bug but a problem with our tenant... my network guys are confused because we actually don't use ADFS...
Same problem for me accessing with MFA. Downgraded to v18 and working fine now. We'll wait for a bug fix in v19 from Microsoft.
Still using this to fix this issue in SMSS 19.1.56 😕
