Forum Discussion
Helper IError Communicating with Analysis Services - Failed to create the MSOLAP command.
Helper IThank you Carson, We have tested a few things based off of what you provided and have ruled out a few issues.
Based on what you said, we have set up a new connection string, based off of OAuth2.0 credentials and verified that it can connect, pull, and publish semantic models that can be connected to by users through powerbi.
The semantic model connects to an Azure SQL Server with Azure Active Directory - Universal with MFA authentication utilizing our EntraID.
When testing reports with this connection string, we return results within PowerBI Service, and powerbi desktop, so the OAuth connection to both is correct.
When we tested the creation of a paginated report, we're still getting the MSOLAP error even with the federated OAUTH2.0 connection through the connection string, and semantic model.
my question is now- Is it possible that the analysis engine behind paginated reports is reading my on-premises active directory account credentials instead of the EntraID credentials?
You also mentioned this earlier-
The root cause of this is that the semantic model you are using is stored in Power BI Service and you can only access this semantic model by logging in through your Power BI Service account and not through your windows account (this is by design).
We have never utilized service accounts, only regular login accounts. I have also tested trying to connect to the semantic model through powerbi desktop and i'm getting an error as well in that instance- mimicing the steps you took above
I assume these two issues are both connected- do you have any insight into how the connection to a semantic model works for powerbi desktop? Could it have anything to do with my local AD connections not being linked to my Entra ID?
Hi,ucmaoTWG .Thank you for your reply.
Your understanding is correct, for paging reports, I think the system prefers to look for local geographic accounts as data source credentials.
According to the documentation for data sources supported by Power BI Pagination Reports, the system also requires users to configure the local Active Directory (AD) to integrate and map with Microsoft Entra ID (formerly known as Azure Active Directory) when using an Azure SQL database as a data source
URL:
Configure Microsoft Entra authentication - Azure SQL Database & SQL Managed Instance & Azure Synapse Analytics | Microsoft Learn
Supported data sources for Power BI paginated reports - Power BI | Microsoft Learn
For the service account I mentioned, it is in fact the account you use to log into Power BI Service (typically a Microsoft 365 account)
I suggest you read the above document carefully, I think it may help solve your problem. Pagination reports are generally more restrictive than PBIX reports
Going back to your error screenshot, I think this error may be caused by the fact that the semantic model you are connecting to has actually been modified in Power BI Service (maybe the storage location has been changed, or maybe the name information has been changed), so that Desktop can't find the corresponding model.
I recommend that you re-edit the pbix report corresponding to the semantic model you want to connect to in desktop, republish it to Power BI Service (set up the data source credentials and gateway connection), and then connect to the semantic model of the pbix report through Power BI Desktop. model through Power BI Desktop and check if the problem can be solved.
And maybe you can change the connection.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.