Forum Discussion
VNET data gateway cannot write to lakehouse
I have come accros an issue that wont allow me to write data to a lakehouse in a copy activity that utilises a VNET data gateway. The error messages references lakehouse Internal Server Error.
I can successfully preview my data from my VNET data gateway source and as the error suggests the issue is associated with writing to the destination lakehouse. Please help, has anyone been able to successfully use VNET data gateways to land data to a lakehouse?
ErrorCode=LakehouseOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Lakehouse operation failed for: Operation returned an invalid status code 'InternalServerError'. Message: 'Internal Server Error'. TimeStamp: 'Thu, 24 Apr 2025 10:13:16 GMT'..,Source=Microsoft.DataTransfer.ClientLibrary,''Type=Microsoft.Azure.Storage.Data.Models.ErrorSchemaException,Message=Operation returned an invalid status code 'InternalServerError',Source=Microsoft.DataTransfer.ClientLibrary,'
Hi Sam_,
Please consider raising a Microsoft support ticket. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your issue or provide a solution that isn't immediately obvious.
Below is the link to create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft LearnIf this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.
10 Replies
Hello Sam_,
Thank you for reaching out to the Microsoft Fabric Community Forum. Based on the information provided, here are some insights and potential troubleshooting steps:
- Check the VNET data gateway and the lakehouse are in the same region, as the gateway can only be accessed from your tenant's home region.
- When using a virtual network data gateway and a private endpoint to connect to a data source, you might experience occasional TCP connection issues. This is a known problem and will be resolved in future updates.
- VNET data gateways currently support only admin roles and not "Can Use and Can Use+Share" for Power Platform dataflows.
- Check for any network connectivity issues between the VNET data gateway and the lakehouse.
- Make sure the VNET data gateway is properly configured and that the necessary roles and permissions are assigned.
For your reference: https://learn.microsoft.com/en-us/data-integration/vnet/overview#limitations
If possible, test the VNET data gateway with different data sources to identify if the issue is specific to the lakehouse or a broader problem with the gateway.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.Hi Sam_,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.Hi Sam_,
May I ask if you have resolved this issue? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hey,
unfortunately not the issue still perists
Thanks,
Sam
Hi Sam_,
Please consider raising a Microsoft support ticket. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your issue or provide a solution that isn't immediately obvious.
Below is the link to create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft LearnIf this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.
We were experiencing the same errors, I can confirm adding the
Microsoft.Storage service endpoint to our delegated VNET Data Gateway subnet fixed the issue.
