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.
Orchestration Query AD Error - Unable to find any validated MID Server based on status (degraded), and application: Orchestration, and IP Range - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Orchestration Query AD Error - Unable to find any validated MID Server based on status (degraded), and application: Orchestration, and IP Range
KB0726923

Orchestration Query AD Error - Unable to find any validated MID Server based on status (degraded), and application: Orchestration, and IP Range


3841 Views Last updated : Feb 17, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms


Unable to query Microsoft Windows Active Directory when running "Query AD" workflow activity. The exact is shown below:

Fault Description:

com.snc.automation_common.integration.exceptions.NoSuitable 

Unable to find any validated MID Server based on status (degraded), and application: Orchestration, and IP Range

Cause


MID Server does not have an IP Range and does not have PowerShell capability set.

Resolution


1. Go to https://YOUR_INSTANCE.service-now.com/ecc_agent_list.do

2. Find the MID Server that your workflow activity is using and open the record.

3. Find the related list named "IP Ranges"

 

4. Click "Edit" and double click "ALL" or an IP range on the left that meets the criteria of your workflow.

This will move "ALL" or your range from the left to the right of the slush bucket. Click "Save".

 

5. Run the workflow again successfully.

Note:

If above is not working, and target is FQDN instead of IP Address, then check Orchestration > MID Server Configuration > MID Server Properties, make sure "Default MID Server to use for Orchestration Activities" field is populated with valid MID server name.

Orchestration is relying on default MID server that's set in "Orchestration MID Server Properties" to resolve target FQDN.

Alternatively you may create a cmdb_ci_dns_name entry for the target FQDN and manually add IP address.

 


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.