Power BI Gateway Installation issues

Hi DaleJohnson I have a similar issue when upgrading the Gateway. Everything is fine until it needs to start the service and then it rollsback and doesn't upgrade.

As a workaround, I manually start the service (when the progress bar is around 90%). To start the service, open the service properties, go to the Log On tab, remove the password for the NT SERVICE\PBIEgwService account, and click OK three times. Then, start the service manually.

Hello DaleJohnson ,

Do you have more information in Event Viewer under Windows Logs → Application for more detailed error message

Vivien 

Hi DaleJohnson,

The on-premises data gateway is a machine-wide Windows service, not per-user, so RDS user profiles/UPDs shouldn’t be involved. Use the Standard (enterprise) gateway installer and run it as an administrator. See Microsoft’s install guide: Install an on-premises data gateway.

Verify the service account has “Log on as a service”. By default the service runs as the virtual account NT SERVICE\PBIEgwService. Confirm Group Policy isn’t stripping this right on RDS hosts:

• Open secpol.msc > Local Policies > User Rights Assignment > Log on as a service and ensure NT SERVICE\PBIEgwService is present.
• If your domain GPO overwrites local settings, add it (or switch to a gMSA/domain account) centrally. Docs: Change the on-premises data gateway service account.
  Tip: If you do change accounts, do it in the Gateway app, not just services.msc, so permissions are applied correctly.

Start the service and check Event Viewer.

• Start: services.msc > On-premises data gateway service (PBIEgwService).
• Event logs: Event Viewer > Applications and Services Logs > On-premises data gateway service for precise startup errors. Microsoft’s troubleshooting article shows where to look and how to export logs: Troubleshoot the on-premises data gateway.

Best practice (optional but recommended): Consider hosting the gateway on a dedicated utility VM instead of an RDS session host to avoid contention and GPO/profile hardening side-effects. Background and guidance: RADACAD gateway overview and Using the gateway with Fabric.

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

Hi DaleJohnson ,

Thanks for reaching out to the Microsoft fabric community forum. Also thank you tayloramy  and vivien57  for your helpful response.

Since the gateway installs correctly on a clean Server 2022 RDS host with the same settings, it looks like the problem is specific to the production server’s environment, rather than being caused by permissions or the installer itself.

The PBIEgwService startup failure typically points to a system-level conflict, such as a corrupted service profile, leftover registry entries, or interference from a local security or endpoint agent that blocks the gateway from initializing its necessary components. Since you have already tried all the troubleshooting steps, it would be best to open a support case with Microsoft so their engineering team can perform a more detailed trace on the affected host.

You can open a support ticket using the following link:

Power BI and Fabric support overview - Power BI | Microsoft Learn

Hope this helps. Please feel free to rech out for any further questions.

Thank you .

Hi DaleJohnson ,

Could you please confirm if the issue has been resolved or raised support ticket with Microsoft? If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community.

Please feel free to contact us if you have any further questions.

Also thank you Wikkleyn_81  for your helpful response.

Thank you.

Hi DaleJohnson ,

We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.

Thank you.

I am faced with the same error 1920 on an AWS EC2 instance where the gateway service fails to start at the end of installation and the installation rolls back completely. I have traced the issue to our network security policy which enforces a role-based domain level security group for logging on as a service (thus requiring a domain account to run as a service) while simultaneously locking the local security policy so that it can't be modified on the machine, even temporarily. Because the install fails and rolls back its changes, there is no way to modify the login account for the service after installation. The service is uninstalled and there is no GUI without the installation.

SOLVED - Error 1920 / PBIEgwService fails to start

I was unable to update/install the On-premises data gateway on Windows Server 2022.

The installation always failed with:

Error 1920. Service 'On-premises data gateway service' (PBIEgwService) failed to start. Verify that you have sufficient privileges to start system services.

I also received Windows Service Error 1064 when trying to start PBIEgwService manually.

In my case, this was not a permissions, .NET, WMI, Windows Update, or service account issue.

The actual cause was a port conflict with On-premises data gateway (personal mode).

I checked the gateway logs here:

C:\Windows\ServiceProfiles\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway\GatewayErrors*.log

The log showed:

System.ServiceModel.AddressAlreadyInUseException

and:

System.Net.Sockets.SocketException (10048)

The standard gateway was trying to listen on:

127.0.0.1:45376

but that port was already in use.

I checked the port with PowerShell:

Get-NetTCPConnection -LocalPort 45376 -State Listen

Then I identified the process using the returned PID:

Get-CimInstance Win32_Process -Filter "ProcessId = <PID>" | Select ProcessId, ParentProcessId, Name, ExecutablePath, CommandLine

The process using port 45376 was:

Microsoft.PowerBI.DataMovement.PersonalGateway.exe

from:

C:\Users<user>\AppData\Local\Microsoft\On-premises data gateway (personal mode)\

Solution:

Stop the Personal Gateway process.

Confirm that nothing is listening on port 45376 anymore.

Start PBIEgwService again.

After stopping the Personal Gateway process, the standard On-premises data gateway service started successfully and showed Running in Services.

So if you are getting Error 1920 and already have or previously had Personal Mode installed, check the GatewayErrors log for AddressAlreadyInUseException and check whether port 45376 is already in use before spending time troubleshooting permissions.

In my case, the Personal Gateway and the standard On-premises data gateway were conflicting over the same localhost port.