• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 256
  • Last Modified:

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?
0
apitech
Asked:
apitech
  • 3
  • 2
1 Solution
 
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now