Forum Discussion
Gateway problems?
Hi all,
All of our semantic models that have been refreshing after 09:34 today have failed to load.
They are all failing with the same error disregarding source type:
DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError
We are still able to update the reports successfully in Power BI Desktop without any issues.
The Gateway server is up and running, and we have not identified any issues with the server itself.
My current thoughts on what could be causing the errors are:
Gateway version: The current version is quite old (300.294.7).
Firewall/network issues: Some maintenance was performed on the server yesterday. However, the refreshes were working normally earlier this morning, so it is unclear whether this is related.
Any ideas or suggestions on what we should check next would be greatly appreciated.
Best regards,
ok we solved issue by restarting the Gateway server.
Gateway looked like it was on in services but powershell said something else.
5 Replies
- tayloramy
Super User
Hi Doink, has there been any network changes recently?
In the gateway software, can you run a network port test and see if all tests are successful or if a port has become blocked?
Can you also double check the credentials for the connections that are timing out? If they use SSO credentials and the user changed their password or left the org, the connections will break.
- Murtaza_Ghafoor
Super User
This looks more like a gateway/network issue than a semantic model related issue, especially since multiple models started failing at the same time.
I would recommend checking:
- Gateway Network Port Test for any blocked ports.
- Gateway logs around 09:34.
- Any firewall/network changes made during yesterday’s maintenance.
- Data-source credentials and connectivity from the gateway server.
- Consider upgrading the old gateway version (300.294.7).
- At last check the gateway credentials.
Since Power BI Desktop refreshes are working, I’d prioritize checking the gateway and network path first.
If this helps, ✓ Mark as Kudos | Help Other - v-aatheeque
Community Support
Hi Doink
Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further.
- DoinkRegular Visitor
ok we solved issue by restarting the Gateway server.
Gateway looked like it was on in services but powershell said something else.