Connectivity
Login timeout expired
Power BI dataset refresh error: what it means and how to fix it.
What this means
The SQL connection could not be established in time (network unreachable, firewall, or a slow server).
How to fix it
- Confirm the server is reachable and port 1433 is open.
- Verify the instance name and the SQL Browser service.
- Raise the connection timeout.
Frequently asked questions
- What does the "Login timeout expired" error mean?
- The SQL connection could not be established in time (network unreachable, firewall, or a slow server).
- How do I fix it?
- Confirm the server is reachable and port 1433 is open. Verify the instance name and the SQL Browser service. Raise the connection timeout.
- Where does this Power BI refresh error appear?
- It appears in a Power BI semantic model's refresh history when a scheduled or on-demand refresh fails.
Related connectivity errors
- DM_GWPipeline_Gateway_DataSourceAccessError
- DM_GWPipeline_Gateway_MashupDataAccessError
- The server was not found or was not accessible (SQL error 40)
- Connection denied: Deny Public Network Access (Azure SQL)
- The certificate chain was issued by an authority that is not trusted
- The server name doesn't match the SQL Server SSL certificate
Catch this automatically
RefreshRadar monitors every Power BI dataset refresh and emails you when one fails, with the likely cause and the fix, so you are not hearing about a broken refresh from your stakeholders first.