ntspawn adds additional powershell parameters that can cause Jobs to Abort

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

The ntspawn.exe in Applications Manager 9.4.1 adds extra command line parameters when launching powershell.exe processes.  

For example, the below line is an echo statement from the program type script, immediately before running ntspawn.exe.  This shows the command used to run the ntspawn.exe utility.

CALL E:\AppManager\c\ntspawn powershell.exe E:\AppManager\Middleware\exec\pstest Value1 Value2

This line is from the job output, and shows the command executed by ntspawn.exe.

19 22:41:52-Executing:(255)[powershell.exe E:\AppManager\Middleware\exec\pstest Value1 Value2]

 

This line is from the job output.  Note that ntspawn.exe adds several parameters to the powershell.exe command ("-NoProfile", etc.).  

Command line to run: "powershell.exe"   -NoProfile -ExecutionPolicy unrestricted -file

These parameters may cause the powershell script to to fail.

Environment

Release : 9.4.1, 9.4.2, 9.4.3

Component : CA Automic Applications Manager (AM)

Resolution

This is resolved with Applications Manager 9.4.4