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.
Troubleshooting Power-shell Orchestration Workflow not working with new MID Server - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Troubleshooting Power-shell Orchestration Workflow not working with new MID Server
KB0748533

Troubleshooting Power-shell Orchestration Workflow not working with new MID Server


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

Issue

Description

If you are struggling with the setup of a new MID Server in that all integrations work fine except for orchestration workflow when pointing to a Power-shell activity then this may be a credential issue, configuration of the clients environment or even a ServiceNow issue.

Procedure

Steps to reproduce: 
1. Open Workflow Editor 
2. Open workflow 
3. Open the first "Run Powershell" activitity in workflow. 
4. Configure "Hostname" to new MID-server. 
5. Impersonate User
6. Go to service portal
7. Open item
8. Use default values and submit request. 
9. Check in RITM that the orchestrations workflow fails. 

To troubleshoot:

Check if there are any credentials set up for the MID Server, otherwise, the MID Server is totally dependant on the Service credential on the MID Server service (right-click the service and select the Log On tab); you can also assign a tag to the Windows credential.

If you suspect this is more to do with the configuration of environment, when testing your scripts, you can run the same script from within Power-shell

  • if it works in Power-shell and your workflow fails, then this will be a ServiceNow issue and you should log a call with Support
  • if it fails in Power-shell then this is an environment issue

 


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.