Error: 'Automation.DatabasePlayer.exe' stopped abruptly during execution

🔴 Root Causes – In Order of Likelihood

1. 🔌 Missing or Mismatched Database Driver / ODBC Driver (Most Common)

The DatabasePlayer.exe process loads the database driver (ODBC, JDBC, OLE DB) at runtime. If the specific VM is missing the required driver or has a different version than the working VMs:

• The process loads, attempts to initialize the driver, and crashes immediately with no graceful error.
• This is especially common with:
  • Oracle ODP.NET / Oracle Client not installed on the failing VM.
  • SQL Server ODBC Driver version mismatch.
  • MySQL Connector/ODBC missing.
  • Microsoft Access Database Engine (ACE OLEDB) missing or wrong bitness (32-bit vs 64-bit conflict).

Check:

• Open ODBC Data Source Administrator (odbcad32.exe) on the failing VM.
• Compare the installed drivers against the working VMs.
• Verify the bitness — AA Bot Agent is a 64-bit process, so it requires 64-bit ODBC drivers.
  • Run C:\Windows\System32\odbcad32.exe for 64-bit drivers.
  • Run C:\Windows\SysWOW64\odbcad32.exe for 32-bit drivers.
• Install the missing or matching driver version on the failing VM.

2. 🖥️ Missing or Incorrect .NET Framework / Visual C++ Redistributable

DatabasePlayer.exe depends on specific Microsoft Visual C++ Redistributable and .NET Framework versions. If the failing VM is missing:

• Visual C++ Redistributable 2015–2022 (x64)
• .NET Framework 4.7.2 or higher

The process will crash on startup with no meaningful error in the bot logs.

Check:

• Go to Control Panel → Programs → Programs and Features on the failing VM.
• Compare installed Visual C++ Redistributables and .NET versions against working VMs.
• Install any missing redistributables from Microsoft's official download page.

3. 🛡️ Antivirus / EDR / Security Software Killing the Process

This is a very common cause of *.exe stopped abruptly errors in RPA environments. Enterprise security tools (CrowdStrike, Symantec, McAfee, Defender for Endpoint, etc.) may:

• Quarantine or terminate Automation.DatabasePlayer.exe as a suspicious process.
• Block the process from accessing network resources (database server connections).
• Apply different security policies per VM (explaining why it works on some VMs but not others).

Check:

• Review Antivirus/EDR quarantine logs on the failing VM for any entries related to DatabasePlayer.exe.
• Check Windows Security Event Logs (Event Viewer → Windows Logs → Security) for process termination events.
• Whitelist/Exclude the following paths in the security tool on the failing VM:

  C:\Program Files\Automation Anywhere\Bot Agent\
  C:\ProgramData\AutomationAnywhere\
  

4. 📋 Windows Event Log – Process Crash Details

The most direct diagnostic step is to check the Windows Application Event Log for the crash details:

• Open Event Viewer → Windows Logs → Application.
• Filter by Error level.
• Look for events from source: Application Error with Automation.DatabasePlayer.exe in the description.
• The event will contain:
  • Faulting module name (tells you exactly which DLL caused the crash).
  • Exception code (e.g., 0xc0000005 = Access Violation, 0xc000007b = Wrong bitness DLL).
  • Faulting module path (identifies the problematic driver or library).

⚠️ This is the #1 recommended first step — the Windows Event Log will tell you exactly what crashed and why.

5. 🗄️ Database Connection String / DSN Not Configured on the Failing VM

If the bot uses a DSN (Data Source Name) for the database connection:

• The DSN must be configured on every VM where the bot runs.
• If the DSN exists on working VMs but not on the failing VM, DatabasePlayer.exe will crash when it tries to resolve the connection.

Check:

• Open ODBC Data Source Administrator on the failing VM.
• Verify that the System DSN (not User DSN) used by the bot exists and is correctly configured.
• Test the DSN connection from the ODBC administrator.

6. 💾 Bot Agent Log – Detailed Database Error

As confirmed by the AA Community, the detailed database error can be found in the Bot Agent logs:

"I found DB Error Log in here: C:\ProgramData\AutomationAnywhere\BotRunner\Logs — Check this file: Bot_Launcher_user.log"

Action:

• Navigate to: C:\ProgramData\AutomationAnywhere\BotRunner\Logs\
• Open Bot_Launcher_user.log
• Search for entries around the time of the crash.
• Look for the actual exception/error message (e.g., ORA-xxxxx, JDBC error, driver not found, etc.).

7. 🔒 User Permissions / File System Access

The Bot Runner service account on the failing VM may lack:

• Read/Execute permissions on the DatabasePlayer.exe file itself.
• Write permissions on the temp directory used by the Database package.
• Network access to the database server (firewall rule missing on this specific VM).

Check:

• Verify the Bot Runner service account has the same permissions as on working VMs.
• Test database connectivity from the failing VM using a simple tool like SQL Server Management Studio, DBeaver, or sqlcmd.

✅ Recommended Action Plan

🔬 Quick Comparison Checklist (Failing VM vs Working VM)

📚 References

• AA Database Package Docs: https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/aae-client/bot-creator/commands/database-connect.html
• Bot Agent Logs: C:\ProgramData\AutomationAnywhere\BotRunner\Logs\Bot_Launcher_user.log
• Community Thread (DB Player stopped): https://community.automationanywhere.com/developers-forum-36/the-automation-database-player-has-stopped-working-i-am-getting-this-error-while-executing-bot-10010
• Community Thread (DB Error Logs): https://community.automationanywhere.com/developers-forum-36/how-to-view-detailed-database-error-messages-in-automation-anywhere-91381