Job stuck as 'busy' in Orchestrator - Force Stop not working

I have two jobs ‘stuck’ in busy status in Orchestrator. I checked the VM where the main process runs and it was not doing anything and I was able to log on ok. I had our IT folks reboot the VM but the jobs STILL show as Busy. What do I have to do to really Kill the processes??? 11-20-2017 4-23-45 PM.pdf (24.4 KB)