Integration run time status on azure running(unhealthy)

Hi Sara,
The logs confirm that the scan is completing successfully but ingestion is not occurring, which indicates an ingestion initialization failure on the Self-hosted Integration Runtime (SHIR).
This means the scan pipeline ran, but no metadata was generated for ingestion.

• Missing SAP dependency: sapnco 3.1 not installed

NET assembly conflict: Microsoft.Bcl.AsyncInterfaces version mismatch

• Ingestion module (AtlasIngestionWriterForScan) fails to initialize and gets disposed

1. Clean reinstall SHIR
   • Uninstall SHIR
   • Delete:

          C:\Program Files\Microsoft Integration Runtime\
     

C:\ProgramData\Microsoft\DataTransfer
```

1. Install latest SHIR version from Purview
2. Install prerequisites
   • SAP .NET Connector (NCo 3.1, 64-bit)
   • .NET Framework 4.8 or higher
3. Avoid manual DLL changes (prevents assembly conflicts)
4. Restart & validate
   • Restart SHIR service
   • Run Diagnostics from Integration Runtime Configuration Manager

References
https://learn.microsoft.com/en-us/azure/data-factory/self-hosted-integration-runtime-troubleshoot

https://learn.microsoft.com/en-us/azure/data-factory/connector-sap-table#prerequisites

https://learn.microsoft.com/en-us/azure/purview/register-scan-on-premises-sql-server

Thank you @SAI JAGADEESH KUDIPUDI for your attention. I have uninstalled Run time and reinstall version 5.51 again and status problems solved. but my main issue , exception "Information 2/12/2026 11:07:43 AM Integration Runtime (Self-hosted) Connectors 30000 None [4320] [07:37:43] [ScanResultId:][TaskId:][PID:4320][JobName:contextinfos.ingestionclient.handler][TaskSlotId:-1][Uri:1b8b6ed2-60f5-469f-8ee6-e156b780a2ba] logger: Module ingestionclient.services initialize failed: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileLoadException: Could not load file or assembly 'Microsoft.Bcl.AsyncInterfaces, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Job ID: b1a3c410-2db5-4f68-9588-b51ffa5c8034", is still there during scanning and as a result all discovery, classification and ingestion show success but ingestion is zero.

I have downloaded integration run time from azure purview.

Would you please guide me ? what is wrong here?

Thanks

Event viewer log file:

log.txt

Hi Sara,
This behavior occurs because the self-hosted Integration Runtime service is running, but the required SAP dependency is missing on the server. The Event Viewer log clearly shows the failure:

“Load sapnco 3.1 failed. Could not load file or assembly ‘sapnco, Version=3.1.0.42’. The system cannot find the file specified.”

When the SAP .NET Connector (SAP NCo) assembly is not available on the machine where the self-hosted Integration Runtime is installed, the SAP connector cannot initialize. In this situation, the scan may appear as completed in preview, but the actual ingestion result is zero because the runtime is unable to load the SAP libraries required to read metadata or data. This dependency failure is a known and documented cause of SAP connector failures on self-hosted Integration Runtime nodes.

The “Running (Unavailable)” status in the Azure portal does not indicate that the runtime is healthy for execution. It usually means the service is installed and running locally, but it cannot successfully execute workloads or communicate fully due to environment or dependency issues. Microsoft documentation confirms that dependency and connectivity issues commonly cause this status and recommends validating logs and dependencies on the runtime machine.

The resolution is to install the correct SAP .NET Connector version on the same server where the self-hosted Integration Runtime is installed. The SAP Connector for Microsoft .NET (NCo 3.1) must be present so that the sapnco assemblies can be loaded at runtime. After installing SAP NCo, restart the Microsoft Integration Runtime (Self-hosted) service and rerun the scan. SAP officially documents SAP NCo 3.1 as the required connector for .NET-based SAP integrations and lists it as a prerequisite.

If the runtime still shows “Running (Unavailable)” after installing SAP NCo, Microsoft recommends running the Self-hosted Integration Runtime Diagnostic Tool from the Integration Runtime Configuration Manager to validate connectivity, firewall, and environment configuration. This tool performs standard health checks and helps identify remaining issues that prevent the runtime from operating correctly.

References Links:
Create common SAP workflows – Troubleshoot “could not load file or assembly sapnco …” (Install required SAP NCo)

Configure SAP source system with Azure Data Factory – Prerequisites include installing SAP .NET Connector and SHIR
SynapseSelfHostedIntegrationRuntimeNodeStatus.InitializeFailed Property
https://learn.microsoft.com/en-us/dotnet/api/azure.resourcemanager.synapse.models.synapseselfhostedintegrationruntimenodestatus.initializefailed?view=azure-dotnet
Demo Scanning - Adding On Premise SQL Server as an asset to Azure Purview 
https://microsoft.sharepoint.com/:w:/r/teams/CSUDataAICommunityIPLibrary/_layouts/15/Doc.aspx?sourcedoc=%7BB92BABA9-C93E-49EE-8C2A-E367E5B0FA3A%7D&file=Demo_SQLServer_OnPrem-Self_integrated_runtime_in_Microsoft%20purview.docx&action=default&mobileredirect=true&DefaultItemOpen=1
Creating Azure hosted Integration Runtime with Managed Virtual network 
https://microsoft.sharepoint.com/:w:/r/teams/GDTools/VWW/_layouts/15/doc2.aspx?sourcedoc=%7B95ECF629-0EF4-4B9F-BFD7-34498B5254DC%7D&file=Azure%20hosted%20Integration%20Runtime%20with%20Managed%20Virtual%20network.docx&action=default&mobileredirect=true&DefaultItemOpen=1