---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Discovery start and classification issue resolution

# Discovery start and classification issue resolution {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Use the Discovery Admin Workspace Diagnostics page to identify and resolve the cause when Discovery fails to start or classify a device.

Most start and classification failures have one of a few causes: the MID Server can't reach the target, the configured account lacks the required rights on the target, or software on the target host blocks Discovery scripts from running. The [Diagnostics](https://www.servicenow.com/docs/aWelbE5mIeP7g4twKx0liw "The Diagnostics page helps you prioritize and address errors and anomalies in IP-based and Cloud Discovery schedules.") page identifies most of these causes with a refined code that includes the root cause and remediation steps.

## Requirements {#disco-start-issue-resolve__section_zcp_31f_fkc}

The Diagnostics page, refined codes, and AI Insights described here require the Error Framework. Confirm the following:

* The ServiceNow AI Platform is running the Brazil release, or the Australia release beginning with Patch 3.
* Discovery Admin Workspace, beginning with v1.17.0, is installed.
* The sn_disco_workspace.enable_error_framework system property is set to <kbd class="ph userinput">true</kbd> (default behavior).
* You have the discovery_admin role.

{#disco-start-issue-resolve__ul_yts_lpt_fkc}To use AI Insights, install the plugins listed in the following table.{#disco-start-issue-resolve__table_lmp_spt_fkc__entry__3}

| Plugin name | Plugin ID | Availability |
|-|-|-|
| ServiceNow Otto for Error Framework | com.sn_ef_gen_ai | Australia Patch 3 |
| ServiceNow Otto | sn_genai_platform | Required by ServiceNow Otto for Error Framework |
[ ]

{#disco-start-issue-resolve__table_lmp_spt_fkc}

## Issue resolution process {#disco-start-issue-resolve__section_idg_2qt_fkc}

The Diagnostics page displays Discovery errors that have been refined and assigned a specific error code. Each refined code identifies the error type and includes the root cause and recommended remediation steps. Start and classification
failures fall into two groups. When a cause can be refined, the Diagnostics page provides guidance to help resolve it. When a cause cannot be refined, no error code is available and you must verify the
cause manually. Work through the causes in the order that follows.

## Review the Errors tab {#disco-start-issue-resolve__section_lk2_fqt_fkc}

Navigate to WorkspacesDiscovery Admin WorkspaceDiagnostics and review the Errors tab. Locate the error by refined code, then open it to view the root cause and remediation steps. Errors that stop Discovery for a device or schedule display with Critical severity.  
The following refined codes commonly correspond to start and classification failures.{#disco-start-issue-resolve__table_tjr_3qt_fkc__entry__2}

| Refined code | Cause |
|-|-|
| SN-DISC-5602 | MID Server isn't running on Windows. |
| SN-DISC-1007 | SSH connection failed. |
| SN-DISC-3486 | Probe skipped because a previous probe failed. |
| SN-DISC-3888 | Discovery ECC Queue is missing or empty. |
| SN-DISC-6004 | The target's SSL certificate isn't trusted. Note: Requires Discovery Admin Workspace v1.20.0. |
[ ]

{#disco-start-issue-resolve__table_tjr_3qt_fkc}

## Verify connectivity and credentials {#disco-start-issue-resolve__section_h33_pqt_fkc}

If Discovery still fails after you follow the remediation steps for a refined code, verify connectivity and credentials.

Confirm that the MID Server can reach the target on the ports that the protocol requires, and that no firewall blocks that path. For Windows targets, confirm that inbound traffic is enabled on the SMB port 445.

Confirm that the account Discovery uses has the rights on the target that the protocol requires. For Windows targets, confirm that the account can create and read files in the administrative share used during classification.

## Check host configuration {#disco-start-issue-resolve__section_pmk_ngg_fkc}

The following conditions don't produce a refined code. If the earlier refined codes don't resolve the failure, confirm each one manually.

PowerShell execution policy

:   The execution policy on the target host must allow Discovery to run PowerShell commands, including any policy applied through Group Policy. If a restrictive policy is blocking scripts, update the policy or add an exemption for Discovery.

Endpoint security

:   Confirm that endpoint protection software on the target isn't blocking the Discovery PowerShell script. If script control is enabled, add an exclusion for the Discovery script and add the ServiceNow publisher to the trusted publisher list.

## Legacy Diagnostics experience {#disco-start-issue-resolve__section_z2w_mbf_fkc}

The refined codes and AI Insights described here require the Error Framework. If your instance runs on an earlier version of Discovery Admin Workspace, the Diagnostics page shows the legacy experience instead. In that case, review the Diagnostics tab to review Discovery errors by error code and severity, then
apply the same environmental checks.
**Related concepts**   

* [Error Framework in Discovery Admin Workspace](https://www.servicenow.com/docs/Y_uGbggQxWtU3xzgDiJ5Og "Discovery Admin Workspace uses the Error Framework to surface actionable Discovery errors. You can review errors, understand their causes, and take steps to resolve them directly from the Diagnostics page.")
* [Discovery Admin Workspace Error Details](https://www.servicenow.com/docs/ZtZ8SsT1zyvfWTjTd0RxPQ "The Error Details page displays the root cause and remediation steps for a specific Discovery error, along with the list of individual error instances associated with that error.")

*[\>]: and then