Identification Engine Payload Sanitization Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2023 02:24 AM - edited 03-20-2023 02:29 AM
Hello,
I'm facing a problem while discovering a Nutanix Prism,
It discovers the prism well, but the discovery does not succeed because of an error in the payload
I was wondering if anyone has already encountered a similar error
The error source is com.glide.ui.ServletErrorListener according to the logs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2024 01:00 AM
Hello,
Servicenow have never been able to solve this problem. As far as I'm concerned, the error message I was getting wasn't the real problem.
Try to retrieve the payload directly from here:
then simulate it on the identification simulation module :
you'll see more clearly what's going on.
In my case, it was a duplicated item in the payload that was preventing CI creation/update, so I had to add a deduplication step to the payload to solve the problem.
let me know what you find out, we'll have a look together if need be.
Good luck !
Best Regards,
L.O.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2024 10:10 PM
Hi @Sohail Khilji ,
Please check the identification rule for that class once, if CI already created please delete the CI and tried once again.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thanks
AJ
Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/
ServiceNow Community Rising Star 2024
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2024 10:27 PM
We have a subnet with veritas , we discoverd few and few are trowing the errror...
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2024 03:18 AM
Here is the SOLUTION :
It was because of device_id duplication for (Vertias storage) device.
They provided a update set to fix... that solved the issue...
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....