Azure Cloud Discovery Sensor error

motsuki17
Tera Guru

When trying to Test Account my Cloud Discovery Schedule, its showing this error:
(See attached image)

There was a hotfix for the script include DiscoverySensor (778011130a0a0b2500c4595ad1d1d768) "System Upgrades: glide-vancouver-07-06-2023__patch7-hotfix2a-04-03-2024_04-09-2024_1017.zip" but it did not fix it. I also tried to repair the Discovery and Service Mapping Patterns v1.12.0 plugin but nothing changed. How to fix this?

Also a warning is also logged in the Discovery Status along with this sensor error:
Warning | Script error in sensor: java.lang.NullPointerException

 

The ECC Queue queue input state is error, despite the status in the payload is SUCCEED.

1 ACCEPTED SOLUTION

motsuki17
Tera Guru

I resolved the issue on my own:
Just had to invalidate, then validate the MID Server, then Rekey again and it fixed.

View solution in original post

8 REPLIES 8

KaushalV
Kilo Contributor

I dont have much knowledge about this error but you can check for  the following maybe it'll help you out:

1. Check the system logs for any additional error messages or stack traces related to this issue. This can provide more context on what might be going wrong.

2. Ensure that your Cloud Discovery Schedule configuration is correct. Double-check settings such as credentials, endpoints, and schedule frequency to ensure they are set up properly.

3. If this issue started occurring after a recent change or update, review what changes were made and consider rolling back those changes if possible.

This error started to occur when I enabled the property glide.discovery.enable_adme, I also disabled it but the error remained. I do not know what is causing it.
The credentials are indeed correct before this error occurred and it validated with the green info message "The service account was successfully validated." . And it is still correct since the probe's payload XML status is SUCCEED.
Does the language matter? Apparently, the language of the cloud data such as Virtual Machine names is in Japanese. The MID Server is also a Virtual Machine in an Azure Cloud.

Pratiksha
Mega Sage
Mega Sage

Hi @motsuki17 

 

Check the video https://www.youtube.com/watch?v=R11fR2fo4Y8

 

 

Also, have tried to discover the data centers? 

Mark it Helpful and Accept Solution !! If this helps you to understand.

Checkout this five part series on managing @MicrosoftAzure Cloud using ServiceNow IT Workflows. Intro - 1:13 - https://youtu.be/2YCDVpEcBdw Cloud Discovery 7:00 - https://youtu.be/R11fR2fo4Y8 Event-based Discovery 5:58 - https://youtu.be/g6tzZSAy1Fk Tag-based Service Mapping 4:41 - ...

Thanks but I've already seen this video and done it before. My service account and service principal were validated by the Test Account button but when I enabled the property glide.discovery.enable_adme this error started to occur.
And yes I have tried to discover the data centers, it has data in the logs but I cannot select any datacenters since its empty.