From 8aff63e5c220fb1a84b91ff0d620f96b983b8b7a Mon Sep 17 00:00:00 2001 From: Tay Caliguiri Date: Tue, 18 Aug 2026 15:35:54 -0400 Subject: [PATCH 1/2] Add KB: collection scan stuck in Running status Covers AD, Entra ID, and Okta scans getting stuck in TaskInstances.Status = 1 with no timeout/watchdog to recover them, and how to manually clear the stuck task instance. --- ...collection-scan-stuck-in-running-status.md | 66 +++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 docs/kb/recoveryad/operations-and-troubleshooting/collection-scan-stuck-in-running-status.md diff --git a/docs/kb/recoveryad/operations-and-troubleshooting/collection-scan-stuck-in-running-status.md b/docs/kb/recoveryad/operations-and-troubleshooting/collection-scan-stuck-in-running-status.md new file mode 100644 index 0000000000..771b684ceb --- /dev/null +++ b/docs/kb/recoveryad/operations-and-troubleshooting/collection-scan-stuck-in-running-status.md @@ -0,0 +1,66 @@ +--- +description: >- + Shows how to resolve an AD, Entra ID, or Okta collection scan stuck in + Running status in Netwrix Identity Recovery by updating the + TaskInstances table and restarting the Task Server service. +keywords: + - collection scan stuck + - Running status + - TaskInstances + - Task Server + - Entra ID + - Okta + - Active Directory + - Netwrix Recovery for Active Directory + - NetwrixRecovery + - SQL Server Management Studio + - Identity Recovery + - StealthRECOVER +tags: + - kb + - operations-and-troubleshooting +products: + - recovery-active-directory +sidebar_label: Collection Scan Stuck in Running Status +title: "Collection Scan Stuck in Running Status" +--- + +# Collection Scan Stuck in Running Status + +## Symptom + +A collection scan (Active Directory, Entra ID, or Okta) remains in **Running** status indefinitely. The console shows no status details or error messages, and the scan never completes or times out. + +## Cause + +The scan hung during its collection step. Netwrix Identity Recovery does not apply a timeout to collection work for any of the three scan types, so a stalled directory query, Graph call, or Okta API call leaves the task instance at **Running** with no automatic recovery. + +## Resolution + +1. In your SQL Server Management Studio instance, locate the Netwrix Identity Recovery database. The default name is `NetwrixRecovery`. +2. Run a query to find the stuck task instance for the affected task: + +```sql +SELECT TOP 1 * FROM TaskInstances WHERE TaskID = '%taskID%' ORDER BY ID DESC +``` + +3. Update the `Status` column for that row to `8` (Failed): + +```sql +UPDATE TaskInstances SET Status = 8 WHERE ID = '%targetID%' +``` + +4. Restart the **Netwrix Recovery Task Server** service on the Netwrix Identity Recovery server. +5. In the console, start a new scan for the affected domain, tenant, or org. + +## TaskInstances.Status values + +| Value | Meaning | +|---|---| +| 0 | Initialized | +| 1 | Running | +| 2 | Paused | +| 4 | Stopped | +| 8 | Failed/Error | +| 16 | Completed/Finished | +| 32 | Waiting | From 2bf974520d95131ed93ea3005b66532c34171db5 Mon Sep 17 00:00:00 2001 From: hilram7 <212961752+hilram7@users.noreply.github.com> Date: Thu, 20 Aug 2026 23:06:17 -0700 Subject: [PATCH 2/2] Fix product ID and formatting in collection scan stuck KB article - Vale: correct heading case (TaskInstances.Status Values) - Derek: fix invalid products frontmatter ID (recovery-active-directory -> identityrecovery) - Derek: convert service name to inline code, trim repeated full product name --- .../collection-scan-stuck-in-running-status.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/kb/recoveryad/operations-and-troubleshooting/collection-scan-stuck-in-running-status.md b/docs/kb/recoveryad/operations-and-troubleshooting/collection-scan-stuck-in-running-status.md index 771b684ceb..f56e4fcd00 100644 --- a/docs/kb/recoveryad/operations-and-troubleshooting/collection-scan-stuck-in-running-status.md +++ b/docs/kb/recoveryad/operations-and-troubleshooting/collection-scan-stuck-in-running-status.md @@ -20,7 +20,7 @@ tags: - kb - operations-and-troubleshooting products: - - recovery-active-directory + - identityrecovery sidebar_label: Collection Scan Stuck in Running Status title: "Collection Scan Stuck in Running Status" --- @@ -37,7 +37,7 @@ The scan hung during its collection step. Netwrix Identity Recovery does not app ## Resolution -1. In your SQL Server Management Studio instance, locate the Netwrix Identity Recovery database. The default name is `NetwrixRecovery`. +1. In your SQL Server Management Studio instance, locate the Identity Recovery database. The default name is `NetwrixRecovery`. 2. Run a query to find the stuck task instance for the affected task: ```sql @@ -50,10 +50,10 @@ SELECT TOP 1 * FROM TaskInstances WHERE TaskID = '%taskID%' ORDER BY ID DESC UPDATE TaskInstances SET Status = 8 WHERE ID = '%targetID%' ``` -4. Restart the **Netwrix Recovery Task Server** service on the Netwrix Identity Recovery server. +4. Restart the `Netwrix Recovery Task Server` service on the Identity Recovery server. 5. In the console, start a new scan for the affected domain, tenant, or org. -## TaskInstances.Status values +## TaskInstances.Status Values | Value | Meaning | |---|---|