This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 89%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBV%3C/text%3E%3C/svg%3E)
Windows 2012 R2 Server, Windows 10 H2 workstation, MS Access 2016
This problem started recently and is limited to 1 workstation
Scheduled Task runs a batch file which in turn executes DOS commands (Dir, Copy) and Access databases
The DOS commands before the 1st run Access command execute
It used to work on this workstation but stopped recently, it does work on other workstations and works if I directly execute the batch file (double click it)
The Access application opens then immediately stops working - no corresponding Events
I have scaled a test version back to a single VBA command (called from AutoRun Macro) DoCmd.OutputTo (simple table to a text file) and it still fails without creating the text file
Access is left open, I use Task Manager to close Access then I can delete the laccdb file
SFC and DISM do not find any problems, I repaired MS Office but this did not help
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 50%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJY%3C/text%3E%3C/svg%3E)
Hi,
1.For the working and non-working machines, is there any differences like patches installed or any changes made recently?
2.The Access application opens then immediately stops working - no corresponding Events
Do you mean there is nothing recorded for this action under Microsoft-Windows-TaskScheduler/Operational?
How about the Last Run Result?
3.Have you tried to test by different account for this scheduled task as well as other conditions?
Hope this helps and please help to accept as Answer if the response is useful.
Thanks,
Jenny
Both PCs are running the same version of Windows 10 (20H2) with the same patches and updates
There are no error or warning events at the time the Task Schedule starts - several Audit messages
The task starts then keeps running with the code 0x41301
When I stop the task running Access remains open - I have to use Task Manager to close
This is a test Access database that is reduced down to a Function with 2 commands Outputto and quit and the function is run from the AutoExec Macro
I get the same result on this PC with several different Access databases including the original version which is scheduled to run at 5:00AM every day to scaled down test versions which are executed from 1 time tasks
All run when executed directly but fail when executed by a scheduled task while the PC is signed out
I am the system admin and I created the Task using my admin login so the scheduled task should have admin rights
The original application ran every morning without problems for several months UNTIL the server crashed about a week ago - our only server was off line when this task kicked off at 5:00AM and the task has not worked since
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 44%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECD%3C/text%3E%3C/svg%3E)
if you have not already, replace the Access front end file of the non working PC with another known-good Access front end file.... and see if that makes a difference.
I moved the database to another PC and it is running ok
The problem appears to be with this specific PC - something happened when the server crashed and then this PC tried to connect to open a SQL table on the server
my experience has been that it was not the PC, but rather the Front End file was corrupted in a way that showed no evidence to it's user otherwise....so I also thought it was the PC... so be sure to double check that by trying that PC with a known-good front end file.... glad you found a fix though....
I created a new, from scratch Front End on another computer then copied to the computer with the problem - and it failed on execution
The test FE consists of the AutoExec Macro that executes a Function that assigns a variable and then quits (I also tried executing the function from a form that opens when the FE opens)
Access opens then stops - there are no associated error events, just Security events documenting the task starting and running Access
I ran SFC and it did not find any errors and I repaired MS Office but this did not fix the problem
The Original (actual production FE) ran for a few days then stopped working with the same problem
In all cases the FE (Test or production) runs fine when directly executed but not when run from a batch file/scheduled task
The folder that the FE is executed from is a Trusted location
well that is interesting and kudos for being thorough and having a good test plan... Scheduled Tasks is not my wheelhouse so I can't get a handle on why that method of launching will not run.... presuming you could schedule open an excel or Word doc....and those files also could trigger VBA code to run.... hmmm going to monitor this and see if others more into Schedule scripts have input....