This project has moved. For the latest updates, please go here.

Scheduled task in our 32-bit application fails to run when user is logged out

Dec 17, 2012 at 3:24 PM

Interestingly, the 64-bit version of our application runs fine, even if user is logged out!

A couple of our customers using the 32-bit version of our application on Windows 7 machines are complaining that they need to be logged in all the time in  order for their scheduled tasks to run successfully.

Is this "by design" or a bug in Task Scheduler 2.0?

Our configuration:
OS: Windows 7 64-bit
Option: "Run only when user is logged on" is NOT checked
Application is not accessing any remote servers...only local resources

Thanks, Audi

Coordinator
Dec 17, 2012 at 8:20 PM

I have not seen this problem before. I would check the event log to see if the 32bit task is reporting errors in the execution or the launch. That will tell you if the action, trigger or task is failing.

Dec 19, 2012 at 1:52 PM
Edited Dec 19, 2012 at 1:53 PM

Thanks David. I've examined the task history, and it's saying that the task completed successfully -- no errors, but no output! Looks like the 32-bit application has problem accessing input data when logged out, but not with the 64-bit version.

Coordinator
Dec 20, 2012 at 7:17 PM

Check some of the internet comments on Wow64 which governs how 32 & 64 bit compilations of .NET applications behave differently on 64 bit OSes.

Dec 20, 2012 at 7:29 PM

Will do...thanks David! Have a merry and safe X'mas!