Update 04.06.2025

When upgrading to v7.7.0 or v7.7.1 The dataabase.xml will need the addition of ;encrypt=false added to the JDBC connection string in order to get the GA Windows service running again after upgrade.

Summary:

When running GoAnywhere 7.7.1 and you want to migrate your database using the database migration wizard within GoAnyhwhere you will find that it will error out with the following error: 

Failed to connect to the specified database server.
"encrypt" property is set to "true" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: Invalid server extended key usage. ClientConnectionId:d7df4917-1b6b-4b02-902d-ed910f935f9a

The issue stems from the JDBC driver that is used with GA 7.7.1. To resolve the issue we can rollback to an older version of the driver 
mssql-jdbc-6.4.0.jre7.jar which we can confirm resolves the issue with connectivity between GA and the SQL server. 

Update:(09/05/2025)
 

At the stage where entering the host IP or FQDN you need to add a space and the words “encrypt=false”, this should resolve the issue. If you find this does not work for you please follow the steps below. 

Steps to resolve:

Step 1: 

Stop GoAnywhere service. If you are running GA in a cluster please stop GoAnyhwhere service on both nodes. 

Step 2: 

Rename the JDBC driver for MSSQL present in your installation directory in the “lib” folder. We would advise renaming this to .old at the end so you can rollback should you experience any issue on startup. 

Step 3: 

Place the older JDBC driver mssql-jdbc-6.4.0.jre7.jar in the “lib” directory and restart the services. You should now be able to migrate your database to your chosen MSSQL server. 

Step 4:

Once you have completed the database migration, stop the GoAnywhere service again and rename the newer JDBC MSSQL driver back by removing the .old we placed earlier. Start the GoAnywhere service again.