Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
Hi,
I am dealing with the following problem with 3 of the reports I run (out of +-90):
We are using an on-prem SQL server and this (and the other two problem giving reports) have an excel file stored on sharepoint connected, through a cloud connection; all are online ->
What would be possible avenues to look into? We can run the refresh in Desktop manually.
Connection errors doesn't seem the case, Gateway error seems unlikely as well as firewall problems; all is online and other reports with same set-up are running fine
Solved! Go to Solution.
Hi @FODK
It usually happens when you're combining an on-prem SQL Server with something like a SharePoint Online Excel file. Power BI Gateway struggles with that mix (called a hybrid data source).
Here are some steps :
Make sure your SharePoint connection is using OAuth2, not Windows or Anonymous.
If possible, avoid combining cloud + on-prem data sources in the same report the gateway often can't handle it well.
If moving the SQL data to Azure SQL is an option, that usually resolves the issue.
Alternatively, using Power BI Dataflows to prep one of the sources separately might help too.
Since it works in Desktop but fails on Service, it's almost certainly a gateway-related problem not firewall or credentials.
Hi @FODK
It usually happens when you're combining an on-prem SQL Server with something like a SharePoint Online Excel file. Power BI Gateway struggles with that mix (called a hybrid data source).
Here are some steps :
Make sure your SharePoint connection is using OAuth2, not Windows or Anonymous.
If possible, avoid combining cloud + on-prem data sources in the same report the gateway often can't handle it well.
If moving the SQL data to Azure SQL is an option, that usually resolves the issue.
Alternatively, using Power BI Dataflows to prep one of the sources separately might help too.
Since it works in Desktop but fails on Service, it's almost certainly a gateway-related problem not firewall or credentials.