Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We have a series of tasks which, when run interactively over the command line run fine creating temporary files and (importantly) logs and backups.

When we schedule the task with Administrator privileges to run at the highest priority, however, no logs or temporary files are created! All the directories have read/write privileges as administrator.

Has anyone else experienced this??

We are running Windows 2008 Server & the job is configured for 'Windows Vista or Windows Server 2008'.

Any help would be much appreciated!


OK - so we installed Z-Cron and it works perfectly.... Still a really really strange error from Windows 2008 Task Scheduler, but a solution is perhaps not quite so urgent now we have Z-Cron working!

share|improve this question
    
Uh Oh.. just thought, this might better belong at SuperUser?.... –  Nick Cartwright Sep 15 '10 at 16:31
    
No, this is the right place for this question. –  Izzy Sep 15 '10 at 16:33
    
What happens when you manually trigger the task? –  Izzy Sep 15 '10 at 16:50
    
Hi Izzy - When we manually trigger the task, still no files are created. –  Nick Cartwright Sep 15 '10 at 17:01
    
Check your path environmental variable. –  xeon Sep 15 '10 at 17:06

2 Answers 2

Make sure that your Start Location for the script is the correct place. It's possible the script is trying to do this in the wrong location? If this doesn't work can you tell us what the result in Task Scheduler is? It should at least be telling you if it's failing for some reason - or if the Task Scheduler thinks everything is succeeding. If you can run it manually from the command line then your script is working - which leaves: Permissions and Location.

share|improve this answer
    
Hi there. Thanks for your reply! Task Scheduler thinks everything is succeeding. We have reduced our script down to a python script with the following code: 'import os <return space> os.mkdir('folder_1234')', so we are sure nothing else is happening in there. Regarding permissions, we are running the script as Administrator, but we will try running from a different drive. –  Nick Cartwright Sep 16 '10 at 8:34

Check C:\Windows\Temp. For me, when the scheduled task runs when not logged in, it was using this location as TEMP instead of C:\Users\USER\AppData\Local\Temp.

For me, this problem only struck while using Windows Server (2012) - didn't occur when using a client version of Windows (e.g., Windows 7).

Note, that when logged in and running the task manually - it would use the users temp location - which was what was throwing me.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.