Re: Scheduled *.bat file won't execute Windows Server 2003
Services are meant to run more or less all of the time. Scheduled tasks are
supposed to run at certain times, as invoked by the Task Scheduler (which,
in fact, is a service!). You should continue invoking batch files or script
files with the Task Scheduler.
"Jeff C" <JeffC@discussions.microsoft.com> wrote in message
news:F0C0F871-7192-4C68-AB57-37B7CBD35A00@microsoft.com...
>
> --
> Jeff C
> Live Well .. Be Happy In All You Do
>
>
> "Pegasus (MVP)" wrote:
>
>> Thanks for the feedback. I'm not sure what you mean with "moving a
>> working
>> group of scheduled files from XP Pro to Windows Server 2003". If you're
>> moving the .job files then you will have to re-enter your credentials for
>> each of them before they will work.
>>
>
> I use a number of different scheduled or spooled report sources for
> example:
>
> Report from system A drops daily to a text file at 4 AM- report from
> system
> B drops daily to an Excel file at 5 AM, Scheduled batch file processes
> report
> from system A. I use both reports as "linked" data sources in an Access
> database. I use Windows Task Scheduler to schedule Docuanalyzer to
> process
> the text file daily with a batch file after it drops and then I run an
> access
> command line firing a macro that runs queries and appends the data to a
> table
> every day.
>
> This is what I meant by a working group of scheduled files.
>
> I edited the batch file replacing the mapped drive letters with UNC names
> of
> the machines and the scheduled file runs now so that was the problem.
>
> I could use a suggestion though on the best method to run scheduled tasks
> in
> Windows Server 2003. Should I just continue to use the task scheduler or
> is
> there a better, preferred method? Can you turn a scheduled task into a
> Service? How?
>
> The Scheduled tasks are all batch files similar to the one described above
> or VBS files generally naming, copying, and/or moving excel spreadsheets.
>
> Thanks for your help.
>
>
>
>
>
>
>> "Jeff C" <JeffC@discussions.microsoft.com> wrote in message
>> news:F5501C2A-6F67-470C-AE43-9BA1A2D4950E@microsoft.com...
>> > Thanks Pegasus - you are correct and I apologize for my redundancy -
>> > I'll
>> > try
>> > your suggestion and also going to try UNC Naming since I am calling
>> > files
>> > from other mapped drives.
>> >
>> > First shot out of the gate though - moving a working group of scheduled
>> > files from XP Pro to Windows Server 2003 and then they don't work gave
>> > rise
>> > to the question.
>> >
>> > I'll post back what I find out. Thanks again
>> >
>> > --
>> > Jeff C
>> > Live Well .. Be Happy In All You Do
>> >
>> >
>> > "Pegasus (MVP)" wrote:
>> >
>> >>
>> >> "Jeff C" <JeffC@discussions.microsoft.com> wrote in message
>> >> news:7E2BCC19-496A-4D68-8DF6-9B31D8E6A646@microsoft.com...
>> >> > Using a program "Docuanalyzer" to process reports with it's command
>> >> > line
>> >> > syntax in a .bat file.
>> >> >
>> >> > "full path to analyzer.exe" "full path to report file" "full path to
>> >> > report
>> >> > model file" "full path and name of output file"
>> >> >
>> >> > I have dozens of these files executing using the Windows Task
>> >> > Scheduler
>> >> > in
>> >> > XP Pro and am now setting up a new machine with Windows Server 2003.
>> >> >
>> >> > The scheduled batch file runs but does not execute. Anyone have a
>> >> > suggestion?
>> >> >
>> >> > Thanks in advance.
>> >> >
>> >> >
>> >> > --
>> >> > Jeff C
>> >> > Live Well .. Be Happy In All You Do
>> >>
>> >> If I had received one Dollar for every post whose author claimed that
>> >> his
>> >> scheduled batch file did not run, I'd be a wealthy man by now . . .
>> >> The
>> >> usual methods in these situations are:
>> >> 1. Post the batch file here.
>> >> 2. Give yourself some eyes so that you can see what's
>> >> going on, e.g. like so:
>> >> @echo off
>> >> echo %date% %time% %UserName% %path% >> c:\test.txt
>> >> "c:\SomeFolder\YourApp.exe" 1>>c:\test.txt 2>>&1
>> >> echo %time% End of batch file >> c:\test.txt
>> >>
>> >> I suspect that c:\test.txt will reveal the nature of your problem.
>> >>
>> >>
>> >>
>>
>>
>>