Impersonation error SSAS

[Anonymous]

Hi there, I have strange error having two reports that connects to SSAS database.

User A log in Power BI to see a report and he receives an error: "Couldn't load the schema for the database model" either the user B does not have access to the source database. (He is user A, and error refers to a user B who has no access).

Another error with the same user is tracked on the refresh history of another report connecting to same SSAS mentioning the user B has no access.

There is a connection created on the gateway to the SSAS database.

As a summary User A receives errors from a different user B.
Any idea of what could be happening here?

[v-yulgu-msft]

Hi @Anonymous,

Did you use user B's account as a credential to connect to SSAS database in Desktop and in Gateway? Please verify that if the credential you used currently has access to SSAS DB. There is also an article about troubleshooting the similar error for your reference.

Does User A have a Pro license? If User A wants to view a report shared with him, a Pro license is required, unless the content is in a Premium capacity.

Besides, please refer to this article to map user names under gateway.

Best regards,

Yuliana Gu

[Anonymous]

Hi Yuliana

A separated service account is used on the gateway connection with admin rights on SSAS.

we setup below properties on config file where the gateway service is installed : 

   <setting name="ADUserNameReplacementProperty" serializeAs="String">
    <setting name="ADUserNameLookupProperty" serializeAs="String">

 to avoid using mapping on each SSAS gateway connection.

The user B has no access which is correct, but the strange thing is the error appeared to user A trying to access the report being logged as user A.  And user B never tried to access the report.

User A has Pro-license yes.

[v-yulgu-msft]

Hi @Anonymous,

Which service account did you use in gateway connection and in report data source connection? Per my knowledge, the report execution uses the specified credential in connection string to access data source rather that the account of the report viewer.

Regards,

Yuliana Gu