Forum Discussion

Sam_'s avatar
Sam_
Frequent Visitor
1 year ago
Solved

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...
Need Help
Pipeline
  • v-ssriganesh's avatar
    v-ssriganesh
    1 year ago

    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 Learn

     

    If 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.

Sam_'s avatar
Sam_
Frequent Visitor
1 year ago

Hey,

 

unfortunately not the issue still perists

 

Thanks,

Sam

schilling's avatar
schilling
New Member
1 year ago

Just resolved a similar issue. 

 

added service endpoint of microsoft.storage in the delegated gateway subnet in spoke vnet, that solved the issue. We had UDR 0/0 in the vnet gateway subnet pointing back to security appliance in hub vnet and subsequently routed back to on-prem for Internet access. . 

 

https://learn.microsoft.com/en-us/data-integration/vnet/data-gateway-architecture is not accurate, especially 

The VNet gateway doesn't require any Service Endpoint or open ports back to Power BI. Data from the VNet is returned to Power BI by an internal Microsoft tunnel that doesn't reach the public internet, which uses Automatic Private IP Addressing (APIPA) and exists on the infrastructure virtual machine.

 

We did firewall log analysis, and noticed that the https://learn.microsoft.com/en-us/data-integration/vnet/troubleshoot-data-gateway traffic is going through on-prem Internet, even after we punched temporary firewall holes, the write still not success with error message like:

Lakehouse operation failed for: Operation returned an invalid status code 'InternalServerError'.

Source=Microsoft.DataTransfer.ClientLibrary,
''Type=Microsoft.Azure.Storage.Data.Models.ErrorSchemaEx

 

So on the delegated vnet, we added microsoft.storage service endpoint, then subsequent write is successful.