Bill Benson
bensonforums at gmail.com
Tue May 27 15:19:27 CDT 2014
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 >