MetricSign
Request Access
Errors

Why do Power BI refreshes fail after installing or updating the data gateway?

Gateway installations and updates are a common source of Power BI refresh failures because the new gateway instance isn't automatically trusted and all existing configurations need to be verified or re-applied.

New gateway installation failures

When a new gateway is installed on a different machine (or alongside an existing gateway as a cluster node), Power BI datasets must be reassigned to use the new gateway. Until this reassignment happens, refreshes continue trying to use the old gateway — which may no longer be accessible if the machine was decommissioned.

Common errors after a new installation: - DM.GWPipeline.Gateway.GatewayNotFound: Datasets are still pointing at a gateway that no longer exists or is offline - DM.GWPipeline.Gateway.CertificateNotTrusted: The new gateway's TLS certificate isn't trusted by the gateway infrastructure

Gateway update failures

Gateway updates sometimes require a service restart. During the restart window, any scheduled refreshes that run fail with gateway unreachable errors. This is expected and temporary — but if the gateway service fails to restart correctly (due to a permissions issue or a failed update), refreshes continue failing.

Check the Windows Services console on the gateway machine after an update to confirm the service is running.

Credential re-validation after update

Some gateway updates reset stored credential associations. After the update, credentials appear present in the gateway's data source configuration but fail validation because the internal encryption has changed. Entering the credential again (even with the same values) forces re-encryption and resolves the issue.

Gateway cluster reassignment for existing datasets

If the new gateway is intended to replace an old one, all datasets that used the old gateway must be manually reassigned to the new gateway cluster in the dataset settings. Power BI provides no automatic migration of gateway assignments when a gateway is replaced.

Post-update verification checklist

  1. Confirm the gateway service is running in Windows Services
  2. Confirm the gateway shows as Online in Power BI Manage gateways
  3. Test connectivity for each registered data source (right-click → Test connection)
  4. Re-enter credentials for any data sources showing a warning
  5. Trigger a manual refresh on a test dataset before relying on scheduled refreshes

Related questions

Related error codes

Related integrations

Related articles

← All questions