Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hello,
I have a Paginated Report that had been working for 1+ years without an issue until now.
1) It is connected to PowerBI as a datasource.
2) The connection string from powerbi to our azure cloud is working- meaning, i can query within the report builder and render results, but when I republish to the service, it is no longer working.
3) Looking into our gateway and connections, it looks like any item under 'analysis services' with an example connection name of something like pbiazure://api.powerbi.com/'sobe_wowvirtualserver etc. with a connection ID is no longer enabled.
My question is this- is there some sort of overall networking setting or firewall that our network administrators could have put up to disable all windows authentifications within azure that would then affect powerbi as well?
This is the error message i am receiving. This is the same error for every single paginated report so i'm assuming something changed in the underlying.
An unexpected error occurred
There was an error contacting an underlying data source. Manage your credentials or gateway settings on the management page. Please verify that the data source is available, your credentials are correct and that your gateway settings are valid.
Timestamp: 2025-01-10T19:51:59.574Z
Root activity ID: e762db15-a6d9-b91a-12d3-eac8473fe124
Cluster: https://wabi-us-east2-b-primary-redirect.analysis.windows.net/
Capacity ID: undefined
ReportViewerVersion: 2024.11.3.1699
Hi @ucmaoTWG ,
Thank you for reaching out to the Microsoft Fabric community.
If my answer addressed your query, kindly mark it as the Accepted Solution to assist others.
I'd also be grateful for a 'Kudos' if you found my response useful!
We use a cloud based microsoft azure sql server with no on-prem gateway. The problem we're having is connecting to the semantic model, so there isn't even a gateway involved.
This doesn't matter at all, because its not a powerbi report that we're having issues with, it's the connector between the semantic model and the paginated report. The powerbi reports are fine. The paginated reports built off the semantic models are not.
Hi @ucmaoTWG
If your data source is using a semantic model in the power BI service, what you could do is instead of going through the gateway, you could connect to this data source directly by changing the settings in your paginated report. Once the paginated report is published, if you go into settings, you should be able to then configure it to connect to the semantic model directly within the power bi service without having to go through the gateway.
I am already connecting to the semantic model. Everything is cloud based, there is no on prem gateway to configure. There is still a connection string that is generated for analysis services every time I publish a report using the 'Add Power BI Dataset Connection' option within the report builder.
When i bring up the settings, I only get the option to change the report/name and to endorse the report. When i select 'Manage', it brings up the data source credentials but that only has the data sources that I used within the powerbi report builder, so I don't see any options to change the settings either.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
21 | |
16 | |
12 | |
10 | |
8 |
User | Count |
---|---|
34 | |
26 | |
19 | |
17 | |
16 |