I have a scheduled task that runs on my server that should run every 5 minutes 24 hours per day. It seems to run fine for 10 hours or so at a time, but then it will stop and I get the following error message in the log file:"FIDSRefresh.job" (FIDSRefresh.vbs) 10/26/2009 7:46:00 AM ** ERROR **The attempt to log on to the account associated with the task failed, therefore, the task did not run.The specific error is:0x80070569: Logon failure: the user has not been granted the requested logon type at this computer.Verify that the task's Run-as name and password are valid and try again.Does anyone know why this would happen? I'm not sure why the login would be ok for such a long period of time and then just stop working. Any advice would be great. Thanks.

Hi please try following steps. 1. Check and see if the service is running using one of the following methods: 2. Start -> Run -> type 'services.msc' and click OK 3. Scroll down to the 'Task Scheduler' service. 4. Check the 'Startup Type' column. The 'Startup Type' should be set to "Automatic". 5. Check the 'Status' column. If the service is started, it will list 'Started' in the 'Status' column. 6. Click the "Log On" Tab, and verify that "log on as: Local System account" and also select the checkbox of "Allow services to interact with desktop" 7. Please also ensure that the user account is not in the"Logon as a Batch Job"and "Logon as Service" right

If the job connects to another machine you may need to add the user / group 'logon as batch job' rights (server side). Control Panel|Admin Tools|Local Security Policy\Local Policies\User Rights Assignments"Log on as a batch job"If the task completes but the job does not then there is a problem in the job itself. Remember that if it involves network resources to make sure the user account has permissions to the resources and also use UNC paths as mapped drives won't natively exist when no one is logged on.Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]