MSACCESS - scheduled job will not run unless you're logged in

[David S]

I've seen similar issues but no solutions yet.

We are running Access 2003 on Windows Server 2003. We are trying to
schedule a job using Task Scheduler that opens an Access database and runs a
module which in turn opens another instance of Access that imports data into
a specific table (I didn't write the code, but it seems to get the job done.)

The job will run fine if you are logged into the server with the account
used to schedule the task. However, if you just schedule the task and log
off the server, the job will hang after opening the second instance of
Access. (It seems to stop at the point where it would import the data.) The
code works as intended IF you're logged into the server. It just won't run
via Task Scheduler.

Any ideas? I know there are two similar posts out there that would benefit
from a solution.

Thanks for looking!

 

[Damian S]

Hi David,

This seems more like a Windows Server 2003 question than an Access question,
since you say that the database works as intended if you open it when you are
logged in.

I would check that the permissions being attributed to the scheduled task to
"run" your access database are sufficient - ie: they have read/write
permission to the directories that your databases sit in etc.

Hope this helps.

Damian.

 

[David S]

Yes, that was something I considered.

To clarify, if I log into the server using my domain admin account I can run
the scheduled job manually. If I schedule the job with that same domain
admin account, the job hangs after it opens the 2nd instance of Access.

The similar posts I've seen involve running a macro with a similar result.