Skip to main content
Question

Python Script getting URL error

  • November 14, 2025
  • 1 reply
  • 34 views
M
Forum|alt.badge.img
  • MIDWB
  • Ground Control | Tier 1

I created a bot that executes a Python script.  This script opens a Chrome browser, loads the URL, downloads 5 rate reports from that web site, then loads those reports to SAP.  When I run the Python script locally using IDLE, it works fine.  When I call the function using AA 365, Chrome opens, but the URL is not populating.  I’m using Python 3.9 and I’ve installed all the necessary libraries for the script to run.  
We currently run this bot on a VDI and this bot works fine but we are trying to switch over to running on a server VM.   The VM is where I’m seeing this error.  Can someone give me some ideas on what could be going on?     

 

here is the error that is being logged in the Bot Launcher Log file:

ERROR - Message: session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause.; For documentation on this error, please visit: 

    1 reply

    Padmakumar
    Premier Pathfinder | Tier 7
    Forum|alt.badge.img+15
    • Padmakumar
    • Premier Pathfinder | Tier 7
    • November 15, 2025

    Hi ​@MIDWB,

     

    The error means Chrome closed immediately after chromedriver tried to start a session — not an AA bug but an environment/driver mismatch or permission/launch issue. You may check the below points.

     

    - Verify Chrome ↔ ChromeDriver version match exactly (chromedriver must support the installed Chrome build).  

    - Inspect the ChromeDriver verbose log (the error advises this) for the real root cause; it will show missing DLLs, bad flags, or exit code.  

    - Confirm Chrome is installed and reachable by the user account the Bot Launcher/Runner uses; test launching Chrome from that same account/interactive session.  

    - Check chromedriver path and that AA is using the same Python interpreter and driver you use locally.  

    - If running on a Linux VM or headless server, ensure a display server (Xvfb) or use headless mode and add flags: --no-sandbox, --disable-dev-shm-usage, --disable-gpu (and consider --headless=new).  

    - For Windows VMs, ensure Desktop Interaction is enabled for the service/runner and that the session isn’t locked; confirm permissions to create processes.  

    - Confirm any required browser dependencies/libraries are installed on the VM (common on minimal server images).  

    - Reproduce the failure manually on the VM (run your script from the same environment the bot uses) and capture chromedriver verbose output for definitive clues.

     

    Padmakumar
    Terms & ConditionsCookie settingsAccessibility statement