vRA/vRO 8.8 SQL Connectivity: java.sql.SQLException: No suitable driver found for jdbc:sqlserver

[Garimos]

Hi everyone,

in our vmware environment we are currently observing a strange bug.
When connecting our MSSQL databases, vRA 8.8 does not find the stored plugins or specifically the plugin for the MSSQL database.

Error while adding the Database with "Add Database - Workflow": com.vmware.o11n.plugin.database.DatabaseException: java.sql.SQLException: No suitable driver found for jdbc:sqlserver

ConnctionURL: jdbc:sqlserver://DNS-Name:Port;databaseName=export;authenticationScheme=NTLM;multiSubnetFailover=true;domainName=XXX;integratedSecurity=true

We are using the following Version: Plugin-MSSQL-10/Verion17-05-22/mssql-jdbc-10.2.1.jre8.jar (&Plugin-MYSQL-8/mysql-connector-java-8.0.25.jar)

Current status with the bug:

Our MY SQL databases are displayed without any problems, the connectivity or accessibility of the MS SQL database is not given and were also doesn't see our MSSQL Database in the vRO Inventory.

Previous state:

Both databases (MSSQL & MYSQL) were connected without problems with the affected plugins and were also displayed in the vRO Inventory.

Taken Steps to enable SQL Connectivity:

1. SSH to the vRO appliance as root
2. cd to /data/vco/var/run/vco
3. mkdir -p plugins/SQL/lib
4. Put the MySQL connector into the directory created (/data/vco/var/run/vco/plugins/SQL/lib
5. Open Orchestrator Control Center
6. Go to System Properties
7. Add a new property with the following:

key = o11n.plugin.SQL.classpath
value = /var/run/vco/plugins/SQL/lib/<name_of_connector>.jar

8. Save changes & wait for the server to restart.



root@master-node [ ~ ]# ls -l /data/vco/var/run/vco/plugins/SQL/lib/
total 3740
-rwxr-xr-x 1 root root 1393721 May 17 17:07 mssql.jar
-rwxr-xr-x 1 root root 2428320 May 10 11:57 mysql.jar

 

root@slave-node [ ~ ]# ls -l /data/vco/var/run/vco/plugins/SQL/lib/
total 3740
-rwxr-xr-x 1 root root 1393721 May 17 17:07 mssql.jar
-rwxr-xr-x 1 root root 2428320 May 10 11:57 mysql.jar

 

root@slave-node [ ~ ]# ls -l /data/vco/var/run/vco/plugins/SQL/lib/
total 3740
-rwxr-xr-x 1 root root 1393721 May 17 17:07 mssql.jar
-rwxr-xr-x 1 root root 2428320 May 10 11:57 mysql.jar

vco-controlcenter -> System Properties:
o11n.plugin.SQL.classpath: /var/run/vco/plugins/SQL/lib/mssql.jar; /var/run/vco/plugins/SQL/lib/mysql.jar

Has anyone observed similar errors and if so does anyone know a solution ?

Regards,
Garimos

[pbit_1]

We had a similar issue after the update and recognized, that the o11n.plugin.SQL.classpath property wasn't there anymore after the reboot of the appliances. 

We had to put the entry into "/data/vco/usr/lib/vco/app-server/conf/vmo.properties" and "/data/vco/usr/lib/vco/app-server/conf/vmo-managed.properties" manually, to get the mySQL working again. 

[BenRoc791]

Ever had a solution for this? I face a similar problem, I need a more recent jdbc driver for MSSQL to support AlwaysOn on multisubnet, and the applicant can't find the driver.