Forum Discussion
Test Connection Broken
OK, permissions only partly solved the issue. I've now consolidated the issue as:
- Open report management screen, click on data sources, for a report that connects to SSAS (all others are fine) with authentication set to "as the user running the report"
- Click Test Connection, get the error stating "Data source AnalysisServices is not supported."
- Look in Chrome dev tools, the API call to Model.CheckDataSourceConnection returns an error
- Change the connection and enter explicit credentials, click Test Connection with success
- Look in Chrome dev tools, the API call is now going to Model.CheckConnection
- Change the connection back to "as the user running the report", click Test Connection with success
- Look in Chrome dev tools, the API call is still going to Model.CheckConnection
I draw the conclusion that this is an issue with Report Server. Please can someone from MS confirm.
Thanks
I have the same issue.
A Power BI report with 'live connection' to SSAS MD with Kerberos ('As the user viewing the report'). The report is working!
But if I go to 'Manage > Data sources' and test the connection i get "Data source AnalysisServices is not supported. "
Regards Taico
- Anonymous8 years agoNot applicable
Hi Taico,
Thanks for posting your experience. If you change from "As the user viewing the report" to "Using the following credentials", then straight back to "As the user viewing the report" and test the connection, does it work?
Thanks
- ForcaTaico8 years agoResolver II
It does initially.
But if I leave the "Manage > Data sources" and return and test again it goes back to "Data source AnalysisServices is not supported."
Regards Taico
- Anonymous8 years agoNot applicable
For sure - this is exactly the same for me here.
If you monitor the HTTP requests being sent when you Test Connection, you can probably see that a different part of the ReportServer API is being called. The first press calls one method (which fails), when you change the connection type it triggers a different method to be called (which succeeds). If you navigate off the page and back to it, then the failing method is called again.
Hope that someone from MS will pick this thread up and confirm this as a bug.
All the best.