Get-WmiObject : Could not get objects from namespace root\default. Access denied.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2017 12:26 PM
Got a new error today while running discovery which I couldn't find on the community or on wiki.
Get-WmiObject : Could not get objects from namespace root\default. Access deniedAt C:\Users\test\Downloads\mid.jakarta-05-03-2017__patch2-07-25-2017_08-11-2017_0919.windows.x86-64\agent\scripts\PowerShell\WMIFetch.psm1:363 char:24+ $reg = gwmi <<<< -list -computer $computer -credential $cred -namespace root\default | where-object {$_.Name -eq "StdRegProv"}+ CategoryInfo : ObjectNotFound: (:) [Get-WmiObject], ManagementException+ FullyQualifiedErrorId : INVALID_NAMESPACE_IDENTIFIER,Microsoft.PowerShell.Commands.GetWmiObjectCommandYou cannot call a method on a null-valued expression.
NOTE:
1. Instance version: jakarta-05-03-2017__patch2-07-25-2017_08-11-2017_0919
2. Powershell v2 is installed
3. Credentials used has local admin rights on the machine.
4. MID Server scripts/folder are not read-only.
5. This happens when I try to discover a remote machine, doesn't happen when I scan MID server itself.
Please advise?
Thanks!
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-26-2017 12:43 AM
Hi Iamer,
Try giving specific credentials on MID Server Service instead of Local Admin account.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-04-2017 03:05 PM
Double check your credential.. reads as if you dont have all the permissions on those name spaces as expected
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-05-2017 08:22 AM
Hi Lamer,
Look at this Known Problem PRB752896. I may help.
Also If it is Jakarta Version Check whether all the requirements in this document are met.
Thanks,
Niranjan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-13-2017 01:02 AM
Have you been able to resolve this issue? I get the same error for one of the servers.
Blog: https://sys.properties | Telegram: https://t.me/sys_properties | LinkedIn: https://www.linkedin.com/in/slava-savitsky/