Forum Discussion
Helper IAnalysisServices: The connection is not open.. Microsoft.Data.Mashup.ErrorCode = 10478
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).
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_WHThank you for your reply. I have tried all your suggestions but still to no avail. The data size is just 5MB.
- AnkitKukreja
Super User
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.
Hi Max_WH,
I suggest reaching out to Microsoft Support by raising a ticket. Microsoft will analyze backend logs and provide a resolution
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticketRegards,
Vinay Pabbu
- dbeavon3
Memorable Member
Hi Max_WH and Anonymous
It has been three weeks since you first mentioned this bug . Did you open a ticket (SR with Mindtree)?
I'm about to open a similar ticket. Would be nice to know your SR number or ICM number.
Did you expand the refresh history to find the multiple failures, per refresh attempt? I think this is a problem that originates with the mashup engine. I think there is some sort of self-inflicted timeout and cancellation. There is exponential backoff as well. I totally HATE the way Microsoft implements retries to hide their own bugs. This troubleshooting is taking many hours longer than it should, simply because of the mandatory retries that are doomed to fail. (Doom is a good word for the feeling, whenever I'm working with these PBI bugs.)Just as with OP, my queries run fine on the local PBI desktop but not in the service. They fail comparatively quickly in the service.
Before failure I am seeing lots of successful activity in the sql profiler trace (image below). However after a period of time, the queries stop executing, presumably because the PQ mashup engine commits suicided. Notice that the queries are hitting my capacity from a PQ mashup engine running in azure (north central)
The dataset refresh is moving data from one dataset to another via a "cloud connection", rather than a gateway. Like so:
Any information would be appreciated. It feels like the type of ticket that will take far too long (3 weeks)? I'm hoping you can help me avoid some of that delay.
