• A CI is created with the name "empty"
• The sys_id of the CI is "undefined"

This is caused when you are trying Abort insertion of a CI based on some conditions. This will some times result on the CI record created with the name "empty" and sys_id "undefined".

If there is a before insert business to abort the insertion on cmdb table, there is a good chance to run into this issue.

You will see the following message the application node logs:

Operation against file 'cmdb_ci_win_server' was aborted by Business Rule.

Disable the business rule or modify its logic so that you will not run into this issue.