Unexplained failure in Azure data factory (get metadata)

Question

Hello,

The issue details we encountered;

There was one failure which could not be explained by code or data issues and no clear error message was found. At similar time other invocations of the same pipeline did complete without any errors. After retriggering the same input file it was processed successfully.

Date: 2024-08-06 10:39:26 AM

Activity type: Get Metadata

Error code: 2010

Failure type: User configuration issue

Details: Object reference not set to an instance of an object.

---

But we can not display any logs, when I try to check it with RunID it shows the below message

we should see it in 45 days as in the mentioned link

https://learn.microsoft.com/en-us/azure/data-factory/monitor-data-factory:

I would be appreciated if you guide me, Thank you!

Answer 1

@Ekiz, Kuebra (098)

Welcome to the Microsoft Q&A and thank you for posting your questions here

It looks like you’re encountering a common issue in Azure Data Factory where the error message “Object reference not set to an instance of an object” can be tricky to diagnose. Here are a few steps you can take to troubleshoot and resolve this issue:

1. Check Configuration: Ensure that all configurations and parameters for the activity are correctly set. Sometimes, a missing or incorrect configuration can cause this error.
2. Review Dependencies: Verify that all dependencies and linked services are properly configured and accessible.
3. Recreate Activity: Try deleting and recreating the “Get Metadata” activity in your pipeline. This can sometimes resolve issues caused by corrupted activity configurations.
4. Integration Runtime: Ensure that your integration runtime is properly configured and running. Issues with the integration runtime can sometimes cause this error.

Regarding the log display issue,

the error message in your screenshot suggests that logs may not be immediately available for fresh activity executions. Ensure that the RunID is older than 2 days before attempting to view the logs.

If the issue persists beyond this period, it might be worth checking if there are any service disruptions

do let us know if issue persists. we will further investigate and help you out .