Forum Discussion
pipeline error
Pipeline was working, now I am receiveing the next message.
Failure happened on 'destination' side. ErrorCode=LakehouseOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Lakehouse operation failed for: An error occurred while sending the request.. Workspace: '7f81ddcc-15a8-4d76-848c-b43236058c8c'. Path: '4bdce7fb-9eb5-4518-bab8-8df25169c33a/Tables/Person/_delta_log'..,Source=Microsoft.DataTransfer.ClientLibrary,''Type=System.Net.Http.HttpRequestException,Message=An error occurred while sending the request.,Source=mscorlib,''Type=System.Net.WebException,Message=The underlying connection was closed: An unexpected error occurred on a receive.,Source=System,''Type=System.IO.IOException,Message=Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.,Source=System,''Type=System.Net.Sockets.SocketException,Message=A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond,Source=System,'
6 Replies
Hi rscorians
Thanks for using Microsoft Fabric Community.
There might be a chance of an intermittent issue could you please follow the below steps that might help you.
Temporary Glitch: Clearing cookies and caches can sometimes resolve temporary glitches within the application that might be causing the issue.
Corrupted Data: In rare cases, corrupted data stored in the browser's cache related to Microsoft Fabric might be causing the issue. Clearing the cache removes this potentially problematic data.
Hard Refresh: A hard refresh bypasses the cached version of the webpage and forces the browser to download the latest version from the server. Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac).
Try Microsoft Edge: If you are currently using Chrome or Firefox, try switching to Microsoft Edge to see if the issue persists. Edge is the native browser for Microsoft products and might have better compatibility with Microsoft Fabric.
I hope this information helps.
Thank you.
Hi rscorians
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.Thank you.
Hello,
We've attempted the solution, but it isn't working. The resolution was not satisfactory.
We need a different approach to understand how to solve this issue.
According to Microsoft documentation, we added the necessary outbound rules:
This configuration allows the necessary communication for these services to function properly.
Protocol: TCP Endpoints:
- *.datawarehouse.pbidedicated.windows.net
- *.datawarehouse.fabric.microsoft.com
- *.dfs.fabric.microsoft.com Port: 1433
Protocol: TCP Endpoint: *.frontend.clouddatahub.net Port: 443
After implementing these rules, the system worked for only a few hours.
It appears that the DNS resolution of these URLs is highly dynamic and can stop working unexpectedly.
Do you have any solutions or suggestions for us to try?
Thank you in advance.
Hi rscorians
Apologies for the inconvenience.
Please reach out to our support team to gain deeper insights and explore potential solutions. It's highly recommended that you reach out to our support team. Their expertise will be invaluable in suggesting the most appropriate approach.
Please go ahead and raise a support ticket to reach our support team:
https://support.fabric.microsoft.com/support
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
Thank you.
Hi rscorians
We haven’t heard from you on the last response and was just checking back to see if you've had a chance to submit a support ticket. If you have, a reference to the ticket number would be greatly appreciated. This will allow us to track the progress of your request and ensure you receive the most efficient support possible.
Thank you.
The problem was related to the firewall's outbound rules. A potential solution would be to use a staging account.
