What causes Failed to create a gateway. Try again?

The machine running the gateway installer cannot reach the Power BI service endpoints. A previous failed gateway installation left behind registry entries or service stubs. The user account performing the installation lacks local administrator rights. The gateway port (443 or 5671) is blocked by a firewall or proxy. An existing gateway with the same name is already registered in the tenant

How do I fix Failed to create a gateway. Try again?

The official documentation does not provide explicit fix steps for this error. See additional troubleshooting below.

High severitygateway

Power BI Refresh Error:
Failed to create a gateway. Try again

What does this error mean?

The Power BI service could not register a new on-premises data gateway. This appears in the gateway installer or the Power BI portal during gateway setup.

Common causes

1The machine running the gateway installer cannot reach the Power BI service endpoints
2A previous failed gateway installation left behind registry entries or service stubs
3The user account performing the installation lacks local administrator rights
4The gateway port (443 or 5671) is blocked by a firewall or proxy
5An existing gateway with the same name is already registered in the tenant

Beyond the docs

The official documentation does not cover this error — these are community-tested approaches.

1Run the gateway installer as Administrator
2Check outbound connectivity to *.servicebus.windows.net on port 5671 and *.powerbi.com on 443
3Open Services.msc and ensure no stale 'On-premises data gateway' service entry exists — remove it and retry
4Delete any leftover gateway registration files in %localappdata%\Microsoft\On-premises data gateway
5Retry the installation from the Power BI portal (Settings → Manage gateways → Add) rather than the standalone installer

Frequently asked questions

Does this error affect all datasets using the same gateway?

Yes — all datasets routed through the affected gateway will fail simultaneously. Resolving the gateway configuration or credential issue restores all of them at once.

Does this error appear in Power BI Desktop?

No — Power BI Desktop connects directly to data sources. Gateway errors only occur when Power BI Service initiates a scheduled or manual refresh.

Can this error resolve itself without intervention?

No — gateway errors require manual action: re-entering credentials, restarting the gateway service, or correcting the network path between the gateway and the data source.

How long does it typically take to fix?

A simple credential refresh takes 5–10 minutes. Network or firewall issues can take 30–120 minutes depending on your infrastructure access.

Source · learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem-tshoot