Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more
Hello Community
I have seen many posts with the error "AzureBlobs failed to get the response" and all posts say that the IPs need to be whitelisted in the firewall to establish the connection. But I feel that is not true.
I have hosted SQL and my data gateway fetches data from SQL using dataflow ( not premium ).
It refreshes almost all schedules. and randomly fails on some schedules. let's say the success rate of dataflow is 90% or more. This data flow has 6 tables to be updated from the same SQL.
Out of 6 tables, only one table fails to update time it fails after running for 6 minutes to 12 minutes. Now Timeout can not be the reason for failure because when it successfully ran the time it took was 19 minutes.
When it fails it gives the below error:
Error: AzureBlobs failed to get the response: 'The remote name could not be resolved: 'wabiindwescdsa.blob.core.windows.net''.
Request ID: 6d23eaf9-1c07-4aee-b256-d0452b3e1fd4
Activity ID: cc3e6946-f0ee-42e1-8ec7-
If the firewall is a problem then how the dataflow is updated 90% time?
Why other 5 tables are updated from the same SQL and only one table is failed?
If the timeout is the problem then how the failure is on fewer minutes and success shows more minutes?
I do not have any answer as to why this randomly fails only to update one table from the same SQL and all other tables are updated. If just after the failure message I get I run it on demand it runs successfully. No explanation.
Kindly if anyone can suggest to me what to check and where to see why "wabiindwescdsa.blob.core.windows.net" is suddenly not reachable only for one table do let me know.
Solved! Go to Solution.
Yes, it got resolved and the solution was very odd.
Create a new workspace and copy the dataflow to the new workspace and then the failure stopped. It's like redoing ( recreating ) the workspace.
Hello @RajeshB and @Anonymous , how are you?
Did you get any solution?
Thanks and regards.
Yes, it got resolved and the solution was very odd.
Create a new workspace and copy the dataflow to the new workspace and then the failure stopped. It's like redoing ( recreating ) the workspace.
Hi @RajeshB ,
Have submitted this issue internal to confirm, would update here as soon as possible if there is any update about it.
Best Regards
Community Support Team _ Rongtie
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello @Anonymous
I have also contacted Microsoft Help and await a response in case I get an answer, I will let you know.
Thanks
Check out the April 2025 Power BI update to learn about new features.
Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
User | Count |
---|---|
47 | |
33 | |
24 | |
19 | |
14 |