When running a TrueSight Server Automation (TSSA) Job a message such as "<job name> is already running" is shown, but the job does not appear in Tasks In Progress.  There may be a job run in the Job Results view in a running state.

There are a few different possible causes for this issue. One common cause is that the appserver intermittently loses its connection to the database and the queries to complete a job are not performed properly.

Using the InfraStructure Manager UI, look at the WorkItem-Thread activity across all appservers and make sure there are no WorkItem Threads involved in executing this job.

If workitem thread are found, then try and cancel this job run via the Tasks in Progress view (if visible still).

If this will not work it's advisable to get the thread dump from the appserver (3 or 4 dumps about 5 minutes apart) and include that in the support case so BMC Support can analyze why the job will not cancel.

If the user must cancel the job and it will not cancel from the gui, one can perform a restart of the appserver the 'stuck' workitem thread is running on.

If there are no WorkItem threads allocated to the job run and it is still showing as running, execute the below query on TSSA database to identify the particular job_run_id for further BMC investigation and provide output to Support:

select j.job_id,j.job_version_id,j.name,jr.job_run_id,ps.name from job j join job_run jr on j.job_id = jr.job_id and j.job_version_id = jr.job_version_id join progress_status ps on jr.progress_status_id = ps.progress_status_id where jr.progress_status_id not in (3,4,7) and j.name = '<job name>';

NOTE: If the error message is something like "<job name> is already running against <server>", then look at this KA: 000088196.