13 views

 

Symptoms


"Resolve DNS Name" Orchestration Activity fails in the multi-domain environment because of wrong MID server selection.

Fault Description: Unable to find any capability matchable to the requested Capability: (Capability: PowerShell, value: null)

 

Environment


All Versions. 

Cause


The problem is because of the way how the MID server is selected for Orchestration activities.

Orchestration should use the default MID Server if it cannot find a MID Server with the correct IP range and capability.

In multi-domain (Domain separation), this selection criterion is not honored and it always looks for "Default MID Server" for Orchestration application. 

Resolution

 

1. You have to set "Default MID server" for Orchestration application for this to work.

                 OR

2. As a temporary workaround, create a copy of the "Resolve DNS Name" activity and on its properties, leave the 'Target host' empty and the activity would succeed.

 

Note: There is a problem: PRB1267529 for this.

Please raise an Incident if the solution doesn't work.

 

Additional Information


MID server selection:

https://docs.servicenow.com/bundle/kingston-it-operations-management/page/product/service-mapping/task/choose-mid-selection-algorithm.html

Article Information

Last Updated:2018-05-15 04:39:20
Published:2018-05-15