Brad Marks
bradm at blackforestltd.com
Tue Sep 9 16:57:09 CDT 2014
All, Back in June, I posted an entry about problems that I was having when trying to use schtasks to initiate an Access "Batch Report Job" on a server. We were in the process of upgrading our old server from Windows Server 2003 to Windows Server 2012. The script on my PC worked nicely when using the old server, but I could not get it to work when trying to initiate jobs on the new server. I did a lot of testing and research, but I simply could not get things to work. FINALLY, today I discovered the problem. My PC is still running XP (it is on the short list for an upgrade to Win-7). I tried the schtasks test on another PC that has Win-7 and it worked! I am all smiles. I thought that I would pass this info on in case others run into this issue. Brad ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > All, > > For the past couple years, I have used schtasks.exe to initiate an > Access 2007 Report Job that runs on a server (Windows Server 2003) from a PC. > > We are now in the process of upgrading this old server to a new box > which runs Windows Server 2012 R2. > > Here is the command (on the PC) that used to work with the OldServer > > schtasks.exe /S OLDServer /Run /TN Task1 > > I have tried numerous modifications, but cannot get this to work with > Windows Server 2012. > > Does anyone have an example of using schtasks to fire up a job on > Windows Server 2012? > > Thanks, > Brad ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~