Need help understanding MID config for Flow PowerShell action processing

chadlockwood
Kilo Sage

‎03-14-2022 01:43 PM

A new flow that processes a PowerShell script failed because it couldn't find a suitable MID server. We have four MID servers in Prod, we'll call them MID2-5; Dev/Test share a MID server, MID1. 

 Here is the configuration for the PowerShell Action

 find_real_file.png

The error in the logs:

Unable to find any validated MID Server based on status (up), and application: ALL, and IP Range: (127.0.0.1)

Previously, in custom workflow PowerShell activities, the Host value was set to Localhost (127.0.0.1) to show that PowerShell will run directly on the MID server, as opposed to running on another machine. To my knowledge, this never really had any impact on the processing of the workflow or PowerShell script.

You can see that the MID selection is “Auto-Select”, Application is “ALL” and Capabilities is “PowerShell”.

All four Prod MID servers include ALL in Supported Applications.

MID5 is the only one that doesn’t include PowerShell in Capabilities.

I set an IP Range on MID4 for Localhost (127.0.0.1), but that didn’t work. I did the same on MID2 and it DID work.

Here are the questions I need help answering:

  1. During testing of this flow, this was never a problem in Dev/Test. Is this because there was only one MID server to choose from? Regardless of configuration?
  2. Why didn’t MID4 work with the Localhost IP Range, when MID2 did?
  3. What would happen if I add a Localhost IP range to all MID servers?
    1. Will it allow the Flow to load-balance between all of the MID servers?
    2. Will it just use the first MID it finds?
    3. Will this affect the processing of any of our workflow activities?

 We don’t currently have multiple MID servers for the lower environments, so I don’t really have a way to test this outside of Prod.

Preview file
70 KB
0 Helpfuls
  • 660 Views
2 REPLIES 2

Maik Skoddow
Tera Patron
Tera Patron

‎03-14-2022 07:21 PM

Hi

maybe the following article can help you: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0871106

Kind regards
Maik

0 Helpfuls

chadlockwood
Kilo Sage
In response to Maik Skoddow

‎03-25-2022 07:25 AM

Not really. This talks about assigning a specific MID server. I don't need to use a specific one, they all should be capable. On the PowerShell action step, the Host field defaults to 127.0.0.1 and I am unable to clear that out. The error message I saw included there was no MID server with an IP Range of 127.0.0.1, which seems strange since they are all technically that.

So I guess the real question would be "at what point did there become a requirement to add local host as an IP Range when running PowerShell solely on the MID server?"

0 Helpfuls