Scheduled Tasks not running reliably

I have two nightly scheduled jobs at a client site - one at 2:00am and the
other at 5:00am

Both jobs launch Access 2003, log into the default system workgroup, open a
[different] Access .mdb that collects data, then shuts down.

Except for the scheduled time and file paths, the job settings are
identical. The machine is password-protected, so when each job was created
the password was entered.

The jobs don't start reliably. The 5:00am job runs most nights, but the
2:00am job doesn't run most nights.

Any ideas?

DFS wrote:

> I have two nightly scheduled jobs at a client site - one at 2:00am and the
> other at 5:00am
>
> Both jobs launch Access 2003, log into the default system workgroup, open a
> [different] Access .mdb that collects data, then shuts down.
>
> Except for the scheduled time and file paths, the job settings are
> identical. The machine is password-protected, so when each job was created
> the password was entered.
>
> The jobs don't start reliably. The 5:00am job runs most nights, but the
> 2:00am job doesn't run most nights.
>
> Any ideas?
>

Does it even start? Have you done some tests....change the schedule to
a time when you are there. You might want to bypass the collecting of
data part with these new times...you simply want to see if it starts and
runs.

Also, you could either write to a text file or to a table the the steps
to see if it is erroring out. Ex. when the code/form fires write a
line like "Form Opened. " & Now(). Then after initializing something
enter "Init complete " & Now(). Etc. When you come in you can find out
what processes were completed and what processes were not complete. At
least you'll have a place where you can see where the program aborts.
Of course, if you don't see any messages that means the program didn't
even fire.

You might have an event that has an error and with an error routine it
might bypass a whole bunch of stuff...and then the program closes...so
you don't know where the problem is.

Salad wrote:
> DFS wrote:
>
>> I have two nightly scheduled jobs at a client site - one at 2:00am
>> and the other at 5:00am
>>
>> Both jobs launch Access 2003, log into the default system workgroup,
>> open a [different] Access .mdb that collects data, then shuts down.
>>
>> Except for the scheduled time and file paths, the job settings are
>> identical. The machine is password-protected, so when each job was
>> created the password was entered.
>>
>> The jobs don't start reliably. The 5:00am job runs most nights, but
>> the 2:00am job doesn't run most nights.
>>
>> Any ideas?
>>
>
> Does it even start? Have you done some tests....change the schedule
> to a time when you are there. You might want to bypass the
> collecting of data part with these new times...you simply want to see
> if it starts and runs.
>
> Also, you could either write to a text file or to a table the the
> steps to see if it is erroring out. Ex. when the code/form fires
> write a line like "Form Opened. " & Now(). Then after initializing
> something enter "Init complete " & Now(). Etc.

I do all those things. I write messages at checkpoints to a text file.

When the job kicks off, it has always run all the way through. The problem
is it won't kick off. I'll sit there at the machine and test it - say at
3:00pm schedule it for 3:01pm and watch it run just fine. Then change the
scheduled time back to 2:00am (reenter the password if asked) and leave.
Next day - job didn't run.

It's very irritating.

Thanks



> When you come in you
> can find out what processes were completed and what processes were
> not complete. At least you'll have a place where you can see where
> the program aborts. Of course, if you don't see any messages that
> means the program didn't even fire.
>
> You might have an event that has an error and with an error routine it
> might bypass a whole bunch of stuff...and then the program closes...so
> you don't know where the problem is.

Thanks

I've had great luck with Schedule Tasks.
A shot in the dark here, but, have you checked the Settings Tab and try to
check the "Wake the computer to run this task" box.

Worth a try, I suppose.
HTH,
Pat


"DFS" <nospam@nospam.com> wrote in message
news:10l6tf37laum974@corp.supernews.com...
> Salad wrote:
> > DFS wrote:
> >
> >> I have two nightly scheduled jobs at a client site - one at 2:00am
> >> and the other at 5:00am
> >>
> >> Both jobs launch Access 2003, log into the default system workgroup,
> >> open a [different] Access .mdb that collects data, then shuts down.
> >>
> >> Except for the scheduled time and file paths, the job settings are
> >> identical. The machine is password-protected, so when each job was
> >> created the password was entered.
> >>
> >> The jobs don't start reliably. The 5:00am job runs most nights, but
> >> the 2:00am job doesn't run most nights.
> >>
> >> Any ideas?
> >>
> >
> > Does it even start? Have you done some tests....change the schedule
> > to a time when you are there. You might want to bypass the
> > collecting of data part with these new times...you simply want to see
> > if it starts and runs.
> >
> > Also, you could either write to a text file or to a table the the
> > steps to see if it is erroring out. Ex. when the code/form fires
> > write a line like "Form Opened. " & Now(). Then after initializing
> > something enter "Init complete " & Now(). Etc.
>
> I do all those things. I write messages at checkpoints to a text file.
>
> When the job kicks off, it has always run all the way through. The
problem
> is it won't kick off. I'll sit there at the machine and test it - say at
> 3:00pm schedule it for 3:01pm and watch it run just fine. Then change the
> scheduled time back to 2:00am (reenter the password if asked) and leave.
> Next day - job didn't run.
>
> It's very irritating.
>
> Thanks
>
>
>
> > When you come in you
> > can find out what processes were completed and what processes were
> > not complete. At least you'll have a place where you can see where
> > the program aborts. Of course, if you don't see any messages that
> > means the program didn't even fire.
> >
> > You might have an event that has an error and with an error routine it
> > might bypass a whole bunch of stuff...and then the program closes...so
> > you don't know where the problem is.
>
> Thanks
>
>

