Showing results for 
Search instead for 
Did you mean: 
New Member

Power BI Gateway - Enterprise - Error generating an asymmetric key


I have tested the Power BI Gateway enterprise in two different enviroments. One works fine (W2008R2, sql + ssas, no DC). The other one is a fresh VM with W 2012 R2, with SQL + ssas and DC on the same machine.


I'm stuck in this screen with this error:


Error generating an asymmetric key.
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.




I have configured the account and computer to have delegation on. The account is Administrator

Any thoughts?


Thanks in advance

Advocate I
Advocate I



Change the logon user for Service "On-premises data gateway service" (PBIEgwService) to "Local System Account"

Frequent Visitor

Thanks eliezer, that did the trick.

Frequent Visitor

Hi, I have the same problem. Could you tell me how can i change the logon user to System Local Account?

Thank you!

Hi, try the following steps.


1. RUN   services.msc

2. Search  "Power BI Gateway - Enterprise Service" in list of services, and click

3. In TAB "Log On" change to "Local System Account"

4. Restart "Power BI Gateway" Service



Thank you!

Hello!  I have downloaded the gateway and went to install it, but because there is no existing gateway and I am getting the error, I have not been able to configure it yet. 

I cannot see power BI Gateway Enterprise service" in the list yet.


Any way to install without configuring?  Thanks in advance!

Frequent Visitor

Thank you!!! You saved my life!!!



Best regards


Frequent Visitor

Hi, I have the same problem. Could you tell me how can I change the logon user to Local System Account? What sgould I do?

Thank you


New Member

The previous version of the gateway, Data Management Gateway, the one that was required to load on premises data into sharepoint 365, also had problems when installed on a domain controller. I won't say it's the same problem, but the symptoms are strikingly similar. Given that installation on a Domain Controller should be fairly rare and I recieved absolutely zero help regarding the problem, I'm guessing microsoft hasn't changed the install, so the problem still exists. The gateway installer creates a user on the local machine to run as, but the local users on a domain controller are domain users and the installer doesn't have enough permissions to create a domain user, so the service fails to start.


You may be sucessful by changing the user the service is running as, or you may run into idiot checks like I did. In the end, our solution was to just not use gateways on domain controllers.


I've attached the last email I sent to Microsoft support in case there's any helpful details, but mostly just to get as much attention as possible for this problem. It's completely avoidable if they changed their installer.


The current status of this the Data Management Gateway doesn't have sufficient permissions
to function properly. I'm 99% sure that is because it was installed on a domain controller.
The service is running as NT Service/DIAHostService, but that user doesn't exist in the
Active directory users and groups. There is a Data Management Gateway Users group, but the
only member of it is me, which must have been added when I installed the DMG because I
didn't add myself to the group. To be clear, the problem is absolutely permissions; the service times out unhelpfully when
running as NT Service/DIAHostService, but runs correctly when running as Local System and
this can be REPRODUCED EVERY TIME. We have moved completely over to the Power BI Pro service, so understanding what the
problem is with the DMG is purely academic. I'm done messing with this since you seem to
be completely incapable of understanding the problem no matter how clearly I state it for
you. Close the ticket. I'll write the summary for you, since most of the time I was rehashing
what was already done: Problem: DMG is installed and running on a local server, all indicators state connections
are good and active, but refreshes, timeout every time. Every part of the convoluted system was scrutinized and analyzed except for the DMG. We
checked that the server was listening, that the datasource was configured properly, that
the Excel document was too big or querying too much data. Finally, we set up a parallel
configuration with another Power BI account and another DMG and that worked correctly.
Since the problem was now clearly the DMG, we changed the registry to log all messages in
the event log and found a tiny WARNING, not an error even though it stopped the DMG from
WORKING, a warning that stated insufficient permissions. Changing the service to run as
Local System allows the DMG to work as expected even though it complains about not being
configured correctly. This lack of proper permissions can only be because the DMG is
installed on a Domain Controller. User requested assistance in configuring the
DIAHostService account with the appropriate permissions for running the DMG on a Domain
Controller, but none was provided. Resolution: Install DMG on a server that is not a Domain Controller or ditch the whole
convoluted system and switch to the Power BI Pro service which supports connecting
directly to Azure Tables the way it should have been done in the first place.


Thank you extragoode! 

Helpful resources

Power BI December 2021 Update_carousel 768x460.jpg

Check it Out!

Click here to read more about the December 2021 Updates!

User Group Leader Meeting January 768x460.png

Calling all User Group Leaders!

Don't miss the User Group Leader meetings on January, 24th & 25th, 2022.

Jan 2022 Dev Camp 768x460 copy.png

Power BI Dev Camp- January 27th, 2022

Mark your calendars and join us for our next Power BI Dev Camp!

Top Solution Authors