Payload processing fails for discovery of windows CI

[Manasi Marathe]

While trying to run horizontal discovery of a windows CI, as checked in logs, discovery is getting failed at stage "Check For Output Payload Errors"

As per the error message operation is getting aborted due to Business Rule. However same business rule exists in different environment where discovery runs without any error.

ERROR

Identifier: Identification CI Errors:
Update failed with error: Operation against file 'cmdb_ci_win_server' was aborted by Business Rulexxxxx

Kindly help to troubleshoot the discovery of this CI

[Niklas Peterson]

Hi,

To start with, is this a custom or ootb BR? What does it do?

Regards,
Niklas

[Manasi Marathe]

Hi Niklas,

It is a custom BR. It restricts creation of CI with duplicate Name. It will abort the process if CI with same name is found already existing in the cmdb_ci table. However, as checked there is no other CI with same name, discovery should ideally update the already existing CI but the BR is aborting this update.

[sry]

Hi Manasi, i am having the same error. we have a "Before update" business rule that records CI field changes into a custom table. could you please let me know whether you are able to resolve this issue and how?

Thanks,

Sry

[Manasi Marathe]

Hi Sry,

We figured that the issue was due to manual updates on the name of the CI. The 'sys_object_source' table captures identifier entry against a CI for IRE, this table behaves as cache during identification. The identifier entry in the table is only updated by discovery, integration source etc. Since manual update was not changing the identifier entry in this table, incorrect CI was being picked for update during discovery. We fixed this by creating another BR which updated the the identifier entry in sys_object_source table whenever name was manually updated for a CI.

Regards,

Manasi