How to Troubleshoot Your Integration Runtime (IR)

What Is the Integration Runtime (IR)?

The Integration Runtime (IR) is a Microsoft-hosted component that acts as a bridge between your on-premises environment and the Azure Data Factory pipelines powering Catalyst. It securely moves your data from local systems (like your ERP or SQL database) into Catalyst for analysis and reporting.

• For you (the client): IR ensures your internal systems can securely transmit updated data to Catalyst.

• For EBM: We use IR to automate, schedule, and monitor those transfers. If it goes offline, data can’t sync properly, which can lead to stale reports or failed jobs.

Most IR setups are installed directly on a server in your environment and registered with a unique key that ties your instance to your ADF pipelines. Occasionally, the IR can become disconnected or need to be re-authenticated—especially after a server update, firewall change, or expired token.

✅ When You Should Follow This Guide

• Your IR shows Stopped, Disconnected, or isn't syncing data

• Smartload uploads aren’t processing or reports are outdated

• You're instructed by EBM support to re-register the IR

How to Troubleshoot

If your Microsoft Integration Runtime (IR) is stuck, offline, or no longer connecting to your pipelines, follow these steps to restart and re-register the IR service.

Step 1: Open the Integration Runtime App

• On your server, open the Start Menu and search for "Integration Runtime".

• Launch the Microsoft Integration Runtime Configuration Manager.

Step 2: Check IR Status

• If it shows Running, you're good to go.

• If it says Stopped or Disconnected:

  • Click Stop, wait a few seconds, then click Start.

  • This often resolves minor issues.

Step 3: Re-register the Integration Runtime

If restarting doesn’t fix it, re-register the IR with a new key.

Instructions:

1. Open PowerShell as Administrator.

2. Run:

cd "C:\Program Files\Microsoft Integration Runtime\5.0\Shared"
.\UnregisterIntegrationRuntime.ps1

3. Get a new IR key from your Azure portal (in ADF).

4. Run:

.\RegisterIntegrationRuntime.ps1 -IntegrationRuntimeKey "PASTE_YOUR_KEY_HERE"

Step 4: Restart the Service

Still in PowerShell, restart the service:

net stop "DIAHostService"
net start "DIAHostService"

Step 5: Confirm It’s Working

• Open the Integration Runtime app again.

• It should now say Running and show it’s connected.

🔁 Still Not Working?

If none of the steps in this guide resolve the issue, the best course of action is to reinstall the Integration Runtime on your server. After reinstalling:

1. Reach out to EBM Support to request your authentication key.

2. We’ll provide the key securely through our secure password manager.

3. You’ll use this key during the IR registration process to re-establish the connection.

Once your IR is successfully re-registered, Catalyst will resume pulling in data as normal.

🆘 Need Help?

If the steps don’t work:

• Make sure you're copying the full key from Azure

• Try using Set-ExecutionPolicy Unrestricted in PowerShell if you get a script error

• Contact our support team with a screenshot and error message