Job stuck in RUNNING when o-file is open on Windows Agents.

Document ID : KB000090194
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Job stuck in RUNNING when o-file is open on Windows Agents.
Resolution:
Detailed Description and Symptoms
Job stuck in RUNNING when o-file is open on Windows Agents.
 
Investigation
1. Run TEST_JOB with a time of 50 seconds.
2. After the job is requested and the job is in a RUNNING status, Open the jobs output file, and click on view.
3. Leave the file open.

The job stays stuck in a RUNNING status until the output file is closed. It appears the that the internal file viewer has a 'hold' on the output file and does not let the job to finish.

The last entry in the output file, while the internal file viewer was still open was:

Fri Oct 16 08:02:20 2009 Done with printem
Exit with 0
end of C:\AppWorx\80\exec\BODY2.BAT status 0 Fri 10/16/2009 8:02:20.79
err is:'0'
log_run is:'Y'
min_run_time=0
exiting BODY2

Under normal runs without the Internal File Viewer open, it continues after this point and calls and finishes BODY3.

Solution
This issue it due to limitations of the Windows OS and is not something we can accommodate for in our product.  Generally, users should not open time sensitive job output files open in the file viewer while the job is in a RUNNING status.  As it will prevent the job from finishing.

If the job is stuck in a RUNNING status after you have closed the o-file, please call UC4 Support for assistance.