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

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

book

Article ID: 276056

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

Powershell job using agent interpreter (custom interpreter on Windows tab of job) ends with ENDED_OK, but throws the following error 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

 

Cause

This is caused by the use of :INC TRAILER.WINDOWS.PWSH.END ,nofound=ignore in the TRAILER.WINDOWS object in Client 0 with the customer interpreter option on a windows job

Resolution

Prior to 21.0.8 HF3, log into client 0, open the TRAILER.WINDOWS object and comment out the line:

:INC TRAILER.WINDOWS.PWSH.END ,nofound=ignore

By default beginning in 21.0.8 HF3 for the Windows agent, the following lines are commented out in the TRAILER.WINDOWS object in client 0:

As long as only the Custom Interpreter is used and not the UC_EXT_INTEPRETERS_* and the *_EXT_INTERPRETERS script function, this will not have any adverse effect on anything else.  If the UC_EXT_INTERPRETERS are used as well in the future, a decision may need to be made two use one OR the other.