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.17.04
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.17 Internal Builds
2.0.17.04
- In a complex sequence of events involving locking and renames, it was possible for a lock to not be released. This has been fixed in 2.0.17.4.
2.0.17.03
- An update has been made to the Hub service to check each root path and ensure they are returning Change Journal events. If the Hub detects that Change Journal events are not being returned, the journal will be restarted for the problem Job. This has been fixed in 2.0.17.3.
2.0.17.02
- When scanning a folder, if a [AgentA] is not connected to the Communications Agent of [AgentB], the error occurred multiple times, you could end up receiving messages about "Unable to scan folder after x attempts. Folder must be re-scanned manually." This did not need to be generated because the recovery code would already trigger the proper retry. This has been fixed in 2.0.17.2.
2.0.17.01
- If a lock(s) is created on a remote machine, the connection is lost on the remote machine, the file(s) is closed on the remote machine, and the remote agent is restarted, or the Job times out, the Hub service may send locks back to the remote machine that never got released. This has been fixed in 2.0.17.1.
- When processing file state changes from a scan or journal events, the checkpoint location for events that have been processed may not be properly saved. This would result in unnecessary reprocessing of file states on a Job restart. This has been fixed in 2.0.17.1.