I got an odd problem I can not seem to figure out.
I got a macro/exe I built with jitbit.. runs perfectly fine on my home computers when I double click it. Also runs like a champ on task scheduler as well.
I decided to put it on a win2008 x64 box at rackspace and now I'm having issues. When I use RDP to connect to the box and login and double click the exe, it works fine. If I set task scheduler to run and I am actively watching it thru RDP, it runs fine too.
The area it start to fail is, if I disconnect from RDP and task scheduler runs it, task scheduler reports it was successful, but I know it wasn't because it is not collecting data ( its a web scraper ).
This issue isn't with just jitbit exe's, as ubot exe's do the same thing. I've tripled check everything I could and I the only variable is RDP. Everything works when I'm viewing it live on RDP, but doesn't run as expected when I disconnect/close RDP and check on it later.
Another example is one of the jitbit exe's open CMD prompt and types some commands in it and closes itself. This ran in task scheduler while I was off RDP and when I logged in with RDP, I seen the CMD prompt window open, but with no commands inserted into it. Again, this all runs fine double clicked or with task scheduler if I am viewing it all live thru RDP.
Does anyone have the same issue or clue to what is going on?
Thanks for any input you can give.
I got a macro/exe I built with jitbit.. runs perfectly fine on my home computers when I double click it. Also runs like a champ on task scheduler as well.
I decided to put it on a win2008 x64 box at rackspace and now I'm having issues. When I use RDP to connect to the box and login and double click the exe, it works fine. If I set task scheduler to run and I am actively watching it thru RDP, it runs fine too.
The area it start to fail is, if I disconnect from RDP and task scheduler runs it, task scheduler reports it was successful, but I know it wasn't because it is not collecting data ( its a web scraper ).
This issue isn't with just jitbit exe's, as ubot exe's do the same thing. I've tripled check everything I could and I the only variable is RDP. Everything works when I'm viewing it live on RDP, but doesn't run as expected when I disconnect/close RDP and check on it later.
Another example is one of the jitbit exe's open CMD prompt and types some commands in it and closes itself. This ran in task scheduler while I was off RDP and when I logged in with RDP, I seen the CMD prompt window open, but with no commands inserted into it. Again, this all runs fine double clicked or with task scheduler if I am viewing it all live thru RDP.
Does anyone have the same issue or clue to what is going on?
Thanks for any input you can give.