Forum Discussion
Helper IIUnable to render paginated report - Error communicating with Analysis Services
Hey Community,
I have a problem with some paginated reports I delivered to a client. They get the error "Unable to render paginated report. There was an error communicating with Analysis Services. Please verify that the data source is available and your credentials are correct."
The paginated report is connected to a PBI data set connection. This datasource is in the same workspace as the paginated report. I can open the .pbix file, navigate, and refresh, so the credentials to connect to the data are good. The problem comes only when running the paginated report.
I don't understand because on my side, the report runs fine, but on the client's side, it throws the error. What could cause this issue? Is this a permission setting in the workspace?
I read that could be a problem with the Dax query, but if it is, why is it working on my side?
Any clues? Thank you!
Thank you!
Hi mcantos,
The error message “Unable to render paginated report. There was an error communicating with Analysis Services” usually indicates that the report viewer lacks sufficient access to the underlying semantic model, or that other factors such as Row-Level Security (RLS) or DirectQuery timeouts are affecting connectivity.
Please review the following key areas:
Dataset Permissions
Paginated reports that connect to a Power BI semantic model run under the viewer’s identity. The client must have access not only to the paginated report but also to the dataset in the same workspace. Please confirm that the user or their security group has Build (or at least Read/Build) permissions on the dataset. If sharing via an App, ensure that “Allow users to build content with the semantic models in this app” is enabled for the audience.Row-Level Security (RLS)
If RLS is enabled on the dataset, it applies to paginated report queries as well. Verify that the client is correctly assigned to the intended role and is not restricted from seeing data.Query Duration / DirectQuery
If the dataset uses DirectQuery, paginated report queries that exceed the 600-second execution limit will fail with this generic Analysis Services error. Consider simplifying queries, narrowing filters, or using Import mode if possible.Gateway Connectivity
If the dataset relies on an on-premises data gateway, ensure the gateway is online, correctly configured, and that credentials for the underlying source are valid.Why it works for you but not for the client
As the author, you automatically have dataset permissions and may not be restricted by RLS. The client, however, must have explicit Build/Read access and correct RLS mappings.Next Steps
Confirm that the client has Build permissions on the dataset.
If using an App, verify the advanced sharing option mentioned above.
Test access from the client’s perspective using View As roles in Power BI Desktop or by having them connect through Analyze in Excel.
Check RLS assignments and simplify queries if DirectQuery is used.
Validate gateway connectivity if applicable.
Thank you.
5 Replies
v-sgandrathiCommunity Support
Hi mcantos,
The error message “Unable to render paginated report. There was an error communicating with Analysis Services” usually indicates that the report viewer lacks sufficient access to the underlying semantic model, or that other factors such as Row-Level Security (RLS) or DirectQuery timeouts are affecting connectivity.
Please review the following key areas:
Dataset Permissions
Paginated reports that connect to a Power BI semantic model run under the viewer’s identity. The client must have access not only to the paginated report but also to the dataset in the same workspace. Please confirm that the user or their security group has Build (or at least Read/Build) permissions on the dataset. If sharing via an App, ensure that “Allow users to build content with the semantic models in this app” is enabled for the audience.Row-Level Security (RLS)
If RLS is enabled on the dataset, it applies to paginated report queries as well. Verify that the client is correctly assigned to the intended role and is not restricted from seeing data.Query Duration / DirectQuery
If the dataset uses DirectQuery, paginated report queries that exceed the 600-second execution limit will fail with this generic Analysis Services error. Consider simplifying queries, narrowing filters, or using Import mode if possible.Gateway Connectivity
If the dataset relies on an on-premises data gateway, ensure the gateway is online, correctly configured, and that credentials for the underlying source are valid.Why it works for you but not for the client
As the author, you automatically have dataset permissions and may not be restricted by RLS. The client, however, must have explicit Build/Read access and correct RLS mappings.Next Steps
Confirm that the client has Build permissions on the dataset.
If using an App, verify the advanced sharing option mentioned above.
Test access from the client’s perspective using View As roles in Power BI Desktop or by having them connect through Analyze in Excel.
Check RLS assignments and simplify queries if DirectQuery is used.
Validate gateway connectivity if applicable.
Thank you.
- v-sgandrathi
Hi mcantos,
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.
mcantosHi v-sgandrathi ,
Thank you for following up on this. Your information was so helpful in troubleshooting the problem.
In the end, the problem was on the client side. They didn't provide too much information about what the issue was, but my guess is they were not importing the .rdl files properly to the Service.
I asked them to open locally the files and set the Datasource from there, and republish. It worked.
In any case, if I get more information, I'll post it as a reference.
Thank you!
Best,
Marlin
