Forum Discussion
Helper IAnalysisServices: The connection is not open.. Microsoft.Data.Mashup.ErrorCode = 10478
Encountering data refresh failure on app.powerbi.com online services.
But the data is able to refresh via PowerBI desktop.
Failures like the below
Data source error: DataSource.Error: AnalysisServices: The connection is not open.. Microsoft.Data.Mashup.ErrorCode = 10478. DataSourceKind = AnalysisServices. DataSourcePath = powerbi://api.powerbi.com/v1.0/myorg/dsa
Data source error: DataSource.Error: AnalysisServices: The connection either timed out or was lost.. Microsoft.Data.Mashup.ErrorCode = 10478. DataSourceKind = AnalysisServices. DataSourcePath = powerbi://api.powerbi.com/v1.0/myorg/dsa
Hi Max_WH
My support case for this error message is almost ready to be closed. I thought I'd let you know. It turns out there was a bug in the way the PQ mashup engine interacts with the underlying connections to the PBI dataset. This behavior should be documented by Microsoft in the near future, and I'll post a link here.
I opened two SR # for this bug:
2503220040000275
and2504010010001220
The second was a unified/premier case.
I'm not totally sure, but I think your case and my case were both associated with the same internal IcM (Incident-603360591) You should be able to confirm that with your Mindtree engineer, if you provide my IcM number.
I have an RCA and a longer explanation can be found here:
https://community.fabric.microsoft.com/t5/Service/DataSource-Error-AnalysisServices-The-connection-either-timed/m-p/4702221/highlight/true#M276330The RCA for my case is like so:
I don't know if that helps. At the end of the day, the workaround is pretty straightforward. You have to wrap any queries for the AnalysisServices connector, and put Table.Buffer around them. This ensures that connections won't be held open for long periods of time resulting in socket exceptions. In my case the offending connection was being held open for internal reasons that are NOT in my control. It has something to do with the fact that we are using one query as the driver to loop/execute some nested queries.
Hopefully this is makes sense. Your best is to test with Table.Buffer and see if that avoids the error. IMO this is an obvious bug, but the ASWL PG doesn't currently see it that way (possibly because the bug isn't theirs but belongs to a related product team - PBI integrations or whatever).
17 Replies
- AnkitKukreja
Super User
Hi! Max_WH
What is the data source? Also, are you calling large amount of data? Try with small amount of data if that works, also make sure you can implement incremental refresh if possible so you are not refreshing huge chunck of data everytime.
Max_WHThank you for your reply. It seems not the case. the volume of the data is normal. The data can be refreshed from Power BI Desktop but fails on Power BI online service.
DataSourcePath = powerbi://api.powerbi.com/v1.0/myorg/
Hi Max_WH,
Thank you for reaching out to Microsoft Fabric Community Forum.
Please verify the below steps:
- Check the Capacity Metrics App for resource consumption and throttling. If on a Shared Capacity, refresh failures might be due to resource limits—consider moving to a dedicated capacity.
- If in Import Mode, check if the dataset is too large or exceeding service limits.
- Check Data source credentials, re-enter credentials, and ensure they match what you use in Power BI Desktop.
- Open the dataset in Power BI Desktop, re-publish it to the same workspace, and reconfigure refresh settings.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Regards,
Vinay Pabbu- Max_WH
Thank you for your reply. I have tried all your suggestions but still to no avail. The data size is just 5MB.
- AnkitKukreja
Hi! Max_WH
I would recommed you to try publishing it to different workspace and also I would recommend to try and create a dataflow with same source and see if issue still persists? This way we might be able to narrow down the issue.
rohit1991Hi Max_WH
The connection is not open. You can try some of these things:
-
Credentials in the Service:
Go to Power BI Service -Dataset Settings -Data source credentials, and re-enter the credentials for your model even if they worked before. This error often shows up when the Service can’t authenticate to one of the sources. -
Gateway mapping:
If you’re using a gateway, double-check the mapping. Make sure it’s connected and the source is mapped exactly like it is in Desktop (server name, database, etc.). -
Privacy levels:
On the Desktop side, sometimes things work because privacy settings are ignored or simplified. But in the Service, if you're combining sources and their privacy levels don't match, it can silently block connections. Try setting both to Organizational under Options -Privacy -Current File -Data Sources. -
Live/Direct connections:
If your model is using a live connection to SSAS or AAS, also confirm that the Service has proper access via Azure AD or a gateway that supports the same authentication method.
If none of these help, grab a screenshot of the full error message from the refresh history or gateway logs that can sometimes point more specifically to the source that's failing
-
