workflow using incorrent MID server

[dalehouston]

I have an application that uses a custom PowerShell activity.   In the original test instance with a single MID server it worked just fine.

When brought into the secondary test instance where there was a preexisting MID server I ran into some issues - specifically that the workflow would always attempt to use the MID server that was already there.

I verified that desired MID server config   has the PowerShell capability set

I verified that the custom PowerShellobject is using desired MID server as the "target host"

We even deleted the the preexisting MID server and the workflow still attempted to contact the wrong MID server.

I'm assuming there are setting outside of the application objects that need to be looked at or checked - any thoughts on what those might be or what the cause of the attempted connection to the wrong MID server might be?

[mattg_snow]

Dale,

I ran into a similar problem and the fix was to ensure that the IP ranges were setup to select the right MID server, unfortunately you cannot rely on capabilities alone.

Are the IP ranges set for the different MIDs?

-Matt

[dalehouston]

Thanks, Matt!   I don't have any IP ranges set up, so that seems a likely resolution.

[VivekSattanatha]

HI Dale,

Setting up an IP ranges is the best solution if you have multiple MID Server for orchestration.

But If you have only a single MID Server which is used for Orchestration then you can set default MID Server property in the Orchestration module.

Regards,

Vivek

Based upon the impact hit like, helpful or correct