March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
Register NowGet certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
Hi,
Over the last few days i have been having some issues with the on-premise gateway connection going offline and requirng to be restarted, this issue has now been resolved and with a server restart and updating to the latest version of the gateway.
I have now encountered another issue with the data sources, the gateway is shown as online but the datasource linking to our reports which all have schduled refreshes have all broken and went offline. The inital error i got from the schduled refresh was
"Before the data import for "X" finished, its data source timed out. Double-check whether that data source can process import queries, and if it can, try again."
I have then been into the data source section with the PowerBI service and tried to update the credentials for each of the data source and get the following error:
Other than updating the gateway there has been no other changes to the reports.
Would anyone be able to assist in helping me understand what could be causing this issue?
Solved! Go to Solution.
Hi,
Thanks for your reply.
Im not sure if i have found the solution but after creating addtional space on the server (i noticed that there was limted free space), the data sources are no longer timing out and seem to be refreshing fine.
Hi. Let me check if got this right. You have a PBI dataset connected to an Azure SQL Database and other sources that require a gateway, because if you are just using Azure SQL Database you don't need a gateway.
In order to make cloud and onpremises sources work properly, you need to enable an option on the gateway
That's a start. Then regarding the message of the issue it says there is a timeout. It's not offline. The timeout can be for two reasons. One, the query is taking more than the command timeout specified by the Power Query code on the source step. If not specified it's between 10 or 15 minutes. Two, there is another timeout that can be configured at SQL Servers regarding how much time a query can take. That last might be more difficult to find, I would suggest talking with a DBA if all the things I have said before are ok.
I hope that helps,
Happy to help!
Hi,
Thanks for your reply.
Im not sure if i have found the solution but after creating addtional space on the server (i noticed that there was limted free space), the data sources are no longer timing out and seem to be refreshing fine.
Well if the memory of the server is busy almost everyday or the disk is out of space it can response a timeout because it needs some memory to use from the server and sometimes it creates a copy of the pbix while refreshing on the disk as temporal file. If it can do it, then fails.
I hope you solution keeps working! just remember to monitor the space on the server
Happy to help!
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
Check out the November 2024 Power BI update to learn about new features.