Payload Processing errors in Discovery log

Robert T · ‎04-07-2021

Hello,

I'm reasonably new to ServiceNow altogether and am playing catch-up on our Discovery progress. Apologies beforehand for any redundancies or obvious questions.

We have several assets where Discovery seems to run smoothly until a "Payload Processing" step. Error text at this step vary, and information I've found out in the community with the messaging I'm getting has not yet been applicable.

Here is the information on 3 Windows devices that are throwing similar error messaging at this Payload Processing step.

In the Devices tab, each looks like this:

Windows Server

Device

2

Classified

2021-04-07 09:37:45

discovery_mid

Identifying

Windows Server

Device

2

Classified

2021-04-07 09:37:45

discovery_mid

Identifying

Windows Server

Device

2

Classified

2021-04-07 09:37:45

discovery_mid

Identifying

In the Discovery Log, each looks like this:

2021-04-07 09:38:55

Error

Failed Exploring CI Pattern, Pattern name: Windows OS - Servers, To Check Pattern Log Press here

(empty)

DiscoverySensor

2021-04-07 09:38:55

Error

Failed Exploring CI Pattern, Pattern name: Windows OS - Servers, To Check Pattern Log Press here

(empty)

DiscoverySensor

2021-04-07 09:38:55

Error

Failed Exploring CI Pattern, Pattern name: Windows OS - Servers, To Check Pattern Log Press here

(empty)

DiscoverySensor

And in the Pattern Log, each is stuck on the same step with equivalent messaging to this:

Check For Output Payload Errors

2021-04-07 07:38:55: Identification CI Errors: Insertion failed with error Operation against file 'cmdb_ci_disk' was aborted by Business Rule 'Check for duplicate serials^9b79b1f61b1f6c100c0877be034bcb'. Business Rule Stack:Check for duplicate serials,Insertion failed with error Operation against file 'cmdb_ci_disk' was aborted by Business Rule 'Check for duplicate serials^1b79f1f61b1f6c100c0877be034bcb'. Business Rule Stack:Check for duplicate serials,Insertion failed with error Operation against file 'cmdb_ci_disk' was aborted by Business Rule 'Check for duplicate serials^1779f1f61b1f6c100c0877be034bcb'. Business Rule Stack:Check for duplicate serials Identification Relation Errors: Insertion failed with error,Insertion failed with error,Insertion failed with error,Insertion failed with error,Insertion failed with error

2021-04-07 07:38:55: Identifier: Identification CI Errors: Insertion failed with error Operation against file 'cmdb_ci_disk' was aborted by Business Rule 'Check for duplicate serials^9b79b1f61b1f6c100c0877be034bcb'. Business Rule Stack:Check for duplicate serials,Insertion failed with error Operation against file 'cmdb_ci_disk' was aborted by Business Rule 'Check for duplicate serials^1b79f1f61b1f6c100c0877be034bcb'. Business Rule Stack:Check for duplicate serials,Insertion failed with error Operation against file 'cmdb_ci_disk' was aborted by Business Rule 'Check for duplicate serials^1779f1f61b1f6c100c0877be034bcb'. Business Rule Stack:Check for duplicate serials Identification Relation Errors: Insertion failed with error,Insertion failed with error,Insertion failed with error,Insertion failed with error,Insertion failed with error

I'm not getting consistent responses from the HI ticket I've opened on this, and would value any feedback/suggestions from this group. Thank you!
--Robert

David104 · ‎04-07-2021

Apologies in advance if you have already covered off what I'm talking about, but given that you are new to ServiceNow and Discovery, best to start with the simple answer and work from there.

Is 'Check for duplicate serials' a custom business rule? I do not see that rule in any of my instances. The IRE should take care of preventing duplicate records, so it would be worth looking at whether that particular business rule can be de-activated. I'd imagine that it's configured on something like cmdb_ci table which is why you are also seeing it on some Netscalers also.

If the discovery runs successfully with the business rule de-activated, it at least gives you somewhere to start looking deeper

View solution in original post

Robert T · ‎04-08-2021

The Netscalers are coming back. They are creating duplicates. I think the ones manually created in 2013 are on a custom table that has fields that Discovery can't populate. I would guess I can create a custom mapping to merge to this custom table, but it is probably better to go the other route, and get necessary manual data into the Discovery-created CI's.

Peter Groft · ‎08-04-2022

Click VPN, and click the configure icon next to the appropriate VPN SA name.
On the Proposals tab, make sure the IKE (phase 1) Proposal and IPsec (phase 2) proposal is identical to the remote firewall. Make sure the Perfect Forward Secrecy settings match on the local and remote firewall.

Regards,
Peter