Problem With Run-time Difference Between Task Scheduler Triggered Start and Manual Start
Posted on 2008-11-18
I'm using Task Scheduler to run scripts that integrate Author-it (authoring/publishing platform) and pdfFactory Pro (printer-queue PDF converter). When I start a task manually (click the Run button), it works perfectly. However, when I start the same task using a daily trigger, it appears to run correctly (no errors anywhere) but produces no PDF output files. There has to be a difference in the run-time environment that affects the PDF printer queue settings. (The job sets the default printer queue of course.)
The PDF printer queue keeps its queue-specific registry settings, including the desired PDF location, stored in HKEY_CURRENT_USER. The job uses the same username and password each time so theoretically, there should be no difference in the job's run-time environment. This one has had me baffled long enough to think about investing in a third-party task scheduler.