Macros Still Running
in [Windows Servers]
|
From: childofthe1980s on 28 Apr 2010 17:00 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
From: Pegasus [MVP] on 28 Apr 2010 17:11 "childofthe1980s" <childofthe1980s(a)discussions.microsoft.com> wrote in message news:436D04D1-E1E4-47EB-B787-14F6D49622C6(a)microsoft.com... > 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.
From: childofthe1980s on 28 Apr 2010 19:48 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? "Pegasus [MVP]" wrote: > > > "childofthe1980s" <childofthe1980s(a)discussions.microsoft.com> wrote in > message news:436D04D1-E1E4-47EB-B787-14F6D49622C6(a)microsoft.com... > > 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. > > . >
From: Pegasus [MVP] on 29 Apr 2010 01:02 Sorry, can't comment without knowing a lot more about those elusive macros. "childofthe1980s" <childofthe1980s(a)discussions.microsoft.com> wrote in message news:8D198654-03CF-42F3-97F2-8F4C16B72551(a)microsoft.com... > 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? > > "Pegasus [MVP]" wrote: > >> >> >> "childofthe1980s" <childofthe1980s(a)discussions.microsoft.com> wrote in >> message news:436D04D1-E1E4-47EB-B787-14F6D49622C6(a)microsoft.com... >> > 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. >> >> . >>
From: DaveMills on 29 Apr 2010 01:09
As Pegasus said you need to show us the macros. This sort of issue is often because the macro is dependant on things like mapped drives. It may be prompting for input etc. On Wed, 28 Apr 2010 16:48:01 -0700, childofthe1980s <childofthe1980s(a)discussions.microsoft.com> wrote: >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? > >"Pegasus [MVP]" wrote: > >> >> >> "childofthe1980s" <childofthe1980s(a)discussions.microsoft.com> wrote in >> message news:436D04D1-E1E4-47EB-B787-14F6D49622C6(a)microsoft.com... >> > 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. >> >> . >> -- Dave Mills There are 10 types of people, those that understand binary and those that don't. |