There is problem to build the Sanitized Payload: Identification Engine errors

BK14
Mega Guru

Hello experts,

 

I recently started getting the error below when discovering some (not all) Windows servers.

there is no duplicates in cmdb_rel_type table. 

Would you please guide me to fix this?

 

2025-01-08 10:13:46: : There is problem to build the Sanitized Payload: Identification Engine errors: See [code]<a href="/nav_to.do?uri=/$identificationLogs%3Fcontext_id%3D27ef44a0834712d056bea6e0deaad3de" target="_blank"><u>Identification Logs</u></a>[/code] for more info.


Proposed solution:
In case the discovered CI is included CI (such as Tomcat WAR) check if there are multiple records with name 'Contains::Contained by' in cmdb_rel_type table.
Found multiple dependent relation items [{"parent":2,"child":0,"type":"Contains::Contained by","sys_rel_source_info":{}}] and [{"parent":1,"child":0,"type":"Contains::Contained by","sys_rel_source_info":{}}] in payload

 

1 ACCEPTED SOLUTION

carlos-schiavi
Tera Expert

I think this article can help you...

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1703757

The fix should be available in Visibility Content plugin update coming this February. For now, you can attempt the suggested steps below to resolve the issue:

[--] Navigate to cmdb_identifier_entry.LIST
[--] Update the identifier for File system - cmdb_ci_file_system

Add criterion attribute as name, volume ID in identifier entry.

 

 

 

View solution in original post

2 REPLIES 2

carlos-schiavi
Tera Expert

I think this article can help you...

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1703757

The fix should be available in Visibility Content plugin update coming this February. For now, you can attempt the suggested steps below to resolve the issue:

[--] Navigate to cmdb_identifier_entry.LIST
[--] Update the identifier for File system - cmdb_ci_file_system

Add criterion attribute as name, volume ID in identifier entry.

 

 

 

Thank you Carlos! 😀

I had the exact same issue. This fixed it. The identifier existed from before but only with critterion attribute = name, not name and volume_id.

It was a handful of Windows Servers which failed due to this.

Kind Regards,

Robin