1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Winautomation bots can not run smoothly on VPS

Discussion in 'White Hat SEO' started by asimovgxj, Dec 22, 2015.

  1. asimovgxj

    asimovgxj Junior Member

    Joined:
    Oct 13, 2011
    Messages:
    190
    Likes Received:
    27
    Hey guys,

    Just wondering whether there's Winautomation gurus here... Recently I created a bot on my VPS using Winautomation. When I run the bot with the window of Remote Desktop Connection opened, it run smoothly. But after I closed the RDC ,the bot failed to run and got error messages such as 'failed to get window','failed to click element in window'.

    I guess it's the closing of RDC that lead to missing of mouse and keyboard on the VPS cos there were some mouse actions reg. the bot.How can I settle it down and make the bot run after closing of RDC?

    Thanks in advance.
     
  2. jlamb

    jlamb Newbie

    Joined:
    Dec 22, 2015
    Messages:
    1
    Likes Received:
    1
    I know that a straightforward solution for the specific problem is to use TeamViewer.

    You also need to make sure that the Windows' settings do not include autologging off after a period of idle.
     
    • Thanks Thanks x 1
  3. SethTurin

    SethTurin Jr. VIP Jr. VIP

    Joined:
    Nov 19, 2011
    Messages:
    282
    Likes Received:
    147
    Occupation:
    President and CEO of Seth Turin Media, Inc. - Crea
    Home Page:
    What are you automating on a VPS that needs Windows automation?
     
    • Thanks Thanks x 1
  4. BuildMoreLinks

    BuildMoreLinks Jr. VIP Jr. VIP Premium Member

    Joined:
    Jun 7, 2012
    Messages:
    2,032
    Likes Received:
    684
    may be something got to do with the settings on VPS that's causing problems, have you checked the logs.
     
    • Thanks Thanks x 1
  5. asimovgxj

    asimovgxj Junior Member

    Joined:
    Oct 13, 2011
    Messages:
    190
    Likes Received:
    27

    Thanks for your input but I guess it doesn't matter whether I use TEAMVIEW or not. I need the bot to run automatically everyday on the vps without getting TV or RDC connection.

    And it's not about autologging off either. I tried to minimize the RDC window instead of closing it but the bot still threw error message like "failed to get window" "failed to click element in window".
     
    Last edited: Dec 23, 2015
  6. asimovgxj

    asimovgxj Junior Member

    Joined:
    Oct 13, 2011
    Messages:
    190
    Likes Received:
    27
    I need the bot to visit a webpage ,download the video from the page and then change the name of downloaded video and upload it to my youtube channel. It's kind of a routine daily job.


    Yes I guess it's something related to the VPS. Do you mean the logs of the bot? How to check it? I'm running an .exe file of the bot, don't know how to check the log for it.
    Strange! The bot keep throwing 'failed to get window(firefox browser)' 'failed to click element in window(firefox browser)' after I close the RDC window or after I minimize the RDC window! When I get the RDC window open on my desktop, the bot always work perfectly!
     
  7. asimovgxj

    asimovgxj Junior Member

    Joined:
    Oct 13, 2011
    Messages:
    190
    Likes Received:
    27
    I'm wrong,you're right. The point to use TeamViewer is not to active the rdp-tcp session that will be triggered by RDP window.

    If the rdp-tcp session is not triggered, then the VPS is always controlled by the session of console which offers a persistent active session for the bot. Then the bot will not fail as before when I disconnect RDP which leads to non-interactive of the rdp-tcp session.

    Thank you! You're genius!
     
  8. telim2

    telim2 Regular Member

    Joined:
    Sep 7, 2014
    Messages:
    339
    Likes Received:
    145
    If you use actions in ui/window category of winautomation, your tasks will always pop up error if your session expires. To avoid these scenarior i always try as much as possible to avoid the actions in those category. The easiest way out is to use two RDP, one of the RDP will be used to login to the second RDP in which the winautomation script is going to automate tasks. These will ensures the second RDP sessions never expires even if you logout from the first RDP