After Washington DC upgrade Discovery does not update Server CIs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2024 05:12 AM
So we upgraded to Washington DC and after that most of the patterns quit working. The Windows OS pattern is failing with "
Error during execution of Windows command: executeQuery -Namespace Root\MSCluster -Query "SELECT Name,Status,Description,Caption FROM MSCluster_Cluster" due to com.snc.automation_common.integration.exceptions.InvalidCommandException: executeQuery : Could not get query SELECT Name,Status,Description,Caption FROM MSCluster_Cluster on namespace=Root\MSCluster. Original Exception: Invalid namespace"
and
There is problem to build the Sanitized Payload: Dedup process failed. Unrelated errors were found in the payload: [NO_LOOKUP_RULES_FOR_DEPENDENT_CI: Cannot have Lookup Rule for a Dependent Identity Rule on 'cmdb_ci_linux_server', ABANDONED: Abandoned due to too many errors, ABANDONED: Abandoned due to too many errors, ABANDONED: Abandoned due to too many errors, ABANDONED: Abandoned due to too many errors, ABANDONED: Abandoned due to too many errors, ABANDONED:
And Linux is
There is problem to build the Sanitized Payload: Dedup process failed. Unrelated errors were found in the payload: [NO_LOOKUP_RULES_FOR_DEPENDENT_CI: Cannot have Lookup Rule for a Dependent Identity Rule on 'cmdb_ci_linux_server', ABANDONED: Abandoned due to too many errors, ABANDONED: Abandoned due to too many errors, ABANDONED: Abandoned due to too many errors, ABANDONED: Abandoned due to too many errors, ABANDONED: Abandoned due to too many errors, ABANDONED:
Any ideas on where to start?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2024 12:03 PM
Having same issue, on IIS pattern, did you find any solution to it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2024 11:28 AM
We just Upgraded to Washington this past weekend, I have checked probes, patterns, credentials, sensors... still discovery is taking average 45 minutes to discover 1 server... I did notice that the shazzam probe does say (Active, Now Classifying) even after the probe is complete, I wonder if there is a step problem within the probe/sensor.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2025 07:15 AM
Any chance you found a solution for this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2025 07:10 AM
@amcd3254 Yes we did find out that there was a change within "Scripted REST External Default" an ACL for Washington that caused an auto deny for anything outside of the platform. We had to add the role of "mid_server" to this ACL and that fixed our issue.