Macros Still Running

April 28th, 2010 - 05:00 pm ET by childofthe1980s | Report spam
Hello:

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?

childofthe1980s
email Follow the discussionReplies 11 repliesReplies Make a reply

Replies

#1 Pegasus [MVP]
April 28th, 2010 - 05:11 pm ET | Report spam
"childofthe1980s" wrote in
message news:
Hello:

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?

childofthe1980s



Can't tell unless you post the macros. You need to be aware that most if not
all macros are fragile. They rely on a certain environment (rather than
creating their own environment) and if this environment changes slightly
then they will fail. Humans will readily adapt to such changes but macros
can't. Using properly written scripts would give you a far more robust
solution and probably one that is a lot faster than a macro.

Similar topics