Symptoms — Is This Article for You?

• ❌"Database Check Error: Failed to validate the database we cannot continue with the upgrade. If you feel you need guidance, contact Ipswitch / Progress Technical Support."

• Function returned : Error|ErrorCheckingDatabase|Unable to connect to the database: MOVEitTech.MySQL.Connect: Could not connect to database.
• Error: Failed attempting to check the database.
• Function returned : Error|ErrorCheckingDatabase|Unable to convert database type string 'image' to data type.

• Testing the database connection from the MOVEit Config Utility works fine, and database reports/functions operate normally — only the upgrade installer fails.
• You are using a MySQL database (this error is most commonly associated with MySQL).

ℹ️ Not your issue? If your install log shows Error: File is locked or Error: Failed requirement: Another application has requested a reboot, your problem is not a database validation error. See the Troubleshooting table below and Installation errors for Failed to unregister assembly for several DLLs upgrading

Important — Before You Begin

• ✅ Server reboot state is clear: Check HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations in the registry — if this key has entries, reboot the server before attempting the upgrade.
• ✅ No processes are locking MOVEit DLLs: Open Task Manager and end any ReportErrors, TableCleanup, or other processes holding files in C:\MOVEitTransfer\COM\. If unsure, reboot the server.
• ✅ Installer version is correct: If targeting version 18.0.x, use the 18.0.2 or later installer — versions 18.0.0 and 18.0.1 contain a known defect that causes this error.
• ✅ You have admin access to the MOVEit Transfer server, the Local Group Policy Editor (gpedit.msc), and the MySQL database.

1. "The database connection test passes, so the database is fine." — The Config Utility test uses a different connection path than the installer. A TLS timeout during the upgrade's certificate validation can fail even when normal DB connectivity works.
2. "The 18.0.2 workaround applies to all versions." — The 18.0.0/18.0.1 installer defect fix only applies if you are upgrading to those specific versions. For other versions, use the TLS resolution (Method A) or data-type fix (Method B) below.
3. "TableCleanup locking files is a database error." — If the install log mentions locked .dll files (not database errors), your issue is process-related, not database-related. Stop the locking processes and retry.

The primary cause is a TLS timeout during the installer's database validation step — Windows attempts to auto-download root certificates, and the connection times out before succeeding. A secondary cause is non-MOVEit tables in the database containing data types the installer cannot parse. In versions 18.0.0 and 18.0.1, a product defect also triggers this error (fixed in 18.0.2).

If the 2026.0.0 or 2026.0.1 (18.0.0 or 18.0.1) installers are being used, upgrade to the 2026.0.2 (18.0.2 version) or later to avoid the defect mentioned above. Otherwise...

Choose Your Method

Method A — Disable Automatic Root Certificates Update (TLS Timeout Fix)

1. Open Local Group Policy Editor: Press Win + R, type gpedit.msc, and press Enter.
2. Navigate to the certificate setting: Expand: Computer Configuration > Administrative Templates > System > Internet Communication Management > Internet Communication settings.
3. Disable automatic root certificate updates: In the details panel, double-click"Turn off Automatic Root Certificates Update", select Enabled, then click OK.

   ⚠️ This change takes effect immediately — no restart required. Remember to reverse this setting after the upgrade if your organization's security policy requires automatic root certificate updates.

4. Re-run the MOVEit Transfer installer from the desktop of the MOVEit server, running as administrator. The database check error should no longer occur.
5. Verify: Confirm the upgrade completes without the "Database Check Error" dialog. Check the install log for a successful completion entry (no ErrorCheckingDatabase lines).

---

Method B — Remove Non-MOVEit Database Tables (Data-Type Error Fix)

1. Identify the offending data type: Open the install log and find the line: Unable to convert database type string '<type>' to data type. Note the type in quotes (e.g., image).

If there are error messages such as these in the install logs: 

18:46:27 Calling the function
 18:46:27 Function returned : Error|ErrorCheckingDatabase|Unable to convert database type string 'image' to data type.
 18:46:27 Error: Failed attempting to check the database.
 18:46:27 Showing message box. Message:
 Database Check Error: Failed to validate the database we cannot continue with the upgrade.
 If you feel you need guidance, contact Ipswitch Technical Support.

Then this means that there is a column with that datatype that is stopping the upgrade. 

1. Query for non-standard tables: Connect to the MOVEit MySQL database and run:
   SELECT * FROM INFORMATION_SCHEMA.COLUMNS

   WHERE DATA_TYPE LIKE '%[image]%'

   ORDER BY TABLE_NAME;

    
   Replace [image] with whatever type string appeared in your log.
2. Remove non-MOVEit tables: If the results include tables that are not standard MOVEit tables (e.g., dbo.trace1 or other DBA-created troubleshooting tables), remove them.

   ⚠️ Do not remove standard MOVEit tables. If you are unsure whether a table belongs to MOVEit, contact Progress Technical Support before deleting.

3. Re-run the upgrade installer and verify it completes successfully.

Troubleshooting — Common Issues After Upgrade Attempt