Power BI on-premise Gateway

This could also be a domain issue with the username. When you use the Analysis Services data source, the email address used to log in to Power BI will be passed to Analysis Services through the gateway as a valid user.

So, the email must match a defined user principal name (UPN) within the local Active Directory domain.

You need to add your user account to the server role in your SSMS Analysis Server --> properties> security, and then restart the gateway to refresh the data set.

Update the gateway to the latest version

Please mark this post as solution if it helps you. Appreciate Kudos.

Hi Paul_Benedict19 ,

Are you able to connect from SSMS?

If yes, try to install older version of gateway and try to create connection and test it.https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-monthly-updates

I hope it helps.

Thanks,

Sai Teja 

Hi Paul_Benedict19 ,
This error typically indicates that the on-premises data gateway is having trouble impersonating the specified user account (AD\AD08PLC) during authentication, which is required to establish a secure connection to your on-premises data source. 

Even though you're using the same credentials as an existing, functioning gateway, the issue may be related to how the new gateway's service account is configured or lacks the necessary permissions to delegate or impersonate users in your Active Directory environment. It’s worth double-checking that the gateway service is running under the correct Windows account, and that this account has the appropriate rights (including "Log on as a service" and impersonation permissions). Also, ensure that the data source credentials configured in Power BI Service are correct and match what's expected by the data source. 

If Kerberos is in use, SPNs (Service Principal Names) and delegation settings could also be a factor. Reviewing those settings and restarting the gateway service after any changes can often resolve the issue. If all configurations look correct and the error persists, contacting Microsoft Support with the session and request IDs may be necessary for deeper investigation.