Horizontal Discovery Sensor is missing in my new Vancouver PDI build

[Jimbo2]

Hi All,

In Probe "Horizontal Pattern" under "Sensor That Reacts to This Probe" tab, the "Horizontal Discovery Sensor" is missing. There is no "Horizontal Discovery Sensor" in discovery_sensor list - it is missing. 

I see this error on simply creating a schedule and attempting to discover a Windows Server

Discovery Log

Sensor error when processing Horizontal Pattern: No sensors defined

Ecc Queue

2023-10-17 05:04:42

mid.server.MIDServer

HorizontalDiscoveryProbe

Pattern Launcher: Windows OS - Servers

192.168.0.150

input

error

(empty)

I have installed and activated "Discovery and Service Mapping Patterns", version 1.8, etc,.. for my PDI, checked Plugin History and see no errors, yet missing is "Horizontal Discovery Sensor" in discovery_sensor list, there are probably others too.

I've searched this forum and seems many others have had the same/similar problem, but none are providing the fix, only logging a support ticket with ServiceNow. My problem is with my PDI, not any of our Prod and sub prod env.

Has anyone been able to resolve this, if so how? Frustrating to see a new build PDI is still failing with this same issue after so many version since I think Rome version had introduced this problem and is still present in Vancouver.

Thanks in advance..

Jimbo!!

[Jimbo2]

Here is an update - I fixed this but I shouldn't have to do this fix for a new clean build.

What I did was from another working instance (nonprod/dev env) where the sensor does exist, created an update set and added it to it. Then exported the update set to then upload and preview / commit it to the new PDI.

Ran discovery again and this time completed successfully - it's just so frustrating to think this is still a problem since a very old version of Servicenow.

2023-10-17 15:05:13

mid.server.MIDServer

HorizontalDiscoveryProbe

Pattern Launcher: Windows OS - Servers

192.168.0.150

input

processed

2023-10-17 15:05:13

[Alvaro Paronuzz]

I'm seeing the same issue in a Xanadu instance. Should I apply the same workaround?

[SagieR]

I have seen this issue as well on a customer instance.

You can apply the workaround but make sure you exported the sensor from the same instance's version, because if not it might cause an issue of fields that are not populating.

[BozhidarNizamov]

This seems to be a known issue with ServiceNow reported here https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0819305 

The steps to "Repair" the Pattern Designer plugin worked for me. The article states that you can't perform this and must open a ticket, but the option was available and I was able to click on Repair.