Skip to main content

Hallo,

my current environment is:

1. AAe 360 on-premise build 23186,

2. Bot Agent version: 22.60.0,

3. MySQL DB to connect to: ver. 5.0.26,

4. JDBC drivers used: old ver: 5.0.2 and new ver: 9.2.0,

5. Connection string: jdbc:mysql://10.31.50.10:3306/samochodyzit?user=<PassString>&password=<PassWordString>.

Issue description: I'm facing issues with connecting to an MySQL ver. 5.026 database using JDBC driver.

When using a new driver ver 9.2.0 i get an error: 'Couldn't connect to data base. CLIENT_PLUGIN_AUTH is required'.

When using an old driver ver 5.0.2 i get an error: 'Driver is not loaded! com.mysql.cj.jdbc.Driver' Screens in the attachment.

 

What could be the solution for this problem? Maybe connection string is incorrect?

Why the proper driver (cer. 5.0.2) couldn’t be found despite it’s attached properly from the file in repository?

 

Any suggestions?

A couple of options:

First, use the 32-bit JDBC driver.

Second, have you tried our User-Defined data source for MySQL?


A couple of options:

First, use the 32-bit JDBC driver.

Second, have you tried our User-Defined data source for MySQL?

Hallo ​@Aaron.Gleason, thanks for quick response,

  1. Which driver did You have in mind? I’ve dwonloaded mine from https://downloads.mysql.com/archives/c-j/
  2. Did You mean using an ODBC driver?

The user-defined connection mode has a preset for MySQL:

You may be able to use this instead of wrangling with a JDBC driver.

Following your link and searching for myself, it doesn’t appear there is a 32-bit JDBC driver for MySQL… or I haven’t found it yet. Give the user-defined mode a try and see if that works.


The user-defined connection mode has a preset for MySQL:

You may be able to use this instead of wrangling with a JDBC driver.

Following your link and searching for myself, it doesn’t appear there is a 32-bit JDBC driver for MySQL… or I haven’t found it yet. Give the user-defined mode a try and see if that works.

Hallo again ​@Aaron.Gleason , of course I\ve tried that method, it failed, not working


I’ve done some research, and hat’s what i’ve found:

DB is pretty old ver. 5.0.26 and the corresponding JDBC driver is 5.0.2 or above and is called: “com.mysql.jdbc.Driver”. The newer drivers are called “com.mysql.cj.jdbc.driver”. That’s why when using an old driver the error message is: ‘Driver is not loaded! com.mysql.cj.jdbc.Drive’, question is why the old driver cannot be used and why Automation Anywhere demands the new driver? On the other hand, when using new driver got stuck with: 'Couldn't connect to data base. CLIENT_PLUGIN_AUTH is required' since the MySQL ver is old and maybe incompatibile with the new driver?

Is there any way to make JDBC driver work with MySQL ver. 5.0.26 in AA360?


Hallo again,

I’ve managed to find a walkaround of the problem: using a MySQL ODBC 32-bit 5.3.13 driver.

The procedure is:

  • Download and install MySQL ODBC 32-bit 5.3.13 driver from https://downloads.mysql.com/archives/c-odbc/,
    • in case of an error (Error 1918. Error installing ODBC driver MySQL ODBC 5.3 Driver, ODBC error 13: The setup routines for the MySQL ODBC 5.1 Driver ODBC driver could not be loaded due to system error code 126: The specified module could not be found. ...\myodbc5s.dll) or an error of missing VC++ redistributable during installation of ODBC driver, Download and install Visual c++ redistributable 2013 (x86 & x64) from https://www.microsoft.com/en-gb/download/details.aspx?id=40784,
  • Having the ODBC driver properly installed, set up an DSN in system ODBC data sources (32-bit):

This DSN should be set-up on every BotRunner host.

  • When establishing connection, use DEFAULT Connection Mode with a connection string:

Driver={MySQL ODBC 5.3 ANSI Driver};Server=<DB Server IP or name>;Database=<Your DB name>;User=<DB User Name>;Password=<DB User Password>;Option=3;

Hope it helps,

greetings MT


Reply