Forum Discussion
Power Bi Gateway - Errors
Hi Team,
We have installed On Premise Data Gateway software, which is used to use the data source from Microsoft SQL Server and publish the information in Power Bi Service.
It was working till yesterday, and we are now getting a new error message while refreshing the data.
Unable to connect to the Data source, unidentified.
Underlyning Error message as listed below.
Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Can you pelase help us what went wrong
Regards
Srini
4 Replies
- FowmySuper User
srinival
Can you check this blog, hope it will help you resolve your problem if it is a similar issue:
https://community.powerbi.com/t5/Service/Power-Bi-Service-Refresh-timeout-expiration-issue/td-p/164836________________________
If my answer was helpful, please consider Accept it as the solution to help the other members find it
Click on the Thumbs-Up icon if you like this reply 🙂
- Greg_DecklerCommunity Champion
srinival - That could be anything. I would check out Fowmy 's link but this could be network related, DNS issue, server could be turned off. Very vague. If all else fails, You could check the Issues forum here:
https://community.powerbi.com/t5/Issues/idb-p/Issues
And if it is not there, then you could post it.
If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET". - Nimai123Post Patron
Hello srinival
I have faced this same issue a few months back.
You can try doing this hope it helps!
- Increase the time of the Query in Advanced Editor.
- Update the Gateway.
- Re-configure the Gateway.
- Do not run many refreshes at the same time because then the load increases on the SQL server.
- Raise a support ticket which is free if you are a PRO user, they will help you to get the logs and help you to understand the source of error so that we can work on the right direction.
2 point was my solution.
As per my experience, your SQL is taking time to respond due to the 4 point, do check if possible SQL error logs.
If you like my solution give it a Kudos!
And if it solves your problem accept it as a solution.
Regards,