win2K task scheduler - at system startup

[Guest]

Hi, I've scheduled a console app to run at system startup (not requiring any
logon). However, it seems like it has problems connecting to my local
database server which runs as a service (Interbase 6.0.2).

I don't have any problem if I schedule it to run at logon/any other options.

I don't see the MSTask popup window as well (which I always see) if I
schedule at system startup.

Why the differerences and how can I make my app to work completely with
system startup option? Anything special to look out for with this option??

Pls help!

Thanks...

 

[Pegasus]

Hi, I've scheduled a console app to run at system startup (not requiring any
logon). However, it seems like it has problems connecting to my local
database server which runs as a service (Interbase 6.0.2).

I don't have any problem if I schedule it to run at logon/any other options.

I don't see the MSTask popup window as well (which I always see) if I
schedule at system startup.

Why the differerences and how can I make my app to work completely with
system startup option? Anything special to look out for with this option??

Pls help!

Thanks...

You must schedule the task under an account that has sufficient
privileges to the files/folders that it is supposed to access.

 

[Guest]

You must schedule the task under an account that has sufficient
privileges to the files/folders that it is supposed to access.

Thanks for the reply. But the thing is I've scheduled the task to run under
a user with Admin privileges. And if I were to schedule the task to run AFTER
logon (with the same user), I don't face any problem...

 

[Pegasus \(MVP\)]

Thanks for the reply. But the thing is I've scheduled the task to run under
a user with Admin privileges. And if I were to schedule the task to run AFTER
logon (with the same user), I don't face any problem...

Add some simple diagnostics to your task:

@echo off
echo %date% %time% Start of job > c:\test.log
echo User=%UserName%, Path=%path% >> c:\test.log
c:\tools\SomeJob.exe 1>>c:\test.log 2>c:\test.err
echo %date% %time% End of job >> c:\test.log

Now examine the log files, and all will become clear!

 

[Torgeir Bakken \(MVP\)]

Hi, I've scheduled a console app to run at system startup (not requiring any
logon). However, it seems like it has problems connecting to my local
database server which runs as a service (Interbase 6.0.2).

I don't have any problem if I schedule it to run at logon/any other options.

I don't see the MSTask popup window as well (which I always see) if I
schedule at system startup.

Why the differerences and how can I make my app to work completely with
system startup option? Anything special to look out for with this option??

Hi

Maybe the database service haven't had time to start up yet when your
scheduked task kiks in. Try to e.g. launch a script that adds a
delay first before launching the console app. Or better, let the
script check the service status in a loop to the service status is
reported as running.