ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

After upgrade Banner Jobs fail with 'Error executing Banner commandError code returned:137'


Article ID: 88039


Updated On:


CA Automic Workload Automation - Automation Engine


Error Message :
Cap: Error executing Banner commandError code returned:137

After an upgrade of the RA Banner Agent from version 3.0 to 3.6 and an upgrade of Applications Manager from v8.0.9 to v9.1.0 all Banner Jobs Abort and the above error message is displayed.


This issue has only been seen after an upgrade of:
  1. RA Banner 3.0 to 3.6
  2. Applications Manager v8.0.9 to v9.1.0
Banner jobs will Abort, and the following error is present in an output log of a Banner job:
Standard error =========================== 

End standard error ========================= 
Output directory /home/jobsub/ncf 
User search pattern:.*[^0-9']{ONE_UP}[^0-9].* 
User search evaluated: .*[^0-9']865884[^0-9].* 
Search /home/jobsub/ncf using .*[^0-9']865884[^0-9].* 
Files [/home/jobsub/ncf/banworx_fgractg_865884.log] 
Cap: Error executing Banner commandError code returned:137 
Command:/home/local/appworx2/banner/NCPO/UC4gjajobs.shl fgractg C banworx pass 865884 NOPRINT 


Cause type:
Root Cause: Further research is necessary to determine root cause.


OS Version: N/A


At the current time we have not been able to determine the cause of the error and would need the following information in order to further research the issue:

Enable debug in the Awenv.ini file:

Then send the RmiServer<timestamp>.log, AgentService<timestamp>.log, and any related output files that are generated to Automic Support.

Fix Status: No Fix

Fix Version(s):

Additional Information

Workaround :
Restore the Applications Manager (AM) database using a backup before the upgrade of AM and the RA Banner Agent.
Revert back to previously working AM and RA Banner Agent versions.