Orchestration activity not receiving success or failure

[zwilliamstp13]

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!

[zwilliamstp13]

Thank you for the response,

I have both the default mid server set and the IP Range set, along with Powershell Capabilities. I am matching the IP Range IP to the one called via the Workflow Activity. The Default MID Server is set to the given mid server. If I try running the Update AD Object activity with only the IP range it requests a default MID Server. With these changes I still get the following error:

"The default MID Server(RTI_MIDServer_Dev1) is being used. For more control over which MID server executes commands against a particular target, configure IP Ranges and Capabilities for your MID Servers."

What could be be taking up the MID Server?

[killswitch1111]

Zach,

That doesn't look like an error, it just says it is using the default Mid Server which is ok.   Is the ECC Queue record still sitting in the output state?

-Chris

[zwilliamstp13]

Yes it is still in ready state and has not been processed.

[killswitch1111]

Zach,

Ok, I was about to work with my AD server anyway, gimme a few minutes to get it spun up and I will take a look.   Are you on Jakarta?

Chris

[zwilliamstp13]

Helsinki.