Windows Task Scheduler stops running python script after a few weeks running successfully

Discussion created by wmakari on Dec 14, 2019
Latest reply on Dec 14, 2019 by wmakari

I have a python script that uses arcpy that I have scheduled to run using the windows task scheduler on a VM (Windows Server 2012, 64bit)


The script runs every hour and produces some maps in png using data driven pages.


The Windows Task Scheduler successfully runs the python script at the defined times for a few weeks before it decides to just stop.


This seems to be just happening with tasks that are calling python on the VM. I have other tasks that do not seem to be affected by this.


In the python script I log the progress of the script in a text file. 


Looking at the history tab of the task I can see the logs generated by the task scheduler from initiating the request, Action started etc. When it stops working I see all the logs that I expect from the Windows task scheduler up to Action Started. However, the python script does not seem to be executed at all as I do not get any logs from the python script in the text file that I log. The next Windows Task scheduler that I see is a task termination that is triggered at the time that I have set in the Settings of the Task (if task runs for x minutes stop it).


I don't know if there is something wrong with my script or if the Windows task is somehow not able to initiate the python script?


The strange thing is that script runs successfully for a few weeks before it decides to just stop for some unexplained reason? I would welcome any ideas on how I can get to the root cause of this issue?