Wednesday, December 05, 2012 11:21 PM
Please could someone help shed some light. I have spent all day investigating a scheduled task failing, the platform is Server 2003 SP2, and we have a task that converts file types and creates files for our customer. During all day investigation/testing we seemed to have a situation where the task would complete successfully if we were logged on to the box at the time of running but fail half way through at a certain point if noone was logged on. We believe it was failing when trying to use a fileconverter program to convert a file format or trying to write the new file to the destination directory. We tested for several hours homing in on the issue with consistant results. everytime we logged out the process would fail and when we were logged in it would be successful.
We decided to try to create another scheduled task identical in everyway and run that to see if somehow the first one was corrupt, we did this and low and behold it worked, great we thought we've sussed it, so we then disabled the new task and reenabled the old one to confirm it was still corrupt but it worked also, now however many times we try the original task will not fail again.
This may sound like I now have no issue but it is very important I can explain the cause as it is part of a very high profile project, and no one will accept that I don't know why it wasn't working. Does anyone know what disabling and reenabling the original task may have done to resolve the issue considering nothing else was changed?
- Changed Type Santosh BhandarkarMicrosoft Community Contributor, Moderator Thursday, December 06, 2012 1:44 PM Question
- Changed Type Cheers ZHANGMicrosoft Contingent Staff, Moderator Thursday, December 13, 2012 6:57 AM
Thursday, December 06, 2012 1:37 PM
First, did you check the Scheduled Task error log when the task did fail ? What was the returned error message and code ? (Advanced, View Log in Scheduled Task window).
Friday, December 07, 2012 10:22 AM
Yes I did check this and it did not report anything, as far as the schecdular was concerned it was run. Additional logging in the program showed that it failed at a certain point. The task script creates a copy of an image file then calls a image converter program which converts the format of that image then the script copies the converted image to another directory. The log states that the image is not found in the new directory, so either the converter program did not run or it failed to copy, we were homing in on this until it just started working again.