External program failing
Posted: Fri 04 Mar 2016 2:06 pm
I have no idea whether this is a mX problem or not but...
A while back, due to extended power outage that surpassed my UPS capability, MX didn't shut down properly and upon restarting my external program was not updating my website.
It is a vbs that, in turn, invokes a bat that, in turn, invokes WinSCP with parameters.
I found that, if I ran the bat manually, WinSCP worked fine but invoked from MX it didn't.
I played around with it a lot and couldn't get it to run (it is on a 15 sec gap) and then, suddenly, one time after the website showed it hadn't updated for 30 secs and I was about to despair, it worked. So, I gave it no more thought.
Now, I have the same problem (however, my despair doesn't seem to help this time). I was in the process of moving my equipment and mistakenly hit the power button on the power bar so everything shut down. The bat runs fine manually but it fails somehow when invoked from MX. If I run it as a bat from MX instead of vbs I see the dos box open (that's why I run from a vbs to obscure that) and it looks as if the first two files are ftp'd (they aren't) but then the dos box shuts too quickly to see.
Any ideas?
A while back, due to extended power outage that surpassed my UPS capability, MX didn't shut down properly and upon restarting my external program was not updating my website.
It is a vbs that, in turn, invokes a bat that, in turn, invokes WinSCP with parameters.
I found that, if I ran the bat manually, WinSCP worked fine but invoked from MX it didn't.
I played around with it a lot and couldn't get it to run (it is on a 15 sec gap) and then, suddenly, one time after the website showed it hadn't updated for 30 secs and I was about to despair, it worked. So, I gave it no more thought.
Now, I have the same problem (however, my despair doesn't seem to help this time). I was in the process of moving my equipment and mistakenly hit the power button on the power bar so everything shut down. The bat runs fine manually but it fails somehow when invoked from MX. If I run it as a bat from MX instead of vbs I see the dos box open (that's why I run from a vbs to obscure that) and it looks as if the first two files are ftp'd (they aren't) but then the dos box shuts too quickly to see.
Any ideas?