"Failed to load the sqljdbc_auth.dll cause : no sqljdbc_auth in java.library.path" 6.0 to 6.7 migration fails

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Unable to upgrade vSphere 6.0 to 6.7 due to failure in migration assistant
• You see the following on the export db logs

Failed to load the sqljdbc_auth.dll cause : no sqljdbc_auth in java.library.path\r\nSet 09, 2019 2:03:13 PM org.apache.tomcat.jdbc.pool.ConnectionPool init\r\nSEVERE: Unable to create initial connections of pool.\r\ncom.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication.

• You have switched from Windows Authentication to SQL Authentication
• ODBC connection tests would be successful, vpxd and invsvc works without issues 

Environment

VMware vCenter Server 6.0.x

Cause

The vcdb.properties file does not get automatically updated, when we change from Windows Authentication to SQL authentication. Since migration assistant uses that vcdb.properties file to obtain the database configuration, it fails to connect because it is expecting integrated authentication instead of SQL authentication.

Resolution

To resolve this issue modify vcdb.properties file and retry the migration.

This file can be located: C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\vcdb.properties 

Process to modify the vcdb.properties files:

Now modify the vcdb.properties files as mentioned below:

from:

driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
dbtype = mssql
url = jdbc:sqlserver://;serverName=Server_Name;DatabaseName=Database_Name;instanceName=Instance_Name;integratedSecurity=True

To

driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
dbtype = mssql
url = jdbc:sqlserver://;serverName=Server_Name;DatabaseName=Database_Name;instanceName=Instance_Name
username=<username>
password=<password>
password.encrypted=fals