Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Windows process detection fails with error "Command NeebulaWMI.PutFileUsingAdminShare failed. System.Exception: Failed to create connection. Unable to connect to." - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Windows process detection fails with error "Command NeebulaWMI.PutFileUsingAdminShare failed. System.Exception: Failed to create connection. Unable to connect to."
KB0786156

Windows process detection fails with error "Command NeebulaWMI.PutFileUsingAdminShare failed. System.Exception: Failed to create connection. Unable to connect to."


1098 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Windows process detection fails with error:

Put file on Windows host <ip_address> failed. filePath: 64/msvcp100.dll error: Unable to execute command. None of the command implementations was successful.
Command NeebulaWMI.PutFileUsingAdminShare failed. System.Exception: Failed to create connection. Unable to connect to \\<ip_address>\c$. Error=53

Release

All currently supported releases.

Cause

The process detection in windows discovery, depending on settings, will use the WMI collector. The WMI collector will attempt to collect the results from either the C$ or via sending the result file back to the MID server via HTTP.

Resolution

If WinRM is available on the target, set the following MID Server properties:

  • mid.sa.use_powershell = true
  • mid.sa.prefer_powershell = true
  • mid.sa.prefer_powershell_fallback = true


If both mid.sa.use_powershell and mid.sa.prefer_powershell are true, WMIProvider will try Powershell first. If powershell command returns nothing it will try to fall back to WMI Collector, if mid.sa.prefer_powershell_fallback is true. When it tries Powershell it will check if WinRM is available on the target and run the command via Powershell remoting. If WinRM is not availble, it will try WMI and will still need the admin share to copy the script to run on the target. Thus, WinRM needs to be setup in order to use Powershell without the admin share.

Related Links

  • Setup a MID Server to use Powershell

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.