Forum Discussion
Issue: Paginated Report Loses Semantic Model Connection After Refresh
Hi everyone,
I’m experiencing an issue with a Paginated Report.
Twice this week, I found that the Paginated Report could no longer access the Semantic Model in the morning when I started work.
Initially, I thought the issue might be related to a Semantic Model refresh. However, I’m not sure that is actually the cause.
The first time this happened, I don’t believe I had updated or refreshed the Semantic Model before the Paginated Report became inaccessible.
The only thing I can confirm is that the Semantic Model itself had not been updated or changed.
Has anyone experienced a similar issue where a Paginated Report suddenly loses its connection/access to the Semantic Model, even though the Semantic Model has not been changed?
Any suggestions on what could cause this or where I should check would be greatly appreciated.
Thank you!
8 Replies
Update:
Since I’m temporarily unable to submit a support ticket, I’ll continue to document what I find here.
I tried editing the data source in the Paginated Report and uploading it again. The last time I experienced this issue, this brought the report back. However, this time it did not fix the problem. All of my Paginated Reports were still unable to access their Semantic Models.
I then created a new Paginated Report using the same Semantic Model. The new report worked normally, whether or not I added parameters.
Then something interesting happened: about 10 minutes later, the original Paginated Report that used the same Semantic Model as the new report became accessible again. However, my other Paginated Reports connected to different Semantic Models were still inaccessible.
At this point, I’m pretty sure this is not something I can fix on my end.
I’ll continue to document any additional findings here until I’m able to get help from Microsoft.
Another update:
I tested one more Semantic Model by creating a new Paginated Report using it. And then something even stranger happened — my other Paginated Reports started working again.
At this point, it seems that creating a new Paginated Report somehow triggers the existing Paginated Reports to recover their access to the Semantic Models.
So, based on what I’ve observed so far, the new “process” would apparently be:
Refresh the Semantic Model → create a new Paginated Report → delete the new Paginated Report because it’s not actually needed.
Obviously, this is not a practical solution. 😅
v-abhinavmuCommunity Support
Hi YL_TCI,
Thank you for sharing the detailed findings.A few checks from the Microsoft documentation that may help troubleshoot this behavior:
• Check Semantic Model permissions: Paginated Reports that use Power BI Semantic Models require Read permission on the underlying Semantic Model. This is also required when the report and Semantic Model are in different workspaces.
• Check the data-source configuration: Verify that the Paginated Report is configured with the expected data source and that the connection and credentials are configured correctly. The embedded data-source guidance also recommends using Test Connection to verify that the data source is available and the specified credentials are correct.
• Check the error message: Microsoft documents specific session and connection errors, including "Your session has expired," "Error communicating with Analysis Service," and "There was an error when attempting to create a new session." The appropriate troubleshooting depends on the error displayed.
• Check network connectivity: If the error indicates a network connectivity issue during session creation, Microsoft recommends checking the network configuration, including VPN settings, network policies, and firewall rules, to ensure that nothing is blocking the browser from connecting to the Power BI service.
• If the Semantic Model uses DirectQuery: Paginated Report queries using a Power BI DirectQuery Semantic Model have a fixed 10-minute timeout. For queries that take longer than 10 minutes, Microsoft recommends using the Semantic Model's XMLA endpoint as the report data source.
• Check the browser if applicable: For the documented Chrome 142 session-creation issue, Microsoft recommends trying Microsoft Edge or an earlier version of Google Chrome.
For more details, please refer to the below Official Microsoft Documentation:
• Troubleshoot Paginated Report Session and Connection Issues - Power BI | Microsoft Learn
• Create Embedded Data Sources for Paginated Reports in the Power BI Service - Power BI | Microsoft Learn
• Supported Data Sources for Power BI Paginated Reports - Power BI | Microsoft LearnI hope this helps. Please feel free to reach out if you have any further questions.
Thank you.Hi v-abhinavmu,
Thank you for your response.
Actually, I believe the case I experienced is a rather unusual one. I was hoping to get some technical support, but unfortunately, whenever I try to submit a support ticket, the page keeps redirecting me to the general troubleshooting articles and the standard checks you mentioned.
In my case, all of my Paginated Reports were working normally and had a valid connection to their Semantic Models before the Semantic Model refresh. Also, I’ve refreshed the Semantic Models many times in the past, and this has never caused the Paginated Reports to lose their connections before.
What makes this case even more unusual is that creating a new Paginated Report, which was not actually related to the problematic report, somehow caused the existing report to regain its connection to the Semantic Model.
That seems quite strange, right?
I’d be happy to work with a technical support engineer the next time I encounter the same issue, so we can hopefully capture more details while it is happening.
For now, the connection issue with my reports has been resolved in a unpractical way, and I’ll continue to monitor the situation.
Thank you again for taking the time to respond and help!
- v-abhinavmu
Hi YL_TCI,
Thank you for the detailed update. I’m glad to hear that the connection issue with your Paginated Reports has been resolved.
I appreciate you sharing your observations and continuing to monitor the behavior. Please feel free to share any further updates or findings that may help provide additional insight into the issue.
Thank you again for keeping the community updated.
Hi, v-abhinavmu
I found another Paginated Report in the same situation I described here.
This time, I downloaded the support document, so hopefully there is some information that can help with troubleshooting.
Is there any chance I could speak with someone from Microsoft Technical Support about this issue?
The way I was able to resolve the previous issue is absolutely not a practical or expected solution:
Create a new Paginated Report in order to restore the connection between an existing Paginated Report and its Semantic Model?
I really hope this is not a recommended workaround from Microsoft. 😅
I’d really like to understand what is actually causing this behavior, especially since I have now encountered the same issue with another Paginated Report.
Thank you!
- v-abhinavmu
Hi YL_TCI,
Thank you for the update and for sharing these additional details.
Since the same behavior has now occurred with another Paginated Report, the support information you captured may provide useful details for further investigation.
If you’re able to share the support document or the relevant error details here, we can review them and see whether they provide any additional insight into the issue.
Thank you for continuing to document your findings and keeping the community updated.
Hello v-abhinavmu,
I have to say, I’m not comfortable posting the support document publicly in the forum. I don’t know whether it contains sensitive or environment-specific information.
To be honest, I’m a little surprised that the suggestion is to post the support document publicly. I don’t think that would be an appropriate way to handle a technical issue that may involve environment-specific information.
I’m happy to provide the relevant details directly to Microsoft Technical Support through an appropriate private channel.
