- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 01:20 AM
While Discovering windows device we got error on SQL DB
Executing WMI query on host: ip address x.x.x.x with namespace: root/Microsoft/SqlServer and query: SELECT Name FROM __NAMESPACE
Error during execution of Windows command: executeQuery -Namespace root/Microsoft/SqlServer -Query "SELECT Name FROM __NAMESPACE" due to com.snc.automation_common.integration.exceptions.InvalidCommandException: executeQuery : Could not get query SELECT Name FROM __NAMESPACE on namespace=root/Microsoft/SqlServer through the remote session. Original Exception: Invalid namespace "root/Microsoft/SqlServer" At line:1 char:5
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 11:30 PM
Hello, You need to contact the Windows team to grant access to all communication paths or the highest path for discovering the SQL database, as indicated in the error message.
Example : The paths are as follows: (ComputerManagement 12, ComputerManagement 13, ComputerManagement 14, ComputerManagement 15, ComputerManagement 16).
The discovery process selects the most recent communication path, which in this case is ComputerManagement 16.
Please note: The pattern configuration is set to select the latest path available.
Additionally, for a permanent solution, ServiceNow has created a PRB record and plans to address this issue in the August patch. Issue: Instead of selecting the latest path, it should permit any of the available paths for discovering SQL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 11:30 PM
Hello, You need to contact the Windows team to grant access to all communication paths or the highest path for discovering the SQL database, as indicated in the error message.
Example : The paths are as follows: (ComputerManagement 12, ComputerManagement 13, ComputerManagement 14, ComputerManagement 15, ComputerManagement 16).
The discovery process selects the most recent communication path, which in this case is ComputerManagement 16.
Please note: The pattern configuration is set to select the latest path available.
Additionally, for a permanent solution, ServiceNow has created a PRB record and plans to address this issue in the August patch. Issue: Instead of selecting the latest path, it should permit any of the available paths for discovering SQL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2025 09:37 AM
Hi Sukran,
I wanted to confirm whether you were referring to the Yokohama patch or the Discovery Pattern-related one. This will help us ensure we're aligned on the next steps and timelines.
Please let me know when you get a chance.
Thanks again!