in reply to Re^3: PAR packaging and Windows scheduled tasks
in thread PAR packaging and Windows scheduled tasks

OK, I think I definitely narrowed it down to a whitespace issue. Here is my diagnosis regarding the settings of the scheduled task:

Install path: "C:\Program Files (x86)\my_app\"

-no specified default start path: did not work
-specified "C:\Program Files (x86)\my_app\" as the default start path: did not work

Install path: "C:\temp\my_app\"

-no specified default start path: did not work
-specified "C:\temp\my_app\" as the default start path: worked

Install path: "C:\dir with spaces\my_app\"

-no specified default start path: did not work
-specified "C:\dir with spaces\my_app\" as the default start path: did not work

I am still confused as to why the given start path does not work if it contains whitespaces BUT is enclosed in double quotes...


UPDATE:

Install path: "C:\Program Files (x86)\my_app\"

-no specified default start path: did not work
-specified "C:\Program Files (x86)\my_app\" as the default start path: did not work
-specified C:\Program Files (x86)\my_app\ (i.e. same as above but w/o the double quotes) as the default start path: worked
  • Comment on Re^4: PAR packaging and Windows scheduled tasks

Replies are listed 'Best First'.
Re^5: PAR packaging and Windows scheduled tasks
by hotchiwawa (Scribe) on Jan 06, 2016 at 16:12 UTC
    Did your scheduled task have access to your temp folder?
    Do you start it with a Runas admin rights?

    Check the Event Viewer ;)