Pat wrote:
> I've had great luck with Schedule Tasks.
> A shot in the dark here, but, have you checked the Settings Tab and
> try to check the "Wake the computer to run this task" box.
>
> Worth a try, I suppose.
> HTH,
> Pat

Pat,

I have tried it, to no avail. As far as I can tell, the computer doesn't
ever go into power hibernation. I'll look at it again, though.

The task ran fine for the first 7 days it was deployed, but no longer. I'll
recreate the task - maybe that's the ticket.

Thanks




> "DFS" <nospam@nospam.com> wrote in message
> news:10l6tf37laum974@corp.supernews.com...
>> Salad wrote:
>>> DFS wrote:
>>>
>>>> I have two nightly scheduled jobs at a client site - one at 2:00am
>>>> and the other at 5:00am
>>>>
>>>> Both jobs launch Access 2003, log into the default system
>>>> workgroup, open a [different] Access .mdb that collects data, then
>>>> shuts down.
>>>>
>>>> Except for the scheduled time and file paths, the job settings are
>>>> identical. The machine is password-protected, so when each job was
>>>> created the password was entered.
>>>>
>>>> The jobs don't start reliably. The 5:00am job runs most nights,
>>>> but the 2:00am job doesn't run most nights.
>>>>
>>>> Any ideas?
>>>>
>>>
>>> Does it even start? Have you done some tests....change the schedule
>>> to a time when you are there. You might want to bypass the
>>> collecting of data part with these new times...you simply want to
>>> see if it starts and runs.
>>>
>>> Also, you could either write to a text file or to a table the the
>>> steps to see if it is erroring out. Ex. when the code/form fires
>>> write a line like "Form Opened. " & Now(). Then after initializing
>>> something enter "Init complete " & Now(). Etc.
>>
>> I do all those things. I write messages at checkpoints to a text
>> file.
>>
>> When the job kicks off, it has always run all the way through. The
>> problem is it won't kick off. I'll sit there at the machine and
>> test it - say at 3:00pm schedule it for 3:01pm and watch it run just
>> fine. Then change the scheduled time back to 2:00am (reenter the
>> password if asked) and leave. Next day - job didn't run.
>>
>> It's very irritating.
>>
>> Thanks
>>
>>
>>
>>> When you come in you
>>> can find out what processes were completed and what processes were
>>> not complete. At least you'll have a place where you can see where
>>> the program aborts. Of course, if you don't see any messages that
>>> means the program didn't even fire.
>>>
>>> You might have an event that has an error and with an error routine
>>> it might bypass a whole bunch of stuff...and then the program
>>> closes...so you don't know where the problem is.
>>
>> Thanks

Hello,

Thanks for your posting here.

I also recommend that you re-create the scheduled task. If the problem
still persists, I would like recommend that you create new simple scheduled
task and put it at 2:00am. For example: a batch file only includes the
following command:

dir c:\ >c:\dir.txt

Does it run properly?

In addition, you can also set Details View in Scheduled Tasks to check the
status.

Wish it helps.

Regards,
Bob Qin
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
From: "DFS" <nospam@nospam.com>
Newsgroups:
microsoft.public.windowsxp.security_admin,microsoft.public.windowsxp.help_an
d_support,comp.databases.ms-access
Subject: Scheduled Tasks not running reliably
Date: Thu, 23 Sep 2004 15:33:55 -0400

I have two nightly scheduled jobs at a client site - one at 2:00am
and the
other at 5:00am

Both jobs launch Access 2003, log into the default system workgroup,
open a
[different] Access .mdb that collects data, then shuts down.

Except for the scheduled time and file paths, the job settings are
identical. The machine is password-protected, so when each job was
created
the password was entered.

The jobs don't start reliably. The 5:00am job runs most nights, but
the
2:00am job doesn't run most nights.

Any ideas?