Windows discovery error

Pranita2 · ‎04-23-2020

Hi,

While discovering few windows servers, they are failing with following errors:

launchWMI : Access is denied. (Exception from HRESULT: 0x80070005(E_ACCESSDENIED))At D:\SIAM City Thailand DC MID ServerAgent\scripts\PowerShell\WinRMAPI\ExecuteRemote\ExecuteRemote.psm

Credentials are getting validated successfully.

Can anyone help in resolving this issue?

Thanks,

Pranita

Ashutosh Munot1 · ‎04-24-2020

HI,

Check this things:

https://hi.service-now.com/kb_view.do?sys_kb_id=74e16b16db6ebb006064eeb5ca9619dd&sysparm_rank=1&sysp...

https://docs.servicenow.com/bundle/madrid-it-operations-management/page/product/discovery/reference/...

This is important:

https://hi.service-now.com/kb_view.do?sys_kb_id=16eb857edbde9bc04816f3231f9619a5&sysparm_rank=6&sysp...

Here from MID Server you can trigger few queries to check the connection:

Common Exploration Phase Errors

Below is a list of common exploration phase issues as well as suggestions on how to resolve them.

WMI and Powershell
- The impersonation of the user failed.
- Ensure that the domain is specified, along with the username in the credentials.

Connection failed to WMI service and other common Windows (WMI/Powershell) error messages:

Error: The remote server machine does not exist or is unavailable

Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
- WMI, does the mid server service account have access to the targeted machine? What if a domain admin account is used as the mid server service account?
- From the command prompt on the mid server host, execute for runner_type=WMI
  
  wmic /node:"<target>" /user:"<user>" /password:"<password>" path win32_operatingsystem
- From within a Powershell console on the mid server host, execute for runner_type=Powershell
  
  gwmi win32_operatingsystem -computer <ip> -credential '<username>'
- It is possible that probe is timing out while waiting for a response. If the command is successful from a command prompt, try extending the wmi_timeout value of the probe.

Thanks,
Ashutosh

View solution in original post

Namrata Khabale · ‎04-23-2020

Hey Pranita,

Refer the Link it might help you:

https://docs.servicenow.com/bundle/orlando-it-operations-management/page/product/discovery/concept/c...

Mark Correct if it solves your issue and also mark Helpful if you find response Worthy!

Best Regards,

Namrata.

Onkar Pandav · ‎04-23-2020

Hi,

In addition to Namrata's answer, please check below links also.

Troubleshooting the Exploration Phase in Discovery

WMI Troubleshooting

Please let me know if it is useful.

Ashutosh Munot1 · ‎04-23-2020

Hi, I have created article like lessons learnt in discovery. Please check those. I will put my thoughts here 1) Use domain\username in credentials. 2) Check if that user has proper rights to machine. 3) Check proper access to this path listed in error. 4) try to do enterPS session from mid server to this machine. Thanks, Ashutosh

Pranita2 · ‎04-23-2020

Hi Ashutosh,

Thank you for your response!!

Can you please let me know where can i find the above mentioned article.

Also, i was facing this issue earlier in Madrid version which got resolved by exporting an XML upgrade set.

While, in one of the service now knowledge article it was mentioned that the above issue was fixed in Orlando release.

Can you please elaborate what exactly is this issue? As i have mentioned the credentials in the below format

Domain\Username

Many thanks,

Pranita