search cancel

Jobs not moving from INITIATED/LAUNCHED to RUNNING

book

Article ID: 215850

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

Jobs start to receive LAUNCH ERROR. The logs don't reveal much and restarting the services has jobs still only go to INITIATED and LAUNCHED, not RUNNING. Several older jobs were removed manually, but still nothing runs.

Environment

Release : 9.3

Component : APPLICATIONS MANAGER

Resolution

This can be caused by the the output directory on the server having too many files

Check to see if there are too many files in the output directory
Back up the output directory and rename it
Recreate the output directory; jobs should run again.