IRE error messages
Summarize
Summary of IRE error messages
The Identification and Reconciliation Engine (IRE) in ServiceNow generates various error messages during CI identification and reconciliation processes. These messages help diagnose issues related to payload processing, identification rules, duplicate records, relationships, and data source constraints. Error messages may appear in the Identification Logging pane and system logs, assisting administrators in troubleshooting and resolving data integrity challenges within the CMDB.
Show less
Key Errors and Their Resolutions
- IDENTIFICATIONRULEMISSING: Occurs when an identification rule for a specified class/table is missing or inactive. Resolution: Ensure an active identification rule exists for the affected class.
- MISSINGMATCHINGATTRIBUTES: Payload is missing required criterion attributes needed for identification. Resolution: Add the minimum required matching attributes to the payload for the CI class.
- NOCLASSNAMEFORINDEPENDENTCI: The class attribute is incorrectly used as a key field in an Independent Identity Rule. Resolution: Remove the class attribute from the CI identifier.
- IDENTIFICATIONRULEFORLOOKUPMISSING / IDENTIFICATIONRULEFORRELATEDITEMMISSING: Lookup or related rules are missing for referenced classes. Resolution: Add corresponding lookup or related rules in the CI Identifier configuration.
- NOLOOKUPRULESFORDEPENDENTCI: Lookup rules are not allowed on dependent identity rules. Resolution: Remove lookup entries from dependent CI identifiers.
- INVALIDINPUTDATA: Payload references invalid or non-existent sysids, invalid data sources, or undefined relationships. Resolution: Correct or remove invalid sysids, provide valid discoverysource values, and verify relationships exist in the cmdbreltype table.
- DUPLICATERELATIONSHIPTYPES / DUPLICATEPAYLOADRECORDS / MULTIPLEDUPLICATERECORDS: Duplicate records or relationships detected in payload or CMDB tables. Resolution: Remove duplicates to maintain data integrity.
- LOCKTIMEOUT: Failure to acquire a system lock during processing. Resolution: Increase the mutex expiration time via system properties.
- REQUIREDATTRIBUTEEMPTY: Mandatory fields missing in the payload. Resolution: Add required attribute values to the payload.
- MISSINGDEPENDENCY / METADATARULEMISSING: Missing containment/hosting rules or relations for dependent classes. Resolution: Add appropriate relations or metadata rules to the dependent classes.
- MULTIPLEDEPENDENCIES / QUALIFICATIONLOOP / TYPECONFLICTINQUALIFICATION: Issues with multiple or looping qualification chains and dependencies. Resolution: Remove duplicate or looping qualification chains to ensure clear identification paths.
- ABANDONED: Processing aborted due to errors in dependent payload items. Resolution: Resolve errors in the referenced dependent payload items first.
- JSON Parsing and API Errors: Errors during JSON payload parsing or recursive API calls. Resolution: Ensure payload JSON format is correct and avoid recursive Identification engine API calls.
- DUPLICATERELATEDPAYLOAD / DUPLICATELOOKUPPAYLOAD: Duplicate related or lookup items found in payload. Resolution: Remove duplicates from the payload.
- INSERTNOTALLOWEDFORSOURCE: CI insertions blocked for a data source by IRE data source rules. Resolution: Modify or delete the data source rule or wait for an authorized data source to insert the CI.
Practical Guidance for ServiceNow Customers
- Regularly verify that identification rules, lookup rules, and related rules are correctly configured and active for your CI classes.
- Ensure payloads conform to required attributes, valid sysids, and proper relationships to avoid processing errors.
- Monitor and resolve duplicate records and relationships promptly to maintain CMDB accuracy.
- Adjust system properties such as mutex expiration time if lock timeouts occur during identification processing.
- Address containment and hosting metadata rules to support dependent CI relationships effectively.
- Validate JSON payload syntax and avoid recursive API calls to prevent processing failures.
- Review IRE data source rules to control which data sources can insert or update specific CI classes.
By understanding and addressing these common IRE errors, ServiceNow customers can improve CMDB data quality, streamline identification processes, and maintain a reliable configuration management database.
The Identification and Reconciliation Engine (IRE) generates the following errors and messages. Depending on settings, these messages appear in the Identification Logging pane and in the system logs.
For information about CMDB Identification Payload error: "FAILED TRYING TO EXECUTE ON CONNECTION", see CMDB Identification Payload error - "Insertion failed with error Error during insert of cmdb_ci...", where node logs show "FAILED TRYING TO EXECUTE ON CONNECTION" "Duplicate entry 'XXX' for key 'XXX'" knowledge base article.
Error- IDENTIFICATION_RULE_MISSING
| Message | Description and Resolution |
|---|---|
| Identity Rule Missing for table [xyz] |
|
MISSING_MATCHING_ATTRIBUTES
| Message | Description and Resolution |
|---|---|
| In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [xyz]. Add these input values in payload item 'abc' |
|
Error- NO_CLASS_NAME_FOR_INDEPENDENT_CI
| Message | Description and Resolution |
|---|---|
| Cannot have 'sys_class_name' as a key field in an Independent Identity Rule on 'xyz' |
|
Error- IDENTIFICATION_RULE_FOR_LOOKUP_MISSING
| Message | Description and Resolution |
|---|---|
| Identity Rule for table [xyz] missing Lookup Rule for class [abc] |
For more information about this error message, see Identification error "Identity Rule for table [cmdb_ci_table_name] missing Lookup Rule for class [table_name]" [KB0786444]. |
Error- IDENTIFICATION_RULE_FOR_RELATED_ITEM_MISSING
| Message | Description and Resolution |
|---|---|
| Identity Rule for table [xyz] missing Related Rule for class [abc] |
|
Error- NO_LOOKUP_RULES_FOR_DEPENDENT_CI
| Message | Description and Resolution |
|---|---|
| Cannot have Lookup Rule for a Dependent Identity Rule on 'xyz' |
|
Error- INVALID_INPUT_DATA
| Message | Description and Resolution |
|---|---|
| Found invalid sys_id in payload. No record with sys_id [xyz] exist in table [abc] or is a duplicate record with [duplicate_of] field set to a main CI |
|
| In payload no data source exist. You need to provide choice value from choice field [discovery_source] in table [cmdb_ci] |
|
| In payload invalid data source [xyz] exist. You need to provide a valid choice value from field [discovery_source] in table [cmdb_ci] |
|
| No such relationship with name [xyz] exist in table [cmdb_rel_type]. If out-of-box relationship for [xyz] has been removed or renamed, it should be restored |
|
| Payload relations 'xyz' has invalid parent record index: [0] |
|
| Payload relations 'xyz' has invalid child record index: [0] |
|
Error- DUPLICATE_RELATIONSHIP_TYPES
| Message | Description and Resolution |
|---|---|
| Duplicate relationship type records exists with name [xyz] in table [cmdb_rel_type] having sys_ids: [abc] |
|
Error- DUPLICATE_PAYLOAD_RECORDS
| Message | Description and Resolution |
|---|---|
| Found duplicate items in the payload (index 0 and 1), using className [xyz] and fields [abc]. Remove duplicate items from payload |
|
Error- LOCK_TIMEOUT
| Message | Description and Resolution |
|---|---|
| Failed to acquire synchronization lock for xyz |
|
Error- MULTIPLE_DUPLICATE_RECORDS
| Message | Description and Resolution |
|---|---|
| Found duplicate records in table [xyz] using fields [abc] |
|
Error- REQUIRED_ATTRIBUTE_EMPTY
| Message | Description and Resolution |
|---|---|
| Missing mandatory field [xyz] in table [abc]. Add input value for mandatory field in payload |
|
Error- MISSING_DEPENDENCY
| Message | Description and Resolution |
|---|---|
| In payload no relations defined for dependent class [xyz] that matches any containment/hosting rules: [abc]. Add appropriate relations in payload for 'def' |
|
Error- METADATA_RULE_MISSING
| Message | Description and Resolution |
|---|---|
| No containment or hosting rules defined for dependent class [xyz]. Add containment/hosting rules for ‘abc' |
|
Error- MULTIPLE_DEPENDENCIES
| Message | Description and Resolution |
|---|---|
| Found multiple dependent relation items [xyz] and [abc] in payload |
|
| Multiple paths leading to the same destination: xyz -> abc |
|
Error- ABANDONED
| Message | Description and Resolution |
|---|---|
| Abandoning processing payload item 'xyz', since its depends on payload item 'abc' has errors |
|
| Can't find matched record with sys_id [xyz] in table [abc] |
|
| Identification engine API got called recursively, aborting... |
|
| Detected error while processing payload from xyz |
|
| While processing relations encountered errors in payload item: xyz |
|
| Error occurred during parsing input json payload: xyz |
|
Error- MULTI_MATCH
| Message | Description and Resolution |
|---|---|
| Duplicate dependent records found having relationship [xyz] with same CI (className:[abc], sysId:[def]) |
|
| Found multiple relations between payload items: 'xyz' and 'abc' |
|
| Found duplicate records in lookup table [xyz] using fields [abc] and reference field [def] |
|
Error- QUALIFICATION_LOOP
| Message | Description and Resolution |
|---|---|
| Qualification chain has loop that contains relation 'xyz' |
|
Error- TYPE_CONFLICT_IN_QUALIFICATION
| Message | Description and Resolution |
|---|---|
| Invalid payload, qualification chain has multiple possible paths for payload items: 'xyz' and 'abc' |
|
Error- RECLASSIFICATION_NOT_ALLOWED
| Message | Description and Resolution |
|---|---|
| CI Reclassification not allowed from class: [xyz] to [abc] |
|
Error- DUPLICATE_RELATED_PAYLOAD
| Message | Description and Resolution |
|---|---|
| Found duplicate Related items (0 and 1) in the payload index 1 using fields xyz |
|
Error- DUPLICATE_LOOKUP_PAYLOAD
| Message | Description and Resolution |
|---|---|
| Found duplicate Lookup items (0 and 1) in the payload index 1 using fields xyz |
|
INSERT_NOT_ALLOWED_FOR_SOURCE
| Message | Description and Resolution |
|---|---|
| Insert into [xyz] is blocked for data source [abc] by IRE data source rule |
|