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

[Manasi Marathe]

Hi Niklas

This is a custom BR. It checks for uniqueness in the CI Name. It will abort the discovery process if a CI with same name exists in the database. As checked, there is only 1 CI with same name in the database, and discovery should update this record. This BR works fine in other lower environment for discovery of same CI.

[Niklas Peterson]

Hi,

Then it sounds like an issue with the idenfication. The IRE is not able to identify a CI to update, instead tries to insert a new one which is stopped by the BR. Use the same condition in the identification rules as you have in the BR and it should be fine.

Regards,
Niklas

[Manasi Marathe]

Hi Niklas,

Identification rules are same in lower environment and current environment. CI is getting correctly updated by discovery in the lower environment where the same BR is also active. Do let me know in case I can perform any troubleshooting steps.

Regards,

Manasi

[Niklas Peterson]

Hi,

Inactivate the BR to make sure that it is the cause of the issue. Then you will also see if you will get a duplicate without the BR. 

Regards,

Niklas

[Manasi Marathe]

Hi Niklas,

The CI in question was uploaded manually via transform map. We changed the name of the CI from lower case to upper case and the discovery was successful (with the BR still active).

However, in lower environment CI was present with name in lower case and even then discovery was successful without having to change to upper case. Any specific reason why this was observed in current environment only and not in lower environment?

Regards,

Manasi