Forum Discussion
Continued ContributorError when connecting to Semantic Model from Excel "connection open intermittent..."
Hi everyone,
I have multiple semantic models with incremental refresh in a specific workspace. Three reports are working well when I connect to them from Excel, but there's one report where, when I try to connect, the following error appears: "Connection open intermittent error while reading in Analysis Services, needs retry." All semantic models have the same configuration, but I don't know why I can't connect to this one (multiple users have tested it, and we all encounter the same error). Any ideas?
Thanks
Hi Everyone! Thanks for your answers but I found the problem:
We can't have two semantic models with the same name in the same workspace (well, we can, but that was causing the issue). So I renamed them and it's working.
5 Replies
v-sgandrathiCommunity Support
Hi julsr,
This issue is typically not caused by the Excel client but by the state or structure of the semantic model itself. Even if all models have the same configuration, errors can occur if the model is in a temporary or unhealthy state on the service side. Common reasons include stuck or long running incremental refreshes, partitions that are processing or have failed, corrupted metadata, or large models that time out during metadata exchange with Excel. Since several users are facing the same problem, it suggests a backend issue with the dataset rather than a local client or network problem.
To start troubleshooting, review the refresh history and check for any ongoing, failed, or canceled refreshes. You can try a full refresh or republish the model to rebuild the metadata. If using Direct Lake or incremental partitions, make sure all partitions are in a Ready state and there are no pending schema changes. Often, republishing the PBIX or recreating the semantic model can resolve connection errors.
Thank you.
- v-sgandrathi
Hi julsr,
we haven't heard back from you regarding our last response and wanted to check if your issue has been resolved.
Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum! - v-sgandrathi
Hi julsr,
We haven't heard back from you regarding our last response and wanted to check if your issue has been resolved.
Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum! - julsr
Hi Everyone! Thanks for your answers but I found the problem:
We can't have two semantic models with the same name in the same workspace (well, we can, but that was causing the issue). So I renamed them and it's working.
