Win2008 Scheduled task won't start 7zip.exe

Question

I made a backup tool for MS SQL Express that -daily- backs up, 7zips and uploads the zipped files via FTP. It is a program made in VB.net, built as an .EXE with a .config file. One of the functions calls a file "7zip.exe". Anyway, on Win2003 (20 webservers) this works perfect. Small databases, big databases, slow servers, powerstations... The 'daily basis' is created by launching a scheduled task at night.

Now in Win2008 R1 I also created a 'basic task' and set it up. When I launch it, I see it working except the 7 zip does nothing. It has something to do with the scheduled task because when I run the .EXE normally (double clicking...) it 7zips, as it should be.

Thanks in advance!

Answer 1

Are you using 7za.exe? It's the command line executable for 7zip, which we find works best for scripting.

Answer 2

I'm having a similar problem with Cron on Linux.

1) Are you using a FULL Path to the 7zip program within your VB Script?

2) Are you running the VB Script with the correct permissions (as the right user)?

Answer 3

Thanks resolove my issue. becuase on windows server 2008 need full path while raring: On my scenario i schediled a batch script to zip one file everyday,but it didnt work as below my old script: "C:\Program Files\WinRAR\WinRAR.exe" a test.rar test.txt : this didnt work

and i added the full path on my batch file and the below script works for me on windows 2008 server; "C:\Program Files\WinRAR\WinRAR.exe" a F:\ziptest\test.RAR F:\ziptest\test.txt : this works fine

Hope this wil help some one using Winrar on windows 2008 server and calling a batch script

Joseph

Answer 4

Make sure you also the Fully qualified path name, for network paths: full hostname or IP. As mostly in Win2008 R2..., also run the task with highest privileges or admin.

Answer 5

Windows Server 2008 made some changes to Scheduled Tasks, but I don't remember the specifics. I do remember having to update some tasks when I went from 2003 to 2008. You might need to assign a user to the task, even if it's a local job. If a regular user doesn't work, try a local admin user.

Answer 6

You may need to check the "Run with Highest Privileges" checkbox in addition to assigning a user/password to the task. This enables your application to start another process outside of itself.