Program runs fine, but task scheduler won't run it

Question

I am running Win Server 2008 R2.  I have a console app that I wrote, which runs just fine when I click on ConsoleApp1.application file.  I want the task scheduler to run this console app every ten minutes, so I set up a task using task scheduler.  Whenever the task scheduler tries to run it, though, it fails, and return an erro rmessage "%1 is not a valid Win32 application. (0x800700C1)".

Most of what I've found in searching talks about making this stuff work on IIS, but I'm not using IIS.  I'm just running a pretty plain ol' vanilla console app.

This is a console app, not a web app.  I've set the task up as a Windows 2008 R2 task, using Domain Administrator credentials, with "Run with highest privileges" checked.  I'm not sure what else to do.  Can someone provide some other advice to try?

Answer 1

I have the same problem - was there ever a resolution for this?

Thank you!

Answer 2

Sadly, no.  But what I've read leads me to believe that it has to do with the fact that it's a 32-bit app.  I have a 64-bit development machine on order.  When it gets here I'm going to recompile my app as a 64-bit app and see if that solves the problem.  I'll let you know.

Answer 3

Hi ScottDarth,

I was wondring if there was any resolution to your issue. What I am up against is very similar. I have a windows application written in VB.NET 3.5, it uses Excel Libraries to work with Excel. When I run it as a stand alone application it works flawlessly, but when scheduled through Task Scheduler, it just hangs. In Task Manager I can see that it has created a handle on Excel application, but then it doenst move forward.

I have read though numerous posts but havent come to a conclusion. The Excel is a 32 bit installation, and my server is 64bit 2008 R2.

I would really appreciate any input.

 

Thank you

 

 

Answer 4

Sorry, I've not been successful with this at all.  There doesn't seem to be any published resolution to this that I can find.

Answer 5

Hi ScottDarth,

I've seen something similar, basically taskscheduler assumes that the applicaiton is 64 bit. If it is 32 bit then try launching it from the 32 bit command line, i.e. if you want to run c:\program files (x86)\Myprogram\Program.exe, tell taskscheduler to launch:

%systemroot%\Syswow64\cmd.exe /C "c:\program files (x86)\Myprogram\Program.exe"

This forces it to launch from the 32 bit command-prompt and hence with 32 bit emulation.

Regards,

Nick

Answer 6

Hi pattmania,

I was in the same issue. So I tried with your solution and finally it works for me.

I created a simple .bat file that launches my console app and it's working now.

Thank you very much!

Lawrence

Answer 7

Try to change the version of the console application to 32 bit.

i.e. Right click  Goto  -> Properties -> Build ->  Platform Target  = x86.

Rebuild the application and run the scheduler. it should work now...

Answer 8

THIS WORKS. I created a 2013 console app to run an SSIS package. For various reasons the app had to remain as 32 bit. I COULD not get Task scheduler to work until I tried this remedy. Thank you so much.

Answer 9

Hi ,

I am not sure if this is still an issue with you . But I had this problem for longest time and it took me a while to get to the solution . So posting it here for someone who may need it .

Create these two folders:

32Bit:

C:\Windows\System32\config\systemprofile\Desktop  

64Bit:

C:\Windows\SysWOW64\config\systemprofile\Desktop

Excel needs these folders if it's not run interactively. Create both folders even if you are on a 64-bit OS.

Answer 10

Our problem was the EXTENSIONS were hidden on our servers - so when I asked for a scheduled task to be created (on a 'new' server) the person who created it for me thought he was selecting 'file.exe' but he actually selected 'file.exe.config' (b/c it wasn't displaying the .config. bit in File Manager).

WHY is that the default on a SERVER?

Answer 11

I had similar problem, but managed to fix it when changed in task properties: Start in (optional) value to my aplication location. Without it, the task sheduler runs in system32 folder but my program wont have privileges to run in system32.

Answer 12

David, this is totally unrelated but I just had to say something since we have nearly identical names.  

Cheers!

Answer 13

It works for me too. Really appreciate you help!

Answer 14

I am running Win Server 2008 R2.  I have a console app that I wrote, which runs just fine when I click on ConsoleApp1.application file.  I want the task scheduler to run this console app every ten minutes, so I set up a task using task scheduler.  Whenever the task scheduler tries to run it, though, it fails, and return an erro rmessage "%1 is not a valid Win32 application. (0x800700C1)".

Most of what I've found in searching talks about making this stuff work on IIS, but I'm not using IIS.  I'm just running a pretty plain ol' vanilla console app.

This is a console app, not a web app.  I've set the task up as a Windows 2008 R2 task, using Domain Administrator credentials, with "Run with highest privileges" checked.  I'm not sure what else to do.  Can someone provide some other advice to try?

Hello have you tried to create a bat file , which will cd to the path of the file and then runs it ?

Answer 15

Jen, your a lifesaver for this info, I was going nuts trying to find out why I couldn't get it to work.

Answer 16

I had similar problem, but managed to fix it when changed in task properties: Start in (optional) value to my aplication location. Without it, the task sheduler runs in system32 folder but my program wont have privileges to run in system32.

This did the trick for me, thanks so much.

Answer 17

I observed similar situation.  You need to insure "Run with highest privileges" box in "Security options" is checked!

Answer 18

Hi Joel Lepp,

I also tried the same and it worked for me.

Answer 19

I had the same problem.

Running on Windows Server 2008.

Tried all the solutions proposed here, and from other forum. Nothing works.

The only thing that worked for me, was to convert the BAT to EXE.

Then it run perfect.

Somehow, I dont know if it was an update from Windows or what, but from one minute to another, Taskman started to have this issue, and this was the only thing that made it work again

Hope it helps

Regards!

Answer 20

This worked for me thanks!