Random WMI error "No such interface supported" getting Windows Server's Serial Number.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2020 01:41 PM
Hi,
This is a very though one to reproduce, so I'm not sure opening a case will be worth.
I'm getting random errors getting Windows Server's serial Numbers which is causing duplicate CIs.
For example, when running the Horizontal Discovery pattern step "Serial number from Win32_BIOS" (from"Windows OS - Server" pattern) the discovery log shows error "No such interface supported".
Then trying to run the same step on a debug session and I got "Invalid namespace" error running the step the first time. Trying to re-run the exact same step after a few seconds worked fine.
What could cause the WMI query to randomly fail?
Thanks in advance.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2020 01:45 PM
what version of win server?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2020 01:48 PM
also do you use WMI collector at all? Maybe only on some mid servers?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2020 01:57 PM
The server I was using to reproduce the issue is a Windows 2016 Standard.
We don't have WMI collectors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2020 02:21 PM
can you run the query on the server itself without that error?
it could be a permission issue allowing the run of the command at the first attempt, by the time you try again the security handshake happened and you're good to go. What kind of account is used to run the query? Domain?