Gateway does not connect to web

[FotFly]

Hi there,

I am using a personal mode gateway for my BI reports.

The gateway seemed to be working fine but for the past 3 updates I am encountering some issues. The constant one is that of SQL trusted servers where I manually add the server that cannot connect to the config file and the latest one is the inability to connect to a web source. I use a query to get data from a web page. There is no paywall. In desktop I am able to open the page and get the data but in the service the connection fails. I use Anonymous authentication method and for many years it used to work on my gateway.

Any ideas why this might be happening?

Thanks in advance.

[v-sgandrathi]

Hi @FotFly,

Thank you for reaching out to the Microsoft Fabric Community Forum.

We understand you are using a Personal Mode Gateway to refresh your BI reports and are experiencing issues connecting to a web data source, despite successful connections in Power BI Desktop with Anonymous authentication.

Please be aware that not all web-based queries supported in Power BI Desktop are available in the Power BI Service, particularly when using a Personal Mode Gateway. This is especially true for queries involving functions like Web.Page or HTML table extraction, as these are limited by security restrictions in the online service.

To help address this, please consider the following recommendations:

Review Privacy Level Settings: In Power BI Desktop, navigate to File > Options and Settings > Data Source Settings and ensure the privacy level is set to Public if the source is open. Incorrect privacy settings can prevent connections via the gateway.

Update the Gateway: Confirm that you are using the latest version of the On-Premises Data Gateway (Personal Mode), as older versions may cause compatibility issues.

Web.Page & HTML Table Limitations: If your query uses Web.Page, note that this function is not supported in the service through the gateway. Consider using APIs or retrieving structured data via the raw URL as alternatives.

Consider Enterprise Gateway: Switching to the Standard (Enterprise Mode) Gateway may provide better support for complex data sources and scenarios.


I'm sharing some Microsoft documentation links that I found helpful and will give you a better understanding:
Troubleshoot Power BI gateway (personal mode) - Power BI | Microsoft Learn
Troubleshooting the Power Query Web connector - Power Query | Microsoft Learn
Troubleshoot gateways - Power BI | Microsoft Learn
Test single sign-on (SSO) configuration - Power BI | Microsoft Learn

If you have any questions, please feel free to reach us..... Thank you.

[v-sgandrathi]

Hi @FotFly,

.Just a quick check-in! Has your issue been resolved with the information we shared? We’d be delighted to help further if needed.
Looking forward to your response.

Thank you.

[v-sgandrathi]

Hi @FotFly,

I wanted to check in your situation regarding the issue. Have you resolved it?  Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum!

[v-sgandrathi]

Hi @FotFly,

Just wanted to follow up and confirm that everything has been going well on this. Please let me know if there’s anything from our end.
Please feel free to reach out Microsoft fabric community forum.

[FotFly]

Hi there!

Sorry for taking too long to come back to this.

I tried all the steps you suggested but it did not solve the issue. However, I also tried to skip the test connection for the specific datasource and it turns out that the refresh runs on the service without any issues. Not sure why the test connection was failing but not the refresh.

Thank you for the help.

[v-sgandrathi · Accepted solution]

Hi @FotFly,

Thank you for the update, and no problem, we appreciate your response!

It's notable that the test connection failed but the actual refresh succeeded. This can happen due to temporary DNS or connectivity issues during testing, or because there are differences between test connection validation and actual data refresh, especially when using web connectors with Anonymous authentication.

In these cases, skipping the test connection is an acceptable workaround if you're sure the data source and gateway are set up correctly.

Consider using raw URLs or APIs: If you are currently utilizing Web.Page, it may be beneficial to switch to structured data endpoints such as JSON or CSV APIs.

If the issue continues or you require enhanced control, transitioning to the standard (enterprise) gateway can provide improved support for complex data sources.

Also, please continue to monitor the gateway logs for any runtime errors, particularly if refresh failures reoccur.

Thank you.

[aj1973]

Hi @FotFly 

If the same exact connections from the same dataset used to work and it now fails then try to update the gateway.

[FotFly]

Hi @aj1973,

Thank you for your answer. I have tried updating it multiple times now and the issue persists. From the gateway export log I was not able to figure out what is the issue when trying to connect.

[aj1973]

Yes the message you receive can be incomprehensive. Can I see it tho?

Have you changed anything lately in the dataset? Have you changed connections in the Dataset in your desktop?...