Macros Still Running

About a year ago, I successfully programmed Windows Task Scheduler in 2003 to run three macros.  Each of the three macros takes less than five minutes to run.

About a month ago, the macros stopped working.  Each AM, when I check on their status, they still say "Running".  The text report that the macros generate to a shared folder, however, are no longer there.

I have the Admin login logged onto the server.  That is a requirement for automateed macros.  The client says that there is nothing that is logging off the admin.

Is there any good reason why the Task Scheduler macros would stop working like this?
LVL 1
apitechAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

cyberkiwiCommented:
Hi there,

Has the admin password changed?
Right-click in Scheduled Tasks and look at the macro properties.
Near the bottom is the Run As - click on Set Password and reenter the current password
0
apitechAuthor Commented:
No, it hasn't changed actually.  Thanks, for chiming in, though.  Could it be anything else?
0
cyberkiwiCommented:
What shows in the next run time and last run time in the main Scheduled Tasks window?
Status is normally blank, if it says "Running" then it is still running probably from "last run time" and has not terminated.
0
apitechAuthor Commented:
The status is "Running", but here's the thing.  (And, I wish that I had mentioned this in the beginning but I just forgot.)

Since discovering this problem, I conducted some tests.  These macros are scheduled to run at 5AM.  So, in several tests, I changed the run time to a few minutes "from now".  Then, instead of logging off, I hit the "X" in the Remote Desktop connection.

Then, a few minutes later, I log back on to the Remote Desktop connection.  The macros finish successfully!

So, how come these macros run successfully when I test at random, but not when they run at 5AM on their own?

That's why I asked the client if this admin user somehow is getting logged off.  Again, I keep the ID logged on when I hit the "X" in Remote Desktop.  She says that the ID is staying logged on, but I'm not so sure.

What do you think?
0
cyberkiwiCommented:
You can always audit the logon/off events if that is what you suspect

http://technet.microsoft.com/en-us/library/cc787567(WS.10).aspx

TS has an annoying habit of showing the message "session limit expired.. click here to close" after a preset (policy) timeout for inactivity.  That may stop the scheduled task from executing.

It is also possible other tasks (antivirus, machine backup) are preventing the task from completing. If it does say "Running" and the last run time indicates that it did run (as opposed to not starting at all at that time) then something else is preventing it from finishing, not starting.
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
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 Server 2003

From novice to tech pro — start learning today.