Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi all,
I have created a solution on my on-premise server, where both Power BI Desktop is running and also SQL Server Analysis Services (tabular mode). On that server, we installed the on-premise gateway, which is online and ready to be used:
We have pubished the report to the Power BI App, and both the datasource and the reports are visible. But it's just the structure, so there is no data and we can''t see the tables as well. So actually, we can't see the datamodel. When we open a report, we get this error message: this report can't access the datasource. Please contact the author of the report to solve the issue (it's in Dutch in the screenshot, so translated):
So it looks like it can't access the data, but the gateway is running and also in Power BI App the gateway configuration seems to be configured right:
So it looks like the gateways are online, the project is publlished, but it just can't access the data.
The user who published the report from the Power BI Desktop App is of course a Office 365 user. It's the same user we try to access the report/datamodel in Power BI App. And even when I configure the Analyses Services server with access 'everyone' it's not working.
Does anyone have any clue on how to solve this issue?
Many thanks in advance.
Best regards, Mike
Solved! Go to Solution.
Hi @mvink ,
According to the description of the error, I think you should check your UPN (User Principal Name) settings.
Power BI allows for mapping user names for Analysis Services data sources. You can configure rules to map a user name signed in with Power BI to a name that's passed for EffectiveUserName on the Analysis Services connection.
The email address must match a defined user principal name (UPN) within the local Active Directory domain. The UPN is a property of an Active Directory account. The Windows account must be present in an Analysis Services role. If a match can't be found in Active Directory, the sign-in isn't successful.
Reference: Manage your data source - Analysis Services - Power BI | Microsoft Docs
Best Regards,
Community Support Team _ kalyj
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @mvink ,
According to the description of the error, I think you should check your UPN (User Principal Name) settings.
Power BI allows for mapping user names for Analysis Services data sources. You can configure rules to map a user name signed in with Power BI to a name that's passed for EffectiveUserName on the Analysis Services connection.
The email address must match a defined user principal name (UPN) within the local Active Directory domain. The UPN is a property of an Active Directory account. The Windows account must be present in an Analysis Services role. If a match can't be found in Active Directory, the sign-in isn't successful.
Reference: Manage your data source - Analysis Services - Power BI | Microsoft Docs
Best Regards,
Community Support Team _ kalyj
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Extra information, this is what I can find in the gateway log file:
InnerMessage=<pi>The following system error occurred: The name provided is not a properly formed account name. </pi>
InnerToString=<pi>Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: The following system error occurred: The name provided is not a properly formed account name.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.