Adding custom debug to troubleshoot Launch Errors on Windows Agent

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

When a Job ends in Launch Error status, an output file is generally not available since the failure occurs before an output file is generated.

If an output file is generated, this article will not apply to the Launch Error and it is recommended that Broadcom Support is contacted for further review and assistance.

In cases where a Launch Error does not generate output, adding a custom debug to the %AW_HOME%\bin\spawnbody.bat file may assist in troubleshooting the Launch Error

Environment

CA Automic Applications Manager 9.x

Resolution

1. Make a copy of the %AW_HOME%\bin\spawnbody.bat file and name it spawnbody.bat.bak.
   
   
2. Edit spawnbody.bat
   
   
3. On line 6 the below line is found
   
   start /min "jobid:%jobid%" %AW_HOME%\c\ntspawn -l %AW_HOME%\exec\BODY.BAT
   
   change this line to:
   
   %AW_HOME%\c\ntspawn -l %AW_HOME%\exec\BODY.BAT > %AW_HOME%\run\%SO_OPERATOR%\ntspawn_debug_%JOBID%.log 2>&1
   
   Save and close. This is a custom debug line that will write to file %AW_HOME%\run\<AGENTNAME>\ntspawn_debug_<JOBID>.log
   
   
4. Enable BODY debug by creating a file with the name BODY in the %AW_HOME%\debug directory. Create the debug directory if it does not exist. The BODY file will be a 0 bit file with no file extensions in the name.
   
   
5. Run TEST_JOB on the Agent where the Launch Error is occurring. Allow it to go into Launch Error.
   
   
6. %AW_HOME%\run\<AGENTNAME>\ntspawn_debug<JOBID>.log file. The log file should provide additional details or errors which may help in determining why Launch Errors are occurring. If needed, please open a case with Broadcom Support and provide the log file.
   
   
7. To revert debugging, delete the BODY and spawnbody.bat files, and then rename spawnbody.bat.bak to spawnbody.bat.