CI class not found: discovery target class does not exist in CMDB

Required CMDB CI class plugin is not activated, preventing the target class from being available in the system dictionary. (high likelihood)

Custom CI class was deleted or deactivated but discovery patterns still reference the missing class name. (high likelihood)

Discovery pattern or identifier rule contains incorrect class name mapping that doesn't match existing CMDB classes. (medium likelihood)

CMDB class hierarchy corruption or missing parent class relationships preventing proper class resolution. (medium likelihood)

Discovery payload contains malformed or invalid CI class names due to probe script errors or external data source issues. (low likelihood)

Step 1: Navigate to System Definition > Dictionary and search for the missing CI class name mentioned in the error to confirm if it exists in the system.

Step 2: Check System Definition > Plugins and verify that all required CMDB plugins are activated, particularly focusing on CI class plugins related to your discovery target.

Step 3: Review the Discovery Status record details and ECC Queue entries to identify the specific discovery pattern or probe causing the error.

Step 4: Navigate to Configuration > Discovery Definition and examine the CI Identifiers and Classification rules to verify correct class name mappings.

Step 5: If using custom CI classes, go to System Definition > Tables and ensure the target class table exists and extends from cmdb_ci or appropriate parent class.

Step 6: Check Discovery > Discovery Patterns for any hardcoded class references and update them to match existing CMDB classes.

Step 7: Re-run the discovery operation after making corrections and monitor the Discovery Status and System Log for resolution confirmation.

Step 8: If error persists, enable discovery debug logging at System Diagnostics > Debug > Debug Security to capture detailed class resolution information.