Scheduled task disabled on own

30 Jun 2009 2:11 PM

Marty Mash

I have a scheduled task on a Windows 2000 server that copies data from a UNIX
server to the Windows server via FTP. This batch file has always worked and
July 31, 2008 the schedule was changed to take into account for our month end
processing to run at a different time for a few days per month. There are 90
some schedules in the job depending on the number of days in the month. The
job ran perfectly and then without anyone knowing it just became disabled on
Sept. 11, 2008.

Has anyone ever heard of a scheduled task just disabling on its own? The
job will stop if it runs for more than 9 hours, but normally only takes about
1 hour to run. The job also runs as the network domain admin with the proper
password as this hasn't changed since early in 2008.

What should I look for

30 Jun 2009 2:42 PM

Pegasus [MVP]

Show quote Hide quote

"Marty Mash" <MartyM***@discussions.microsoft.com> wrote in message
news:94756E5B-B216-44D6-A3D0-1FEFFAEF6EC7@microsoft.com...
>I have a scheduled task on a Windows 2000 server that copies data from a
>UNIX
> server to the Windows server via FTP. This batch file has always worked
> and
> July 31, 2008 the schedule was changed to take into account for our month
> end
> processing to run at a different time for a few days per month. There are
> 90
> some schedules in the job depending on the number of days in the month.
> The
> job ran perfectly and then without anyone knowing it just became disabled
> on
> Sept. 11, 2008.
>
> Has anyone ever heard of a scheduled task just disabling on its own? The
> job will stop if it runs for more than 9 hours, but normally only takes
> about
> 1 hour to run. The job also runs as the network domain admin with the
> proper
> password as this hasn't changed since early in 2008.
>
> What should I look for

This will happen when standard time changes to summer time and vice versa
but only on systems that use the FAT32 file system for the system volume.
You can restore the tasks by re-entering the appropriate passwords. By the
way, seeing that it took you 9 months to catch up with the problem, you
might want to create a monthly reminder (e.g. in Outlook) to remind you to
check all scheduled tasks. Your reputation as a system administrator gets
enhanced if you discover (and fix!) problems before your boss does.

30 Jun 2009 3:00 PM

Marty Mash

Thank you for the quick response Pegasus.

The system is running NTFS for all volumes and all I had to do was to check
the box to enable the job. Restarting the job isn't the problem it was more
of "why did this happen in the first place. I will keep my eye on this in
the future to make sure it actually is running when it is supposed to be.

The job started out as a single task that ran at 7 pm. But accounting was
complaining that the system was slow when they were doing their month end
close because of the job. My boss wanted the job time changed, just for
month end time, to 10 pm. I originally was just going to put a task in
outlook or a recurring reminder in outlook to change the times of the jobs,
but decided to actually adjust the schedules based upon the number of days in
the month so no one would have to manually adjust the time in the future.

Show quoteHide quote

"Pegasus [MVP]" wrote:

>
> "Marty Mash" <MartyM***@discussions.microsoft.com> wrote in message
> news:94756E5B-B216-44D6-A3D0-1FEFFAEF6EC7@microsoft.com...
> >I have a scheduled task on a Windows 2000 server that copies data from a
> >UNIX
> > server to the Windows server via FTP. This batch file has always worked
> > and
> > July 31, 2008 the schedule was changed to take into account for our month
> > end
> > processing to run at a different time for a few days per month. There are
> > 90
> > some schedules in the job depending on the number of days in the month.
> > The
> > job ran perfectly and then without anyone knowing it just became disabled
> > on
> > Sept. 11, 2008.
> >
> > Has anyone ever heard of a scheduled task just disabling on its own? The
> > job will stop if it runs for more than 9 hours, but normally only takes
> > about
> > 1 hour to run. The job also runs as the network domain admin with the
> > proper
> > password as this hasn't changed since early in 2008.
> >
> > What should I look for
>
> This will happen when standard time changes to summer time and vice versa
> but only on systems that use the FAT32 file system for the system volume.
> You can restore the tasks by re-entering the appropriate passwords. By the
> way, seeing that it took you 9 months to catch up with the problem, you
> might want to create a monthly reminder (e.g. in Outlook) to remind you to
> check all scheduled tasks. Your reputation as a system administrator gets
> enhanced if you discover (and fix!) problems before your boss does.
>
>
>

30 Jun 2009 3:16 PM

Pegasus [MVP]

Here are some other reasons why scheduled tasks may not run. I don't know
whether they just fail to run or whether they get disabled as in your case:
http://support.microsoft.com/default.aspx?scid=kb;en-us;329227
MS KBase Q272022
http://support.microsoft.com/?id=328773
http://support.microsoft.com/Default.aspx?kbid=867466

Show quoteHide quote

"Marty Mash" <MartyM***@discussions.microsoft.com> wrote in message
news:63A63F29-9B40-4F2D-8409-20A5248DA6E7@microsoft.com...
> Thank you for the quick response Pegasus.
>
> The system is running NTFS for all volumes and all I had to do was to
> check
> the box to enable the job. Restarting the job isn't the problem it was
> more
> of "why did this happen in the first place. I will keep my eye on this in
> the future to make sure it actually is running when it is supposed to be.
>
> The job started out as a single task that ran at 7 pm. But accounting was
> complaining that the system was slow when they were doing their month end
> close because of the job. My boss wanted the job time changed, just for
> month end time, to 10 pm. I originally was just going to put a task in
> outlook or a recurring reminder in outlook to change the times of the
> jobs,
> but decided to actually adjust the schedules based upon the number of days
> in
> the month so no one would have to manually adjust the time in the future.
>
> "Pegasus [MVP]" wrote:
>
>>
>> "Marty Mash" <MartyM***@discussions.microsoft.com> wrote in message
>> news:94756E5B-B216-44D6-A3D0-1FEFFAEF6EC7@microsoft.com...
>> >I have a scheduled task on a Windows 2000 server that copies data from a
>> >UNIX
>> > server to the Windows server via FTP. This batch file has always
>> > worked
>> > and
>> > July 31, 2008 the schedule was changed to take into account for our
>> > month
>> > end
>> > processing to run at a different time for a few days per month. There
>> > are
>> > 90
>> > some schedules in the job depending on the number of days in the month.
>> > The
>> > job ran perfectly and then without anyone knowing it just became
>> > disabled
>> > on
>> > Sept. 11, 2008.
>> >
>> > Has anyone ever heard of a scheduled task just disabling on its own?
>> > The
>> > job will stop if it runs for more than 9 hours, but normally only takes
>> > about
>> > 1 hour to run. The job also runs as the network domain admin with the
>> > proper
>> > password as this hasn't changed since early in 2008.
>> >
>> > What should I look for
>>
>> This will happen when standard time changes to summer time and vice versa
>> but only on systems that use the FAT32 file system for the system volume.
>> You can restore the tasks by re-entering the appropriate passwords. By
>> the
>> way, seeing that it took you 9 months to catch up with the problem, you
>> might want to create a monthly reminder (e.g. in Outlook) to remind you
>> to
>> check all scheduled tasks. Your reputation as a system administrator gets
>> enhanced if you discover (and fix!) problems before your boss does.
>>
>>
>>