Brad Marks
bradm at blackforestltd.com
Wed May 28 15:27:23 CDT 2014
Bill, Yes, we could get around this problem by setting up a standalone machine that is always logged on. I would like to avoid this if I can find a way to make things work with the Windows Task Scheduler. Not sure about the Google Mail deal. Maybe I messed something up in an earlier post. Thanks, Brad -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bill Benson Sent: Wednesday, May 28, 2014 3:18 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Moving Access Application to Windows Server – Task Scheduler Problem Too bad. Thought the other post had nailed it. But truthfully you have called my bluff, I don't live in a networked world. I have NEVER had an application that TM ran, on a.machine that was not logged in. In fact I specifically remembering leaving a standalone machine turned on and logged in just so it could connect to the network and run scheduled tasks. Why can't that be done where you are? Also, why is this showing up in my Google Mail in its own thread I wonder, did the discussion headers get modified? Weird. On May 28, 2014 11:57 AM, "Brad Marks" <bradm at blackforestltd.com> wrote: > Bill, > > Thanks for the help. I tried the steps that you posted, but still no luck. > > In order to debug this issue, I have set up a very small Access > application that simply writes one record to a log file when it is > initiated. > > I then used the Windows Server 2012 Task Scheduler to establish a new > Scheduled Task which initiates MSACCESS.EXE directly with the name of > the little accdr file as a parameter. Running this task from the Task > Scheduler works properly when it is set to "Run Only When User is > Logged On". I can see that it is working by looking at the log file. > > However, when I change the setting to "Run Whether User is Logged on > or Not", things do not work. No record is written to the log file. > When I look at the Task Manager I see "Microsoft Access (32 bit)" in > the process list. > > I have looked at the logs via the Event Viewer but have not found > anything. My experience with the Event Viewer is quite limited, so > maybe I am not looking in the right place. > > Any help would be appreciated. > > > Thanks, > Brad > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com [mailto: > accessd-bounces at databaseadvisors.com] On Behalf Of Bill Benson > Sent: Tuesday, May 27, 2014 3:23 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Moving Access Reporting Applications from > Windows Server 2003 to Windows Server 2012 – Initiation Problem > > Btw, may be red herring but I am getting this from: > > > http://blogs.technet.com/b/askperf/archive/2012/04/18/task-scheduler-e > rror-a-specified-logon-session-does-not-exist.aspx > > Additional guidance: > > How to open the "Local Group Policy Editor" > > 1. click Run, type gpedit.msc, and then click OK. > > 2.Under Computer Configuration, expand Windows Settings, expand > Security Settings, expand Local Policies, and then expand Security Options. > > 3.In the Policy pane, right-click Network access: Do not allow storage > of credentials or .NET Passports for network authentication, click > Properties, click Disabled, and then click OK. > On May 27, 2014 4:19 PM, "Bill Benson" <bensonforums at gmail.com> wrote: > > > Check the network policy in the Local Group Policy Editor (if there > > is one in 2012, I think it came along with 2008 Server). > > > > If the Network "Do not allow storage of passwords and credentials > > for network authentication policy is enabled and applied, Credential > > Manager cannot store the credentials locally, and this might be what > > is > hurting you. > > On May 27, 2014 4:11 PM, "Brad Marks" <bradm at blackforestltd.com> wrote: > > > >> All, > >> > >> We are in the process of replacing our old Windows Server 2003 > >> machine with a new box that is going to run Windows Server 2012 R2. > >> > >> I have a number of Access applications that are run at night to > >> create reports. These report jobs are initiated via small scripts > >> which are used for a number of “utility” type tasks that are > >> related to the generation of the Access reports. > >> > >> Currently with Windows Server 2003, we have scheduled tasks set up > >> to initiate the little scripts. These scripts in turn do their > >> tasks and then initiate the appropriate Access accdr file to create > >> the > reports. > >> > >> This approach has worked well for several years in the Windows > >> Server > >> 2003 environment, but not so smoothly in the Windows Server 2012 > >> environment. > >> > >> If I have the Windows 2012 Task Scheduler set to “Only Run While > >> Logged On” everything works fine (as long as I am logged on). > >> > >> If I have the Windows 2012 Task Scheduler set to “Run While Logged > >> On or Logged Off”, the script is initiated, and it does a number of > >> small tasks properly. However, when it tries to initiate the > >> Access accdr file, nothing happens. The Access application is not > >> fired up and there are no error messages. > >> > >> Perhaps this is a new "feature" of the Task Scheduler. > >> > >> Has anyone else run into this issue? > >> > >> 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 > > -- > 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