Scheduled Tasks not running due to failed logon credentials.

Basically, our Scheduled Tasks no longer run. However, if you right click on the task and re-enter the service password then perform a manual run the job works&.once. Trying to run the job again creates a Could Not Start error due to incorrect credentials on the service account.

I created another account, same issue. So I always have to enter the same password over and over.

Any ideas on this one?
supportservicesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ehab SalemIT ManagerCommented:
This is a known issue if it is happening on a network drive or a unc.
If this is the case, try to run it on a local drive and see if it works.
0
TekServerCommented:
Have you tried deleting the scheduled task and re-creating it?
0
supportservicesAuthor Commented:

Not yet, looks like I will have to try recreating the tasks. I will let you know what I find.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

supportservicesAuthor Commented:
tried deleting and recreating the tasks from scratch, same issue.

Is there some program out there that will execute a batch file other than windows task scheduler?
0
TekServerCommented:
I have a few more suggestions for you.

First:  make sure that the account you're using to run the scheduled tasks has a password.  Accounts with blank passwords cannot be used to run scheduled tasks.

Second:  make sure the account has "Log on as a batch job" rights.  To check this, open Local Security Settings (in Administrative Tools), expand Local Policies, then click on User Rights Assignment.  Double-click "Log on as a batch job" to see the list of accounts with this right.

If you check these two attributes of the account, and the scheduled tasks still won't run, you might try recreating the scheduled tasks using the AT.EXE command line utility.  This will create scheduled tasks that will run using the System account, which can't be done with Task Scheduler.  Here is a link to a site that describes how to use the AT command:  http://support.microsoft.com/kb/313565

Finally, if that doesn't work, you might try a program called VisualCron.  I haven't used this program; I just found it via a Google search, but it looks pretty good, and I believe it's open source and/or freeware.  Here is the link:  http://www.visualcron.com/

Hopefully one of these will do the trick for you.
:)
0
supportservicesAuthor Commented:
TekServer,

Thanks for the lengthy reply. When I check the Log on as Batch Job, I see all the accounts, however I am unable to add or remove an account. This system is a Windows 2000 DC and I am logged in with the Domain Admin account.

The VisualCron looks great but is not open source or I should say it is not free. But if it is our only alternative we will have to use. At least I get to try it for 45 days and it will work for now however I would rather try your Log On As Batch Job permissions first.

Thanks!
0
TekServerCommented:
Hmmm... This being a DC, you may want to try editing the "Log on as Batch Job" setting in the "Domain Controller Security Policy" rather than the "Local Security Policy".

My apologies on the VisualCron; apparently I didn't look close enough to see that it was in fact a paid solution.  It's still pretty reasonable if it works, though.  As an alternative, here is a link to a project on SourceForge that definitely IS open source, and may suit your needs:

http://sourceforge.net/projects/pycron/

Just a cautionary bit of common sense:  SourceForge projects are generally "works in progress", so I would test it on a non-critical machine if possible before deploying it on a production server.

Hope this helps!
:)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
supportservicesAuthor Commented:
While the issue was not resolved, Visual Cron does work around the issue.
0
TekServerCommented:
Thanks, glad I could help!
:)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.