200th task scheduler question

[devilman0]

I have a problem with this one windows xp computer. I have a task that is set to run seti@home when the computer isn't in use. I copied the files and the task from one of the other 3 winxp computers that we have here. This task runs fine on those, but this one, after a period of time, refuses to run. To fix it either i have to restart, or restart the task scheduler service. the log donesn't show anything about usernames/passwords problems. It shows that the task exited normally, in reality, task scheduler starts and stops the task. I have tested this with a bat file in the same task. Deleted/readded the task. Changed usernames/passwords. But nothing seems to keep. I am running trend micro pc-cillin 2003 (if this has anything to do with it) which is the only diff between the other xp machines (pc-cillin 2000). Thanks in advance.

Thanks,
James

"Make it idiot-proof and someone will make a better idiot." ~bumper sticker

 

[bcastner]

Look on your SETI site for information about running SETI as a Service.

That will fix the issue.

 

[bcastner]

Here:

http://www.littlewhitedog.com/reviews_other_00028.asp

 

[bcastner]

The Win2k resource tools you need:

http://www.petri.co.il/download_free_reskit_tools.htm

 

[devilman0]

I've done that, but it does noticably slow the sytems down (the software we use does use a lot of cpu by itself) i would like to have it run only when the computer is idle (this method works on 11 other comptuers in a mixed 2k/xp environment) This is a newer comptuer and for some reason it seems like the task scheduler service is borking somewhere along the line. Thanks for your responses tho.

Thanks,
James

"Make it idiot-proof and someone will make a better idiot." ~bumper sticker

 

[bcastner]

The service only runs during idle cycles. There should be no reason for it to slow down the computer.

 

[devilman0]

I will take another look. What i saw in the past was that it was always running, under lower process, this did cause a problem (lower process or not, it still used cpu)

Thanks again


Thanks,
James

"Make it idiot-proof and someone will make a better idiot." ~bumper sticker

 

[bcastner]

Click on "SETI Driver.exe"
. Set "maximum processes" to "1"
. Set "desired cache size" to "1"
. Make sure the "hide processing box" is checked (default value).
. Set "SETI client priority" to "low"
. "Process monitoring" is at the bottom of the window, make sure the "use SETI Driver" is checked.
. Click on the "save config" button

 

[devilman0]

This is one way to get it to work, but this is just a work around for an underlying problem with task scheduler. I am also considering setting up backups that run on each machine at night, this will only help me with the seti problem. Thanks for your help thus far.

Thanks,
James

"Make it idiot-proof and someone will make a better idiot." ~bumper sticker

 

[bcastner]

See if my answer to the 196th Task Scheduler question does not help: thread779-663445

 

[devilman0]

I think there is a miss understanding here, the task does run with supplied permissions for a lentgh of time (not the same eachtime). Then is seems something happens with task scheduler. No tasks that are definded will work, they start then immeidatly stop. No errors are reported in the log. Just that task started, then stopped. I made a bat file to test this and the scheduler did the same, started, then stoped. It didn't process anything that was in the bat file. To get it to work again (it being task scheduler) i either restart the computer, or restart the task scheduler service to make it start working again.

Thanks,
James

"Make it idiot-proof and someone will make a better idiot." ~bumper sticker

 

[bcastner]

. No blank or empty passwords

Remember that the tasks required to be run and the user given as the task authenticator must match in all permissions or the task will not run without error message.

If I as user create a backup task and schedule it, when the task runs it finds I do not have permissions, or the paths specified require permissions I do not have, or the mapped paths do not exist, the job is rescheduled.

That is the purpose of my earlier link to you. Schedule a shortcut. The shortcut points to a batch file that does all mapping with full permisions. Use the "runas" permission features of scheduled tasks to give a username and password of a user with sufficient rights to access all the files and mapped shares involved. In the batch file rempap using NET USE to make certain all drive letter assignments are correct, or use FQDN as the basis of the map.

What you are describing is a permissions/rights issue.

As a final note, I never edit scheduled tasks. I recreate them. Always works this way, but I have had issues with edited tasks.

 

[devilman0]

How can it be a rights issue when it will run for days, then stop. I can re-enter usernames/passwords and it will still not work until i restart the task service. If this is, how come the other 11 machines aren't experiencing the same problem? They are setup in the same way as this machine (username/password path of the run file). I can't figure out why they work, and this one works then stops, then after i resart the service then does it start to work again (I do not modify usernames/passwords when i restart the service.) I just go to the service control manager, hit restart, open up task schedulser on that computer right click on the tast and hit run and it works.

Thanks,
James

"Make it idiot-proof and someone will make a better idiot." ~bumper sticker

 

[devilman0]

ok here's what i do:

I right click on the task and hit run. Task starts then stops right away, task scheduler reports no error (log or manager) I then open up the services manager, click on the scheduler service, hit restart. Back to the task scheduler, hit run, now it is working. What is happening to make it stop working in the first place. Oh, and it reports that seti is returning 0x80 as the last result.

Thanks,
James

"Make it idiot-proof and someone will make a better idiot." ~bumper sticker