MFT Documentation
      Back to home
      1. Software Pursuits Support Center
      2. MFT Documentation

      SureSync MFT Internal Build

      An MFT Internal Build is used to update your MFT environment with the latest fixes not yet available in an official public release.

      SureSync MFT Installer

      The full SureSync MFT Internal Build can be downloaded by clicking here.

      File Name: SureSyncMFTSetup.exe

      Version 2.0.16.07

      To update to the internal build, simply run the installer on each machine in the environment with the Hub or the Communications Agent installed. The steps are the same as performing a regular SureSync MFT Update as outlined in the Updating SureSync MFT KB article.

      Fixes in the 2.0.16 Internal Builds

      2.0.16.07

      • Performance enhancements have been made.  This has been fixed in 2.0.16.7.
      • In rare timing situations, in environments with high levels of activity, a deadlock could occur that would halt processing. This has been fixed in 2.0.16.7.
      • When a delta copy failed, the delta copy was being incorrectly retried instead of falling back to transferring the whole file. This has been fixed in 2.0.16.7.
      • A retry loop that could occur in rare timing related situations was corrected. This has been fixed in 2.0.16.7.

      2.0.16.06

      • A System.NullReferenceException: Object reference not set to an instance of an object error could occur.  This has been fixed in 2.0.16.6.

      2.0.16.05

      • Corrections to rename processing have been made to avoid situations where processing would halt on renamed folders and/or files.  This has been fixed in 2.0.16.5.

      2.0.16.04

      • Performance enhancements have been made to address an issue where files could end up getting delayed in processing longer than they should.  This has been fixed in 2.0.16.4.

      2.0.16.03

      • Performance enhancements have been made.  This has been fixed in 2.0.16.3.

      2.0.16.02

      • File locking corrections have been made.  This has been fixed in 2.0.16.2.

      2.0.16.01

      • If a locked file was opened and closed without an additional change (perhaps because an open copy was performed), it is possible that the lock was released by the Hub service but the updated lock status was never transmitted to the agents.  This has been fixed in 2.0.16.1.