It was a Firewall issue!
Error writing to Datalake Gen 2

Hello,
my Source is a SQL Server, queried with a Self Hosted IR Runtime and my sink is a Datalake Gen 2,
I get the following Error
Failure happened on 'Sink' side. ErrorCode=AdlsGen2OperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=ADLS Gen2 operation failed for: Operation returned an invalid status code 'Forbidden'. Account: 'mydatalake'. FileSystem: 'temp'. Path: 'NavTemp/navcustomer.csv'. ErrorCode: 'AuthenticationFailed'. Message: 'Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.'. RequestId: '1148db6e-a01f-0069-616e-d94891000000'. TimeStamp: 'Wed, 23 Dec 2020 20:59:25 GMT'..,Source=Microsoft.DataTransfer.ClientLibrary,''Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Operation returned an invalid status code 'Forbidden',Source=,''Type=Microsoft.Azure.Storage.Data.Models.ErrorSchemaException,Message=Operation returned an invalid status code 'Forbidden',Source=Microsoft.DataTransfer.ClientLibrary,'
If I read from other Sources (using Self Hosted or Azure IR) and write to the same DataLake it works.
Could it be the Source?
Thank you so much
Hello,
thank for your reply.
I use Account Key.
What is strange is that I use this Linked Service in all my pipelines about 50 with different data sources without any issue.
I only get issues with this particular SQL Server and this integration Runtime (version 4.15.7611.1) even if I can read the tables (Preview shows no issues) but it is not able to sync to the ADLS Gen 2.
Do you have a private email where I can send you my Run Id?
Thank you so much
Hi @Silvano P ,
Sure, please share pipeline run id in mail to AzCommunity[at]microsoft[dot]com with subject - "Attn:Haritha - Error writing to Datalake Gen 2" and we will assist you further in resolving the issue.
Hi @Silvano P ,
As discussed in the mail, our product team mentioned it as a firewall issue at the ADLS folder that might have triggered the error. Please suggest if checking the same resolved the issue.
Looking forward for your response!
Hello,
Yes it was a Firewall issue!
Thank you so much for your help on this
Sign in to comment