How to troubleshoot MFT Installation Failed with Error 1015: LocalDbInstance Creation Issue?

This error is specifically related to Microsoft SQL Server Express LocalDb. It often occurs due to remnants of a previously installed LocalDb instance that was not fully removed.

Symptoms:

• Installation fails with Error 1015.

• Logs show authentication attempts using an SFTP username during the installation MSI process.

• Previous uninstallation attempts

• Root Cause: Residual files and registry entries from a previously installed LocalDb instance prevent the creation of a new LocalDb instance during MFT installation.

Solution:

Perform a thorough manual cleanup of the LocalDb remnants by following these steps:

1. Remove Configuration Backups

• Delete the following folders if they exist:

  • C:\Users\<installing user>\AppData\Roaming\OPSWAT\MetaDefender Managed File Transfer\backup
  • C:\Users\<installing user>\AppData\Roaming\OPSWAT\MetaDefender Vault\backup

• If an elevated user account was used during installation, repeat this step for that user as well.

2. Remove Database Files

2.1 General File Cleanup:

• Delete any database files related to MFT, including:
  • sft_data.mdf
  • sft_data.ldf
  • sft_conn.mdf
  • sft_conn.ldf

2.2 If Using SQL Server or Windows Authentication:

• Check the SQL Server Data folder for any residual MFT-related database files and delete them.

2.3 If Using LocalDb:

• Check the following folders for leftover databases and delete any found:

  • C:\Windows\System32\config\systemprofile
  • C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\sftdb
  • C:\Windows\SysWOW64\config\systemprofile
  • C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\sftdb

• Delete any empty folders named vault in the paths above.

• If using a third-party file browser (e.g., Total Commander), ensure you run the x64 version with administrator privileges.

3. Cleanup Registry Keys

3.1 Remove MFT-Related Registry Keys:

• Delete these registry keys (open regedit):
  • HKEY_LOCAL_MACHINE\SOFTWARE\OPSWAT\MetaDefender Managed File Transfer
  • HKEY_LOCAL_MACHINE\SOFTWARE\OPSWAT\MetaDefender Vault

3.2 Remove Stuck Windows Installer Keys (if MFT still appears under installed programs):

• Open regedit and search for the following keys:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{78b91f88-e354-4f45-9662-XXXXXXXXX}

    • DisplayName: MetaDefender Managed File Transfer or MetaDefender Vault

  • HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX}

    • DisplayName: MetaDefender Managed File Transfer or MetaDefender Vault

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX}

    • BundleUpgradeCode: 220ec284-c7dc-4231-ba04-4007e3ccd965

4. Cleanup Leftover Files

• Delete the MFT installation directory if it exists, e.g.,:
  • C:\Program Files\OPSWAT\MetaDefender Managed File Transfer

Recommended Action:

Perform the above cleanup steps to ensure the complete removal of LocalDb remnants and MFT files before reattempting the installation.

Additional Notes:

• Avoid using third-party uninstallers for LocalDb removal. The default Windows uninstallation can also remove LocalDb, though it may not always be sufficient to resolve this specific issue.

• These steps are recommended if a standard uninstallation did not resolve the issue or if the previous installation status is unclear.

• This KB article applies to MFT versions prior to 3.8.0, which introduced a clean installation feature.