@Nibedita Dey​ :

It is supported but the issue might occur when you call the same bot multiple times.1st-time run is successful in the loop. But for the second iteration, the bot will fail.

Link: https://apeople.automationanywhere.com/s/article/Bot-is-getting-stuck-in-connect-command-line

if you are still facing an issue then please create a support case

How to create a support case :

https://apeople.automationanywhere.com/s/article/How-to-create-a-support-case-in-service-cloud

if you don't have access to the above link, email the AA Support team "apeopleopsteam@automationanywhere.com" to get access.

Has this been fixed in v26????

@Nibedita 

Instructions

• Automation Anywhere Enterprise database command is not able to connect with 64-Bit data provider as it is only compatible with 32-bit data provider.
• But if you want to connect with any 64-Bit data provider you must follow below steps to successfully configure 64-bit data provider connection:
  •  Download the Microsoft access database engine 2010 in 32 bit from URL below
    • https://www.microsoft.com/en-us/download/details.aspx?id=13255
  • Navigate to C:\Windows\System32 or C:\Windows\SysWOW64 folder and open odbcad32.exe
  • When we open odbcad32.exe it displays all 64-bit connection type as per operating system behavior.
  • Create new connection on System DSN and specify 64-bit data provider.
  • Verify connection with test connection button and specify system DSN name.
  • Open Automation Anywhere Task Editor and select database command.
  • Select Microsoft OLE DB Provider for ODBC Driver and configure system DSN connection.
• Verify the connection it should work with database command.

This is not true at all. It depends solely on these factors (assuming that your A360 version is v26 or v27):

• If the bot runner VM has M365 32-bit installed, this will inherently install the Microsoft Access Database Engine 2016 Redistributable, which is fully compatible with A360 (v26 build 15436 or higher) (link)
• If you are using v27, this supports 64-bit ODBC driver in Database package (link)

If you are running A360 v25 or lower, then you must use the Microsoft Access Database Engine 2010 Redistributable in all cases