Forum Discussion
DirectQuery Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Ahh, I forgot something. You can workarround this problem if you set an user name and password on the report datasource, instead of the default Windows Authentication.
Tnx, but only Windows authentification is acceptable for my case
- tragonneau8 years agoFrequent Visitor
Hello, I have the same error when I use Chrome.
It works when I use IE.
I tried to import settings from IE but I still have the same error.
- ganga-2016-MSFT8 years agoMicrosoft Employee
It's typical Kerberos issue. AUTHORITY\ANONYMOUS LOGON. Can you just use the sql login while connecting to data source or you should enable Kerberos in order to cover double-hop scenario.Adam made a nice video which explains Kerberos configuration - https://guyinacube.com/2017/02/configure-kerberos-power-bi-reports-reporting-services/
- Anonymous7 years agoNot applicable
That guide only explains how to set up Kerberos with SSAS as a datasrouce, rather than an SQL Server.
Has anyone managed to resolve their Kerberos double hop issue? We're still getting the error that than original poster specified.
Our setup:
Report Server: RS1 running under a domain account DOMAIN\RSService
Database Server holding the data for the Report Server reports: DB1 running SQL Server under a domain account DOMAIN\DBService
SPNs set for RS1:
- http/RS1 DOMAIN\RSService
- http/RS1.domain.com DOMAIN\RSService
SPNs set for DB1:
- MSSQLSvc/DB1 DOMAIN\DBService
- MSSQLSvc/DB1.domain.com DOMAIN\DBService
- MSSQLSvc/DB1:1433 DOMAIN\DBService
- MSSQLSvc/DB1.domain.com:1433 DOMAIN\DBService
Constrained delegation has been set up on RS1, and it allows authentication to DB1 for the above SPNs.
ReportServer config has also got <RSWindowsNegotiate/> set as a <AuthenticationType>.
We manage to query the reports successfully via DirectQuery in Google Chrome, not as much success using Internet Explorer (v11).