Azure Blob Source Error: The remote server returned an error: (400) Bad Request

2
votes

I have created Data Flow Task in SSIS and configured Blob storage container.My request to process from Azure Blob to SQL server.I am getting "The remote server returned an error: (400) Bad Request" exception while executing SSIS.

I have verified the connectivity and access in Azure.

execution error No debug error

2
azuressisazure-storage-blobs
do you want to copy one file or all the files in blob to SQL Server? Can you show us any screenshots or more details? – Leon Yue
Did you use the account and access key to access the blob storage ? – Leon Yue
Attached screenshot in above, kindly verify and advise. – Meena
I am trying load flat file data from azure blob storage --> azure sql server using SSIS – Meena
Hi @Meena, I got it. Just from your second screenshot, you get the in progress but the data flow works well and the data have been load to SQL Server successfully, am I right? – Leon Yue

2 Answers

1
votes

@Meena

You need to add two Key to windows registry

To use TLS 1.2, add a REG_DWORD value named SchUseStrongCrypto with data 1 under the following two registry keys.

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.0.30319

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319

This works.

0
votes

Just from your second screenshot, you get the error in progress but the data flow works well and the data have been load to SQL Server successfully, am I right?

I tried the same SSIS package(Load data from Blob to SQL Server) but has no error. Please try delete and reset the Azure Blob Source.

Test the connection when we create the source: enter image description here

Azure Blob Source editor:

enter image description here

Progress: enter image description here

Just from your progress error, we can not find which cause the 400 bed request error. But We can try re-create the source again to check if it will happen again. And most of all, the data flow task works well and all the data loaded to SQL Server correctly.