I'm having trouble with getting the Updater to work as a scheduled task using the /checknow command line argument. If I take the same project and only change the command line parameter in the scheduled task configuration from /checknow to /silentall the scheduled task executes perfectly and my program is updated. If I install my program and then run the updater from a shortcut (either installed with the program or manually via the command prompt) using the /checknow argument, it also executes perfectly. I get the message letting me know that an update is available and it allows me to download and install it.
What happens when I try to run the scheduled task is that the task will execute and finish. If I check the Scheduled Task logs, I get the following:
"Updater.exe.job" (Updater.exe)
Started 6/23/2010 4:25:50 PM
"Updater.exe.job" (Updater.exe)
Finished 6/23/2010 4:25:58 PM
Result: The task completed with an exit code of (0).
However, the updated MSI file is not downloaded and therefore my program is not updated - check the downloads folder specified in the Updater configuration and only the aiu file exists. If I check the log files on my web server, I can verify that the Updater is getting the updates.txt file, but it does not try to get the updated MSI.
After running the scheduled task with the /checknow argument, if I check the Windows Task Manager processes, I can see that the Updater is still running under the SYSTEM username, but it is not using any CPU resources and seems to just be stuck. If I rerun the scheduled task, another Updater process will spawn and finish with the same results. If I try to run the Updater (either via the shortcut or command line), I now get a Windows error saying that the Advanced Updater has encountered a problem and needs to close and then a Dr. Watson message pops up. If I kill the Updater process that is stuck and then try to run the Updater (either via shortcut or CLI), it runs perfectly again.
Any ideas on what could be causing this problem?
P.S. If it makes a difference, I was using 7.3.1 when I encountered the issue. I also updated to 7.7 in hopes that it would help, but it didn't.
Thanks.
FOLLOW US
Get the latest news in Application Packaging