Orchestration activity not receiving success or failure

zwilliamstp13 · ‎10-10-2017

I am working on a simple Orchestration project that lets a user choose their Charge Code from a ServiceNow table and it will update their AD Profile with that information. This is the companies first Orchestration project. They have set up the MID Server within the network domain of the AD, and set up a Windows Credential with write rights on AD. MID Server is connecting, and has mid.use_powershell and mid.powershell.use_credentials properties set to true. The MID Server has the given Credentials set as the default credentials.

When running the below activity we are not receiving a Success or Failure message, simply nothing happens and the activity remains active indefinitely while it waits for a response. Are there usual causes for this type of issue?

Thank you for the help!

killswitch1111 · ‎10-10-2017

Zach,

There are a couple places you are going to want to look to see what is going on. The first and primary is the ECC Queue. (ecc_queue.list in the navigator). Run your workflow with your activity, and then look into the ECC Queue and you should see an "output" record with the name of "Powershell." Make sure that it says "processing" as the state. If it is sitting at "ready" then that means the record is not getting picked up by the mid server. If this is the case, you can check the Mid Server capabilities, make sure the Mid Server is Up, and the Mid Server has been Validated. You can also check the ServiceNow System Logs, which will probably show something along the lines of "No default Mid Server found".

IF the Mid Server is picking up the queue record, then it should respond with an "input" queue record. You can check that record to see if an error is thrown in the result. Otherwise, you may need to open up the Mid Server logs to review. If you don't have physical access to the Mid Server (or virtual access) you can go to the Mid Server in ServiceNow and click on the UI Action Related Link "Grab mid logs" and that will pickup the mid logs and return them to the instance so you can take a look.

If all this doesn't work, let me know. If you can, post that information or screen shots of the ECC queue which will help debug.

Thanks,

Chris

zwilliamstp13 · ‎10-10-2017

Thank you for the response I will review those items and see what comes up!

zwilliamstp13 · ‎10-10-2017

I have the following messages from the ECC Queue and the Log:

There is no IP Range given, would this be necessary? I had thought it was not.

killswitch1111 · ‎10-10-2017

Zach,

You need the IP Range in order for Orchestration to select the correct server.

You need either the IP Range or to set the Default Mid Server:

Here is the documentation on that issue:

https://docs.servicenow.com/bundle/helsinki-it-operations-management/page/product/mid-server/task/t_...

Hope this helps.

Chris