What causes DM_GWPipeline_UnknownError?

SAML signing certificate is not loaded or accessible to the gateway service account. CryptographicException during SSO token generation (signing key not loaded). Gateway service account lacks permissions on the certificate private key. A gateway component crashed and the root cause is in a nested InnerType field. Kerberos or SAML SSO misconfiguration on the gateway server

How do I fix DM_GWPipeline_UnknownError?

Inspect the full gateway log — the InnerType and InnerMessage fields contain the actual error.. If InnerType=CryptographicException, verify the SAML or Kerberos certificate is installed in the correct certificate store.. Grant the gateway service account read access to the private key of the signing certificate.. For SAML SSO: re-run the gateway configuration wizard and re-upload the certificate.

High severitygateway

Power BI Refresh Error:
DM_GWPipeline_UnknownError

What does this error mean?

The on-premises gateway encountered an internal error. Usually wraps a CryptographicException when the SAML signing certificate private key is inaccessible.

Common causes

1SAML signing certificate is not loaded or accessible to the gateway service account
2CryptographicException during SSO token generation (signing key not loaded)
3Gateway service account lacks permissions on the certificate private key
4A gateway component crashed and the root cause is in a nested InnerType field
5Kerberos or SAML SSO misconfiguration on the gateway server

How to fix it

1Inspect the full gateway log — the InnerType and InnerMessage fields contain the actual error.
2If InnerType=CryptographicException, verify the SAML or Kerberos certificate is installed in the correct certificate store.
3Grant the gateway service account read access to the private key of the signing certificate.
4For SAML SSO: re-run the gateway configuration wizard and re-upload the certificate.

Beyond the docs

Common practitioner solutions not covered in the official documentation.

1Restart the gateway service after any certificate change: net stop PBIEgwService && net start PBIEgwService

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-sso-saml