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 - Active Connections probe returns error: Exception calling ".ctor" with "2" argument(s): "Cannot process argument because the value of argument "userName" is not valid. - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Windows - Active Connections probe returns error: Exception calling ".ctor" with "2" argument(s): "Cannot process argument because the value of argument "userName" is not valid.
KB0753501

Windows - Active Connections probe returns error: Exception calling ".ctor" with "2" argument(s): "Cannot process argument because the value of argument "userName" is not valid.


2021 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms

Windows - Active Connections probe returns error: Exception calling ".ctor" with "2" argument(s): "Cannot process argument because the value of argument "userName" is not valid.

 

Release

Post Madrid

 

Cause

This issue normally happens when remoteExecution is on for "Windows - Active Connections" probe, and 

MID Server parameter mid.powershell.use_credentials is set to false.

 

 

Resolution

Either do:
navigate to Discovery Definition > Probes > Windows - Active Connections > uncheck "Execute script remotely".

or:
navigate to MID Server > Servers > open record "DPWDEV", check property: mid.powershell.use_credentials, either delete this property, or set this to true

 


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.