CMDB identification error?

[DanLevin]

Greetings,

I am working on setting up Discovery as a proof of concept in our environment, which is domain separated.

I have configured the MIDServer, which is up and validated in my instance. I am now encountering an issue when I attempt to have the MIDServer Discover itself. We do not presently have a CI for this device in our CMDB, so I would expect that one would be created.

When Discovery attempts to Identify the single IP of the MIDServer, the log displays a Warning: "CMDB Identification Error: INVALID_INPUT_DATA: Invalid data source exist in payload".

Any suggestions for "next steps" from here would be very much appreciated. I've poked through the ECC Queue without any luck.

Thanks!

[DanLevin]

Welp, I found an answer to my own question. Being a domain separated environment was the culprit.

To fix the issue, I had to navigate to the Dictionary Entry for the "discovery_source" field. Since this is a choice list, I had to set the Domain of the "ServiceNow" choice to align to our "Top" level domain, rather than the "global" Domain as it was configured by default. Seems that the system felt that it was unable to determine a proper data source for the Discovery activity as the "ServiceNow" choice wasn't in the Domain it was expecting it to be in.

Odd, but I'll take it.

[crc2580]

I've also encountered this issue after we activated Service Mapping in our instance. Did you recently activate any plugins (besides Discovery)? Older instances use "Service-now" as the value and label while newer instances use "Servicenow". You can also look at 'glide.discovery.source_name' to choose what the system defaults to.