Paginated Report connection problems / Analysis Services engine

[ucmaoTWG]

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.

• When i try to connect via basic or oauth 2.0, it says unable to update connection credentials. The authentification type is not supported. Only the authentification type 'Windows' is supported.
• Windows is not an option for when I try to select the authentification methods, only Basic and OAuth 2.0

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

[V-yubandi-msft]

Hi @ucmaoTWG ,

We wanted to follow up on your question. Has your issue been resolved, or are you still experiencing problems?

If everything is working now, it would be helpful if you could share your solution, as it might assist others who encounter the same issue. If we don’t hear back soon, we’ll assume the issue is resolved and close the thread.

Of course, if you need help later, feel free to start a new topic in the Microsoft Fabric Community we’re always here to assist.

Thank you for staying engaged with the community.

[ucmaoTWG · Accepted solution]

The problem has been resolved after 6 months tracing and testing- we had to enable private link in our powerbi tenant in order for users to connect to semantic models in the analysis system. 

[V-yubandi-msft]

Hi @ucmaoTWG ,

Just checking in has your issue been resolved, or are you still facing any challenges. If the solution provided helped, please consider marking it as an accepted solution so it can benefit others in the community as well.

Thanks.

[V-yubandi-msft]

Hi @ucmaoTWG ,

The ICM issue has been resolved. Could you please try again and let us know if you still encounter any problems?

If your issue is resolved, we would appreciate it if you could confirm here, as it may help others in the community facing similar situations.

Thank you.

[V-yubandi-msft]

Hi @ucmaoTWG ,

Thank you for reaching out to the Microsoft Fabric community.

• If a connected service or data source uses Windows Authentication, report access in Power BI will be affected if it gets blocked or disabled. Ensure the service accounts to be used in Windows Authentication aren't blocked or disabled.
• If an option for using Windows Authentication is missing, the version of the gateway is probably obsolete. Update it to the newest version.

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!  

[ucmaoTWG]

• If an option for using Windows Authentication is missing, the version of the gateway is probably obsolete. Update it to the newest version.

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. 

• If a connected service or data source uses Windows Authentication, report access in Power BI will be affected if it gets blocked or disabled. Ensure the service accounts to be used in Windows Authentication aren't blocked or disabled.

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.

[V-yubandi-msft]

Hi @ucmaoTWG ,

Since there is already an ICM in place, I hope it will be resolved as soon as possible based on the severity. I kindly request your patience until the ICM is resolved.

Thank You.

[GilbertQ]

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.

[ucmaoTWG]

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.