Powershell jobs using custom interpreter throw error: '__call_messanger' is not recognized as the name of a cmdlet,

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

A Powershell job using the customer interpreter option (selected by the "Customer interpreter" radio button, on the Windows tab of job, see also additional info), ends with status ENDED_OK, but throws the error below after the execution of the Process:

__call_messanger : The term '__call_messanger' is not recognized as the name of a cmdlet, 
function, script file, or operable program. Check the spelling of the name, or if a path was 
included, verify that the path is correct and try again.
At C:\automic\MAIN\Agents\WIN01\temp\JAAFXJMA.TXT.ps1:4 char:1
+ __call_messanger "E" "0"
+ ~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (__call_messanger:String) [], CommandNotFoundExcept 
   ion
    + FullyQualifiedErrorId : CommandNotFoundException

Environment

Windows Agent

Cause

This is caused by the use of the INC HEADER.WINDOWS.PWSH.HEAD in the HEADER.WINDOWS or TRAILER.WINDOWS.PWSH.END in the TRAILER.WINDOWS objects in Client 0

Resolution

Prior to 21.0.8 HF3:

• log into client 0
• open the HEADER.WINDOWS object
• comment out the line:
  :INC HEADER.WINDOWS.PWSH.HEAD ,nofound=ignore
• open the TRAILER.WINDOWS object
• comment out the line:
  :INC TRAILER.WINDOWS.PWSH.END ,nofound=ignore

Beginning in 21.0.8 HF3 these lines are commented out by default in the HEADER/TRAILER.WINDOWS object in client 0.

This modification will not adversely affect the behavior if only the Custom Interpreter is used. If the UC_EXT_INTEPRETERS_WINDOWS VARA and the *_EXT_INTERPRETERS script functions are used a decision may need to be made on how to initiate the use of Powershell scripts.

Additional Information

This shows where the Customer interpreter is selected: