Forum Discussion
SSMS 19 Bug - Error logging into XMLA Endpoint
- 3 years ago
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)
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!
GilbertQ It does appear to be a bug in SSMS 19.0. But I heard back from MS on the issue and they said contact my "network folks" (who have actual issues to handle). Microsoft isn't owning this.
So I am still wondering how I am the only person in the world that SSMS 19 XMLA Endpoint connections won't work for. I guess my MS365 tennant must be very unique. 🙄
- eduecker3 years agoRegular Visitor
You are not the only person. I have had this exact same issue ever since I upgraded to SSMS 19.
I followed the steps and upgraded the apps per this site: Cannot access analysis server via ssms - Microsoft Q&A and that nocked the error down to this
TITLE: Connect to Server
------------------------------Cannot connect to powerbi://api.powerbi.com/v1.0/myorg/SRI Azure Synapse [Prod].
------------------------------
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. See https://aka.ms/msal-net-iwa-troubleshooting for more details. Error Message: An error occurred while sending the request. (Microsoft.AnalysisServices.AdomdClient)
------------------------------
An error occurred while sending the request. (mscorlib)
------------------------------
The remote server returned an error: (401) Unauthorized. (System)
------------------------------
The system cannot contact a domain controller to service the authentication request. Please try again later (System)
------------------------------
BUTTONS:OK
------------------------------But I am still looking for the overall solution to the problem. I feel that this has to be something with SSMS 19 just because all works fine when I use SSMS 18.