Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

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.

Power BI and SQL 2019 possible kerberos issue

I have a report in Power BI Report Server (May 2020) that is configured with kerberos to use the identity of the current user against the database.   Database is connected to using direct query method.   SQL 2019 database and PBI May 2020 are on different servers.  Kerberos trust was enabled for the databse server for both SQL Server and OLAP services.   service account HTTP service was registered as well.  kerberos setup works but fails intermittently with one of two errors:

 

error 1:   We couldn't connect to the Analysis Services Server.  Make sure you've entered the connection string correctly

error 2:  Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.. The exception was raised by the IDbConnection interface.
Please try again later or contact support. If you contact support, please provide these details.

Request IDb0cbf72a-caca-4e90-f785-6c4da8e2c01d

 

Sequence

1.User 1 logins into power bi report server.  Opens a report and renders correctly using direct query and displays content.  kerberos trust works and user is authorized against the databse and content returned and rendered in the report. 

2. User 2 has database login access but no database object read permission gets error #1.  Since they don't have database object access.  

3.User 3 has no database login access.  Gets error #1.  

4.Randomly then error 1 starts appearing for people with database access and those without.

Is this a kerberos caching issue on the domain controller or the power bi report server or something else?

Status: New
Comments
v-lili6-msft
Community Support

hi @rfremmer 

If the SPNs from the service account were set incorrectly, and please have a look this document.

 

Regards,

Lin

rfremmer
Regular Visitor

Thanks Lin this document is the one of the ones we followed to setup the kerberos.  The errors occur intermittently normally no kerberos errors but those errors pop up from time to time for no apparent reason.