Brad Marks
bradm at blackforestltd.com
Wed Sep 10 09:10:45 CDT 2014
Bill, Thanks for your reply. I suppose it could be some kind of policy or services setting. This is not a realm that I have worked with much. In summary, here is what I saw... Initiating Access Batch Report job (via schtasks) works fine from XP against Windows 2003 Server. Initiating Access Batch Report job (via schtasks) does NOT work from XP against Windows 2012 Server. Initiating Access Batch Report job (via schtasks) works fine from Win-7 against Windows 2012 Server. My conclusion from this is that there is a difference between XP and Win-7 when using schtasks to initiate jobs on a server Brad -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bill Benson Sent: Tuesday, September 09, 2014 11:13 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Using schtasks.exe to Initiate Access 2007 Report Job on a Server (from a PC) ---- Update - PROBLEM SOLVED !!! Do you really think it is a win-7 issue, or that some kind of policy or services setting is different on that machine's install than your own XP system? Guess it would be hard to know. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks Sent: Tuesday, September 09, 2014 5:57 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Using schtasks.exe to Initiate Access 2007 Report Job on a Server (from a PC) ---- Update - PROBLEM SOLVED !!! 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com