VI Jobs have a status value for when they are running (because VI jobs are not designed to be run by more than one person at a time).  When a job crashes (or otherwise does not complete properly) this status value is not reset to not running.  That means you have to open each job, click Yes, then Accept, to reset the status... before it can be run in any way.  (Only reset jobs when you are sure they are not actually still running... check Master Console, and task manager on the server for stray pvxwin32/pvxwin64 threads).

VI Jobs have a status value for when they are running (because VI jobs are not designed to be run by more than one person at a time).  When a job crashes (or otherwise does not complete properly) this status value is not reset to not running.  That means you have to open each job, click Yes, then Accept, to reset the status... before it can be run in any way.  (Only reset jobs when you are sure they are not actually still running... check Master Console, and task manager on the server for stray pvxwin32/pvxwin64 threads).

Great, thank you.

Hey Kevin, another issue we are running into is when we try to delete the task we are met with an error that says another user is using it. we tried ending all tasks in the task manager and resetting the server, but keep getting the error message. any ideas?

https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=224924750069169

It is not on file name list. 

You might want to get your Sage Partner / reseller involved.  DFDM edits are not to be taken casually.

For modern versions, typing in the table name will allow Sage to find it...

Ok, this is a test company for reference so if it needs to be deleted it can.

Task Scheduler entries are system wide, not limited to test companies.  Same with VI jobs.