SSIS - Azure - ADLS Gen2 operation failed for: Object reference not set to an instance of an object.

Question

I made a very simple ETL package, the ETL package sends Azure data from Oracle Database with "Flexible File Destination".

The ETL package is running on my local computer. But after deploy, it keeps waiting on the server for a long time. It finally gives the following error.

Inside the ETL package, I added the service principal key as an expression as a constant value between double quotes. It works fine on my local computer. I have the problem running on the server after deploying. According to the error message, it seems like there is a missing reference. I could not figure out what happened. I would like the help of the knowledgeable friends.

Sent To Data - xxlx3exxb03 - DEV 27.04.2021 11:18 27.04.2021 12:38 4,822 80 Transfer data error : Microsoft.DataTransfer.Common.Shared.HybridDeliveryException: ADLS Gen2 operation failed for: Object reference not set to an instance of an object.. Account: 'xxlx3exxb03'. FileSystem: 'xxxxxxxxx'.. ---> Microsoft.DataTransfer.Common.Shared.HybridDeliveryException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.IdentityModel.Clients.ActiveDirectory.Internal.Http.AdalHttpClient.<GetResponseAsync>d__221.MoveNext() \--- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.IdentityModel.Clients.ActiveDirectory.Internal.Http.AdalHttpClient.<GetResponseAsync>d__221.MoveNext()
--- End of stack trace from previous location where exception was thrown ---

Answer 1

Hi @Oktay Bozdemir ,

Welcome to Microsoft Q&A!

Here has a similar thread with yours, see below:

In order to fix this particular issue, just right click on the role (in the roles folder under cloud configuration) and select "Add Diagnostic Configuration", then Build the solution and attempt to publish. These diagnostics files are ONLY needed when publishing directly from Visual Studio.

Best regards,
Carrin

---

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

I am using Visual Studio 2012 and SQL Server 2012. My target is to send data to Azure from Oracle database with "Flexible File Destination".
Is "Add Diagnostic Configuration" only on the Azure portal enough? Do I have to do anything in Visual Studio 2012?

We're deploying in Visual Stodio. I'm running the etl package from under the SSIS catalog, but I get the error I mentioned.

Answer 3

Our process:
We use SQL Server 2012, SSIS 2012 and Visual Studio 2012.

Our target is to send data to the Azure system. For this, we did the steps on the following website, Azure Feature Pack Setup was installed, Java was installed, TLS 1.2 was set.

https://learn.microsoft.com/en-us/sql/integration-services/azure-feature-pack-for-integration-services-ssis?view=sql-server-ver15

I developed and tested the ETL package in Visual Studio on my local computer. I have tested it many times.
I used "Flexible File Destination" for data submission. Source: Oracle Database, Destination: Azure- "Flexible File Destination".
I requested an installation on the SSIS server. Installations have been made. Azure Feature Pack was installed on the SSIS server, Java was installed, TLS 1.2 setting was made. There is no incomplete installation. But after deployed, I run the package from SSIS catalog, it waits for a long time and gives an error.

In summary, we do not do the deploy process to the azure system. We do the deploy operation to the usual SQL Server 2012/SSIS 2012.

Answer 4

Add the link "login.microsoftonline.com" to the whitelist or two or three of these links will be pinged. Firewall authority is defined for the learned IP range. Port: 443