What causes AdomdConnectionException?

The SSAS instance is down or the Windows service has stopped. The ADOMD.NET client library on the gateway machine is outdated or missing. Kerberos authentication is failing — the service account cannot authenticate against the SSAS instance. Firewall rules are blocking TCP port 2383 (default SSAS port) from the gateway machine. Azure Analysis Services has been paused or the server tier has a connection limit that is exceeded

How do I fix AdomdConnectionException?

Verify the Analysis Services Windows service is running on the SSAS server.. Install the latest version of the ADOMD.NET client library (part of SQL Server Feature Pack) on the gateway machine.. Test connectivity from the gateway to the SSAS server on port 2383 using telnet or Test-NetConnection.. For Kerberos issues, use the Kerberos Configuration Manager and ensure SPNs are registered: MSOLAPSvc/hostname.. For Azure Analysis Services, check the server status in the Azure Portal and verify it is not paused.. Check the Analysis Services error log (typically in %ProgramFiles%\Microsoft SQL Server\MSAS...\OLAP\Log).

High severitydata source

Power BI Refresh Error:
AdomdConnectionException

What does this error mean?

The Analysis Services client library (ADOMD.NET) failed to connect to the Analysis Services or Azure Analysis Services instance. This error occurs with SSAS Tabular or Multidimensional models used as a Power BI source.

Common causes

1The SSAS instance is down or the Windows service has stopped
2The ADOMD.NET client library on the gateway machine is outdated or missing
3Kerberos authentication is failing — the service account cannot authenticate against the SSAS instance
4Firewall rules are blocking TCP port 2383 (default SSAS port) from the gateway machine
5Azure Analysis Services has been paused or the server tier has a connection limit that is exceeded

How to fix it

1Verify the Analysis Services Windows service is running on the SSAS server.
2Install the latest version of the ADOMD.NET client library (part of SQL Server Feature Pack) on the gateway machine.
3Test connectivity from the gateway to the SSAS server on port 2383 using telnet or Test-NetConnection.
4For Kerberos issues, use the Kerberos Configuration Manager and ensure SPNs are registered: MSOLAPSvc/hostname.
5For Azure Analysis Services, check the server status in the Azure Portal and verify it is not paused.
6Check the Analysis Services error log (typically in %ProgramFiles%\Microsoft SQL Server\MSAS...\OLAP\Log).

Frequently asked questions

Does this error affect multiple datasets at once?

If multiple datasets connect to the same data source, yes — all of them will fail until the source connectivity is restored.

Can this error be caused by a server migration or rename?

Yes — if the server name, database name, or connection string changed (e.g., during a cloud migration), Power BI still holds the old connection details. Update the connection in Power BI Desktop and republish.

Does this error appear in Power BI Desktop?

Sometimes — if you open the .pbix file and attempt a refresh, Desktop will surface the same connection error. This is useful for debugging without affecting the Service dataset.

Will the error resolve automatically once the source is back online?

Only if it was a temporary outage. The next scheduled refresh will succeed automatically. If the connection string changed or credentials expired, manual intervention is needed.

Source · learn.microsoft.com/en-us/analysis-services/instances/monitor-analysis-services-with-sql-server-profiler