The on-premises data gateway's service account failed to impersonate the user.

Anonymous · ‎02-14-2020

The Microsoft troubleshooting page doesn't give enough information on how to fix this issue. We have been using the gateway for over a year with an admin account set up in the Gateway and all of the sudden, today it's failing with this error:

The on-premises data gateway's service account failed to impersonate the user.

Does anyone have more information that is NOT in the troubleshooting page on how to remedy this?

Thanks!

Anonymous · ‎02-14-2020

We solved the issue, somehow the environment changed and we had to do this- if this helps others having the same error:

For the delegation settings on the gateway service account,
Check 'Trust this user for delegation to specified services only'
And not 'Use Kerberos only' but 'Use any authentication protocol'

View solution in original post

agarwal137 · ‎01-19-2022

Faced same issue on migrating to a new laptop. The SQL datasources were not connecting on Power BI Service resulting in failed reports refresh. However, files on sharepoint could connect and refresh. The error thrown was -

After 2 days of trying everything, it somehow got solved. Here's how -

- Ensured .NET is installed on system

- Installed Microsoft Access Database engine 2010

- Installed MS ODBC driver 17 for SQL server

- Uninstalled and reinstalled On Premises data Gateway.

- Did a reset of Domain/Laptop Login Password

- Selected the 'existing gateway' for setup (which was being used earlier to run reports in old laptop)

- After setup, logged into Gateway using domain email id.

- Ran couple of reports on Excel connected to the same SQL server databases

- Then Closed everything and did a system shut down.

- Restarted system and found that the datasources were back up on Power BI servcie!

Note that I checked the data source connection status after each step and it wasn't up until the last. So not sure if all are relevant but then here's how it got solved for me.

(have posted this on similar query too. Sorry I couldnt find how to link)

Anonymous · ‎02-14-2020

We solved the issue, somehow the environment changed and we had to do this- if this helps others having the same error:

For the delegation settings on the gateway service account,
Check 'Trust this user for delegation to specified services only'
And not 'Use Kerberos only' but 'Use any authentication protocol'