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

      SureSync MFT Version History

      This article includes details about fixes and enhancements made to each version of SureSync MFT.

      Known Issues in All Versions

      This section has known issues that cross versions, such as conflicts with other software products or system requirements.

      Required Microsoft Components

      SureSync MFT requires current Microsoft technologies as outlined on the SureSync MFT System Requirements page. The installer will check to see if your system meets these requirements. If it does not it will offer to install them for you.

      Zip Magic

      If you are using ZipMagic to handle your zip files and are allowing ZipMagic to display zip files as folders, SureSync MFT will be unable to copy those files. If you turn off ZipFolders then the files will copy as expected.

      In order to display the zip files as folders, ZipMagic must somehow intercept the standard actions such as opening a file and reissue them as if you were working with a folder. This command change prevents SureSync from being able to properly open, copy and rename files.

      It is our guess that the makers of ZipMagic recognize this issue. There are two ways to circumvent this issue. You can turn off ZipFolders for SureSync MFT only or you can turn off ZipFolders during the time you run your synchronization.

      To turn off the ZipFolders for SureSync MFT’s file synchronization engine. You can open the ZipMagic control panel, select the ZipFolders
      choice, and go to Applications. Click ‘Add’ on the Control Panel and browse to your SureSync folder and choose SPIFiles.exe from the file list. Then click ‘Add’ on the Add New Application dialog. Click ‘Done’ and ‘OK’ to save the new settings.

      Or to turn ZipFolders off at a specific time, you can open the ZipMagic control panel, select the ZipFolders choice, and go to
      Schedule it allows you to schedule times for the ZipFolder option to be disabled. The text on the panel says “this can be useful for automatic activities done overnight”. This implies that SureSync is not the only product that can not work with the ZipFolders feature on.

      Note: The only files that SureSync will not copy if ZipFolders is turned on are the zip files. All other files should copy normally.

      Return to top of page

      Known Issues in the Latest Version (2.0.5)

      Version 2.0.5 was posted on April 23, 2024.

      This version contains all patches to previous versions as well as new fixes and features.

      All issues listed for prior versions have been resolved.

      There are no patches issued for this version at this time.

      We will report known issues as they come up.

      If you have any problems not listed here, please contact our Support Team.

      Return to top of page

      SureSync MFT 2.0.4 Known Issues

      Version 2.0.4 was posted on March 17, 2024.

      • Changes have been made to increase the maximum number of state and folder scans allowed on the Hub machine. The amount will differ depending on the capabilities of the server running the Hub. In Options, on the General tab, there are options to increase further or reduce the number of actions allowed at once. This has been fixed in 2.0.5.
      • A file could be copied a second time unnecessarily, resulting in an add and a replacement. This has been fixed in 2.0.5.
      • A path recovery message could be logged twice for the same recovery event. This has been fixed in 2.0.5.
      • A System.NullReferenceException error could occur. This has been fixed in 2.0.5.
        In the Local Communications Agent Configuration Utility, if you changed the listen port, the "Save" and "Cancel buttons would not enable. This has been fixed in 2.0.5.
      • Skip Rules were not being applied to lock processing, so a lock would still be established on a file within a skipped folder. This problem did not occur with a rule subfolder definition on the Copy Files rule. This has been fixed in 2.0.5.
      • A state scan could wait on a folder scan and not be processed. This has been fixed in 2.0.5.
        Our journal processing code should discard self-generated events. This was not matching entries for archive files, possibly generating a database error. The list of self-generated events was also not being properly purged, allowing it to grow unnecessarily large. This has been fixed in 2.0.5.
      • Additional retries have been added to address an "unexpected error when transmitting from ServerA to ServerB System.ServiceModel.CommunicationObjectAbortedException: The communicationobject,System.ServiceModel.Security.SecuritySessionClientSettings`1+ClientSecurityDuplexSessionChannel[System.ServiceModel.Channels.IDuplexSessionChannel], cannot be used for communication because it has been Aborted" message that could occur. This has been fixed in 2.0.5.
      • In rare timing circumstances, a file database record could end up with a flag indicating it was a folder. This has been fixed in 2.0.5.
      • When a file was copied into the SureSync MFT tmp folder, it was inheriting permissions at that level. When the file was renamed to the final location, that renamed copy was not inheritting permissions again. If the permissions on the subfolder were different from the permissions on the root path, this would result in security not being correct on the final location copy. This has been fixed in 9.0.20.

      SureSync MFT 2.0.3 Known Issues

      Version 2.0.3 was posted on January 31, 2024.

      • A deadlock could occur, halting processing until the Hub service was restarted. This has been fixed in 2.0.4.
      • Changes have been made to correct issues with file and folder renames that happen in certain complex sequences. This has been fixed in 2.0.4.
      • Issues with renames where archive paths or backup roots were involved were corrected. This has been fixed in 2.0.4.
      • It was possible for a rename to be queued, but before it was processed, a new event would arrive with the old name, causing issues with the rename. This has been fixed in 2.0.4.
      • A "cannot create a file when that file already exists" error could occur when a rename occurred on an offline path. This message would occur when the path recovered, and the rename was performed on the other paths. This has been fixed in 2.0.4.
      • A journal checkpoint would not always be saved correctly, causing actions to be replayed. This is inefficient and could result in "cannot create a file when that file already exists" errors being reported. These were harmless but should not have occurred. This has been fixed in 2.0.4.
      • Some of the counters displayed in Detailed Status or Enterprise Status could incorrectly show negative numbers. This has been fixed in 2.0.4.
      • In environments with file locking, when a locked file was closed, it was given priority in the queue. This created situations where those copies blocked lower-priority copies from completing. This has been fixed in 2.0.4.
      • In certain timing situations, tracking priority actions was incorrect. The counts would be incorrect, resulting in only priority actions being processed. This would make the job appear to hang or stop processing pending changes. This has been fixed in 2.0.4.
      • In certain timing situations, when a Job was enabled, it could sit on a "draining change journal" message and not advance. This has been fixed in 2.0.4.
        Jobs with defined backup root paths could corrupt the database's file history records. This has been fixed in 2.0.4.
      • When a Job had overlapping root paths with another Job, a 'severe error while generating actions system alert could be generated. This has been fixed in 2.0.4.
      • Jobs with back root paths could stop processing actions. This has been fixed in 2.0.4.
      • When a Job had overlapping paths with another Job. the Job could get stuck on "waiting for renames or deletes." This has been fixed in 2.0.4.
      • A performance improvement has been made to the full scan process when a job runs the first time. It would reach the end of the process and show a "processing file changes for all jobs" message where it would do some unproductive processing. This has been fixed in 2.0.4.
      • A "System.NullReferenceException" could occur, which would halt processing. This has been fixed in 2.0.4.
      • If a folder rename encountered an access denied situation, it could slow overall Job processing because renames have to wait for actions to complete before proceeding. An access denied on a rename will no longer cause these delays. This has been fixed in 2.0.4.
      • In an environment with file locking enabled, it was possible to have a file locked on one machine and a file rename queued on a different machine. This would require that the Hub was stopped with the rename queued. In that case, the rename would be delayed by the lock. The delayed rename would block scans. This would prevent scans from running and appear like a deadlock where changes were not processing. This has been fixed in 2.0.4.
      • A deadlock could occur, halting the Hub processing changes until the Hub service was restarted. This has been fixed in 2.0.4.
      • Queued counters displayed in Enterprise and Detailed Status could be incorrect, indicating there are queued actions to be performed when there aren't any. This has been fixed in 2.0.4.

      SureSync MFT 2.0.2 Known Issues

      Version 2.0.2 was posted on January 19, 2024.

      • In rare circumstances, a journal event for a file close could not be processed. This would cause a lock to remain waiting for the file to be copied. This has been fixed in 2.0.3.
      • Corrections have been made to truncate delete processing. This has been fixed in 2.0.3.
        A job running with a Schedule might display that it is idle and waiting for changes instead of terminating the current step in the Schedule. This has been fixed in 2.0.3.
      • When a new machine is added along with a new Job, the new machine might be placed in a "disabled" state because it was not evaluated for licensing. The new Job would repor the volume on that machine as "offline." The machine would be reported as properly licensed if the Hub was restarted or some other action was taken. This has been fixed in 2.0.3.
      • Wild card searches in File Status for the File Name Filter field on a Query were not working correctly. This has been fixed in 2.0.3.
      • Databases created in 2.0.1 or 2.0.2 were found to be missing some SQL indexes, which could negatively impact performance. If these indexes are missing from the MFT database, they will be added. This has been fixed in 2.0.3.
      • If a Schedule has a pending state and that Schedule is not running, the Hub service may keep attempting to start the scan for the Job, consuming unnecessary CPU resources. This has been fixed in 2.0.3.

      SureSync MFT 2.0.1 Known Issues

      Version 2.0.1 was posted on January 12, 2024.

      • If a remote agent is rebooted, the Hub service may not recognize the change. It could attempt to continue reading from the Change Journal. That attempt would fail, but the Hub failed to re-initialize the journal processing. This would cause a 2nd failure. The Hub would continue to report an error and fail to recover the path. This has been fixed in 2.0.2.

      SureSync MFT 1.0.29 Known Issues

      Version 1.0.29 was posted on November 23, 2023.


      IMPORTANT: SureSync MFT 2.x requires running a database conversion utility to move the database to the new v2 level. This conversion must be done with the Hub stopped and all Jobs disabled. Please visit https://support.softwarepursuits.com/upgrading-to-suresync-mft-v2 for full instructions.

      • Performance improvements have been made, particularly when many Jobs have root paths that share the same volume on a server. These changes will allow all Jobs to run more independently with fewer items blocking processing on the Hub. This has been fixed in 2.0.1.
      • An action could be queued with a source FileState that no longer exists. This would lead to an "Error while loading pending file actions from the database. System.NullReferenceException: Object reference not set to an instance of an object" error. This has been fixed in 2.0.0.1.
      • Enterprise Status has been enhanced with the ability to multi-select Jobs and perform stop/start actions on the set.  This has been fixed in 2.0.1.
      • Corrections have been made to the process of changing the Hub from one machine to another. This has been fixed in 2.0.1.
      • If two Jobs had overlapping paths where one Job had file locking enabled and the other did not, the file locking on the one Job would not always be initialized correctly. This has been fixed in 2.0.1.
      • A ‘System.Data.ConstraintException: Column ‘AgentConfigId’ is constrained to be unique.’ message could occur when clicking on the ‘Update Agent Configuration’ button for an agent.  This has been fixed in 2.0.1.
      • Tracing enhancements have been made. This has been fixed in 2.0.1.
      • A ‘NullReferenceException error could occur on a test connection.  This has been fixed in 2.0.1.

      SureSync MFT 1.0.28 Known Issues

      Version 1.0.28 was posted on November 12, 2023.

      • Corrections have been made to internal caching, representing a significant performance improvement. This has been fixed in 1.0.29.
      • Corrections have been made to the initialization of file locking when there are multiple UNC paths on a volume. This has been fixed in 1.0.29.
      • File Locks established on remote agents would have a 4-second delay before arriving at the Hub for processing to allow batching of requests. This time has been reduced to 2 seconds. This has been fixed in 1.0.29.
      • General performance improvements have been implemented. This has been fixed in 1.0.29.

      SureSync MFT 1.0.27 Known Issues

      Version 1.0.27 was posted on October 26, 2023.

      • When a server got very busy with actions, other actions could be delayed until active dropped. Recognition that the activity level dropped may be extended longer than necessary, which could cause a job to sit with ready actions and no actions being processed. This has been fixed in 1.0.28.
      • When defining a root path that is a root drive letter, a System.NullReferenceException error would occur that would cause scans to be blocked and halt processing. This has been fixed in 1.0.28.
      • In rare timing situations, when a Job was enabled, the volumes would not get initialized. This would leave the Job in the initializing state (yellow dot icon in the Desktop) until it was disabled and enabled again. This has been fixed in 1.0.28.
      • Significant performance improvements in the caching routines have been implemented. This has been fixed in 1.0.28.
      • Corrections to security copy processing have been implemented. This has been fixed in 1.0.28.

      SureSync MFT 1.0.26 Known Issues

      Version 1.0.26 was posted on October 17, 2023.

      • Some indexes in the database will be updated on the first launch of the Software Pursuits SureSync MFT Communications Agent service on the Hub machine to address some performance issues. The easiest way to know if the database update is completed is to use Enterprise Status. Enterprise Status will display that it cannot connect to the Hub service, but it will retry until it gets a connection. That is when you will know the update is complete and the MFT Desktop can be used. Launching the MFT Desktop before the update will not hurt anything but could cause the update to be attempted twice, slowing down the initialization. This has been fixed in 1.0.27.
      • In some instances with folder renames, a folder scan could be waiting for a rename, and the scan would not start when the rename finished. This would cause the Job to sit with a message in Detailed Status of "x state scans waiting on a folder scan." This has been fixed in 1.0.27.
      • Duplicate file copies could be queued. This has been fixed in 1.0.27.
      • When actions were retried with scans with file locking enabled, it was possible to have locks not be released when the retried scan occurred. This has been fixed in 1.0.27.
      • Performance improvements have been implemented. This has been fixed in 1.0.27.

      SureSync MFT 1.0.25 Known Issues

      Version 1.0.25 was posted on October 3, 2023.

      • Performance improvements have been implemented. This has been fixed in 1.0.26.
      • The file size for a file might be stored incorrectly in the database. This will normally trigger a file copy, but the copied file size will not match the expected file size and a new copy will be triggered. This has been fixed in 1.0.26.
      • A folder scan may not update the FileState record for a file, correcting a possibly incorrect value, if the cache entry was recently loaded while scanning. This has been fixed in 1.0.26.
      • Code has been added to prevent FileState records from being incorrectly saved with a ParentFolderID=0. This has been fixed in 1.0.26.
      • When rapid changes were occurring, it was possible for events to be missed in rare timing circumstances. It is recommended to perform a rescan on Jobs to ensure that no events were missed. Rescans should be performed one Job at a time to minimize the impact of the scanning on other processing in the environment. This has been fixed in 1.0.26.
      • A scan of a file could occur while that file was actively being copied. The FileState records were not being properly coordinated, and a new file copy could be attempted resulting in a "cannot create a file when that file already exists" message being logged. This has been fixed in 1.0.26. 
      • An old Change Journal checkpoint could fail to update for a Job when other Jobs were run. This could cause unproductive duplicate processing of events the next time the Job was started. This has been fixed in 1.0.26.

      SureSync MFT 1.0.24 Known Issues

      Version 1.0.24 was posted on September 29, 2023.

      • Jobs with Backup Roots were experiencing database corruption. This new build corrects the issue and will repair the database on the initial Hub start after the update. This process may take up to 15 minutes to complete. Please wait 15 minutes after updating the Hub to allow the repair to take place. This has been fixed in 1.0.25.

      SureSync MFT 1.0.23 Known Issues

      Version 1.0.23 was posted on August 29, 2023.

      New Feature: MFT now supports real-time processing of UNC paths. There are some limitations. File locking is not available. Each time the Job is started, or when a path loss occurs on the UNC path, the entire path must be rescanned because there is no Change Journal support. It must be assumed that an event could have been missed, necessitating the full scan.
      • A “System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it” error could occur in the browse panel when adding a Root Path. This has been fixed in 1.0.24.
      • A “System.NullReferenceError” could occur during rename processing. This has been fixed in 1.0.24.
      • The Hub could stop processing with actions waiting for a priority action to complete that was not actually busy. This would make the Hub stop processing changes until a restart of the Hub. This has been fixed in 1.0.24.
      • In environments with multiple Jobs processing data in different folders on the same volume, Jobs could incorrectly wait on renames occurring in other Jobs. This would cause unnecessary processing delays. This has been fixed in 1.0.24.
      • Optimizations have been made to rename processing. This has been fixed in 1.0.24.
      • In rare instances, a state change could occur before a folder scan. This would cause a database error for a missing FileID on a new Job. This has been fixed in 1.0.24.
      • A “SqlTypeException: SqlData.SqlTypes.SqlTypeException: SqlDateTime overflow.” error could occur while attempting to stop journal processing for a root path. This has been fixed in 1.0.24.
      • In environments with a heavy volume of renames occurring, a backlog of changes could build while waiting for rename processing to complete. Changes have been made to better handle the backlog of change events in these situations. This has been fixed in 1.0.24.
      • The first time a Job was enabled that referenced a new machine, the license validation process could loop and cause the Hub service to be stopped. This has been fixed in 1.0.24.
      • In a new database, the first Job that was enabled could incorrectly report paths offline. The paths would process successfully regardless of the warning. This has been fixed in 1.0.24.
      • It was possible for checkpoints to not be correctly saved. This would cause unproductive compares when a Job was disabled and enabled again. This has been fixed in 1.0.24.
      • A NullReference error could occur when a path was dropped. This has been fixed in 1.0.24.
      • It was possible for the queued state scan counter to display a negative number. This has been fixed in 1.0.24.
      • It was possible for change event processing to become degraded. A checkpoint was being written for every change, slowing processing significantly in some situations. This has been fixed in 1.0.24.
      • In some circumstances, a Rule change would fail to trigger a rescan. This has been fixed in 1.0.24.

      SureSync MFT 1.0.22 Known Issues

      Version 1.0.22 was posted on July 10, 2023.

      • History in the database was not always being marked properly to determine if a history record was related to a folder or a file. This has been fixed in 1.0.23.
      • Improvements have been made to processing queued changes, especially delayed changes. Renames were not always assigned priority. This has been fixed in 1.0.23.
      • It was possible for a deadlock to occur between a queued folder scan and retries of a folder delete where the folder was not empty, which would stop the Job from processing. This has been fixed in 1.0.23.
      • The Hub service could stop with an “Index was out of range. Must be non-negative and less than the size of collection” error in rare instances where an event was being processed that did not reference any online root paths. This has been fixed in 1.0.23.
      • Performance improvements have been made to the processing of events when there are many thousands of changes pending and many renames pending. Fewer events should be delayed, and processing should be faster in these situations. This has been fixed in 1.0.23.
      • A change was made to allow a truncate delete to occur when there are no active locks within a folder being deleted in environments with locking active. This has been fixed in 1.0.23.
      • Corrections have been made to the handling of Symbolic Links, which were not being copied or properly reported. This has been fixed in 1.0.23.
      • Performance enhancements have been made related to state scans being processed multiple times. This was harmless but would slow down processing. This has been fixed in 1.0.23.
      • A duplicate action database error could terminate the Hub service in rare situations. This required actions to be computed for a Job that did not start due to an issue like a licensing error. That would block the initialization of the volume, but actions could be computed that were duplicates from the prior run. This has been fixed in 1.0.23.
      • A Job could get stuck waiting on a rename in a rare timing situation where the Change Journal was replayed and the Hub queued the same rename twice. This has been fixed in 1.0.23.
      • If Detailed Status was configured to display status on a remote machine using an access name instead of just the computer name, that access would fail. This has been fixed in 1.0.23.
      • In environments with large amounts of state scans queued, MFT attempted to delete subfolder state scans which could cause each state scan to be delayed by multiple seconds. The Hub will now skip trying to delete the subfolder scans when there is a large number of scans pending, which will improve performance. This has been fixed in 1.0.23.
      • In some instances with Endpoint, the Endpoint would be incorrectly licensed as both a server and a workstation. To correct the issue, apply this update and display the licenses panel from the MFT Desktop by clicking the Licenses button in the ribbon bar. This has been fixed in 1.0.23.
      • When a folder was created, the creation event would be logged in the Job Log for all Jobs with paths on that volume instead of just the single correct Job the folder creation applies to. This has been fixed in 1.0.23.
      • If permissions on an existing account listed in an ACL were updated, these were not being correctly replicated to the other machines if “copy file security objects even if the file is not copied” was selected. All Communications Agents need to be updated to implement this fix fully. This has been fixed in 1.0.23.
      • Defining a root path at the root level of a drive, for example, D:\ or \\Server would produce errors. This has been fixed in 1.0.23.
      • If you request a root scan and there are more than 20,000 change items queued, the Job will discard reading changes, and those changes will be processed via the scan for enhanced performance. This has been fixed in 1.0.23.
      • A System.NullReferenceException error could be presented on an Endpoint client due to an issue with the Hub receiving status messages out of sequence due to the Hub not waiting for a reply to each send. This has been fixed in 1.0.23.

      SureSync MFT 1.0.21 Known Issues

      Version 1.0.21 was posted on May 23, 2023.

      • When deleting a folder to the recycle bin, the Job only received a folder delete event. This means no individual delete events are received for each file. In situations where a truncate delete cannot be used, a folder scan should have been generated that would clean up the folder structure but was not. This has been fixed in 1.0.22.
      • When the Hub service started, it would attempt to recreate an index that was already created. Often times, this was not even noticeable but on large databases it could create a period of many minutes where the Hub was unresponsive. This has been fixed in 1.0.22.
        Fixes have been made to archive, backup root, and Azure file processing. This has been fixed in 1.0.22.
      • Changes have been made to handle files with modified dates set into the future. Modified dates in the future could only occur if done programmatically with an application or if a system was configured with an incorrect date and time into the future. This has been fixed in 1.0.22.
      • If a Job was run with an Interval Set defined that contained no Internals, a System.NullReferenceException error would occur when the Job was executed. An Interval Set must contain at least one Interval, the Desktop has been updated to enforce this correctly. This has been fixed in 1.0.22.
      • Corrections have been made to the handling of checkpoints related to the processing of state changes. In environments with multiple root paths on the same volume on the same server, this could cause the Jobs to stop processing changes. This has been fixed in 1.0.22.
      • If a Job had a large amount of old log entries to purge, it was possible for this cleanup to timeout. This could cause up to a 15 minute period of time where actions may not be performed while the timeout is occurring. This has been fixed in 1.0.22.
      • In specific folder rename sequences from New Folder to different names, it was possible for the Job to get stuck in a “waiting on folder renames or deletes” status. This has been fixed in 1.0.22.
      • In rare circumstances, a deadlock could occur in the Hub which would stop Jobs from processing. This has been fixed in 1.0.22.
      • A correction was made to Enterprise Status to allow a right click on a Job Group Folder to perform a disable all or enable all for Jobs in that specific Job Group Folder. This has been fixed in 1.0.22.
      • When processing a high volume of rapid folder renames, it was possible for processing to halt on a “waiting on x folder renames or deletes” message. This has been fixed in 1.0.22.
        When a file system has files with modified dates that are set into the future by a program or process, the Job could encounter “cannot create a file when that file already exists” error messages. This has been fixed in 1.0.22.
      • When a folder was renamed, it was possible for the checkpoint to not be saved correctly at the end of the Job. This would result in the events being replayed. This caused no problem because there was nothing to be done but was unnecessary overhead. This has been fixed in 1.0.22.
      • Duplicate state scans were not always being purged correctly which could cause a Job to have very high levels of pending state scans which could impact performance negatively. This has been fixed in 1.0.22.
      • In environments with a large number of path losses and recoveries, internal locking on volume changes could impact performance negatively. This has been fixed in 1.0.22.

      SureSync MFT 1.0.20 Known Issues

      Version 1.0.20 was posted on March 30, 2023.

      • A database upgrade has been made to significantly enhance performance during an initial synchronization / population of the MFT database for a new Job. The changes will also enhance performance going forward. Existing databases must be upgraded using a standalone utility distributed with this version. To perform the upgrade, install the new version. Stop the Software Pursuits SureSync MFT Communications Agent service on the Hub machine. Launch the SureSync MFT Desktop. You will be prompted with a message "A database upgrade is required that must be done with a special utility." Click "Yes" on this prompt. Click on the "Start Conversion" button in the next dialog. On the "This will populate a new table in your MFT database to optimize performance" dialog, click "Yes" to continue. In the "Select an existing SureSync MFT database" drop-down select your MFT database. You will receive status on the database update process. Depending on the size of the database, this process could take hours. When finished a "The database has been prepared for the file update part of this conversion" dialog will be displayed. Click "Yes" to complete the process. This has been fixed in 1.0.21.
      • Newly created files were having locks established when a Job had file locking enabled. Since a new file does not exist on the other paths yet, locking is not necessary on the initial add and was adding unnecessary overhead. This has been fixed in 1.0.21.
      • Optimizations have been made to avoid unproductive work attempting to start additional actions when the system was already too busy. This has been fixed in 1.0.21.
        In rare timing circumstances, the Hub could process item compares and increase actions queued without triggering the actions. This has been fixed in 1.0.21.
      • If the Hub service was not running and the MFT Desktop was launched, it was possible to encounter a NullReference error. This has been fixed in 1.0.21.
      • When a path is lost with a communications error when initializing Change Journal processing, it was possible for the root path to be incorrectly disabled which prevented automatic recovery from the communications error. This has been fixed in 1.0.21.
      • In rare timing circumstances, a lock could be released before the file copy action completed. This is very timing specific and required a lock event to be processed before the related journal event. This could cause the file to not be processed correctly. This has been fixed in 1.0.21.
      • If a first level subfolder was moved out of the monitored root path, it was possible that the folder would not be deleted from the destination paths due to a necessary folder rescan not being triggered. This has been fixed in 1.0.21.
      • In file locking, it was possible for a remote machine that was offline to not correctly establish locks from other paths when path recovery occurred. This has been fixed in 1.0.21.
      • When scanning an individual folder, if an exception was encountered it was possible for the Queued Folder Scan counter to present a negative number. This has been fixed in 1.0.21.
        During a retry, it was possible for state scans to be generated incorrectly from individual file scans. This has been fixed in 1.0.21.
      • If a Job was configured with Backup Roots, the backup thinning process could run very slowly and halt other work. This could make the Hub appear to have stopped processing. This has been fixed in 1.0.21.

      Return to top of page

      SureSync MFT 1.0.19 Known Issues

      Version 1.0.19 was posted on February 27, 2023.

      • A background database cleanup query is timing out in some circumstances. This cleanup has been suppressed while work is done to address the slowness leading to the timeouts. This has been fixed in 1.0.20.
      • A loop was identified in the scan manager where it would think there were scans to load when none were present. This would degrade performance. This has been fixed in 1.0.20.
      • It was possible for loads of state scan records to be rejected because a parent scan was already queued. This was blocking scans from executing in a case where it should not have. This has been fixed in 1.0.20.
      • Improvements have been made to a background database cleanup query to avoid timeouts. This has been fixed in 1.0.20.
      • It was possible for the Hub to deadlock waiting for access to actions. This would halt processing and block status from updating. This has been fixed in 1.0.20.
      • A “Violation of primary key constraint” error could occur on the QueuedActions table. This has been fixed in 1.0.20.
      • It was possible for the Hub to deadlock between a lock on actions DB access and processing delayed actions. This would halt processing and block status from updating. This has been fixed in 1.0.20.
      • If running a Job without tracing, it was possible for the job to not initialize in certain timing circumstances. This would result in a job that shows active but did not process any files. This has been fixed in 1.0.20.
      • In some circumstances, duplicate key errors could occur. This has been fixed in 1.0.20.
        Corrections were made to scan processing when Jobs had overlapping paths. This has been fixed in 1.0.20.
      • A System.InvalidOperationException: The operation cannot be completed because the DbContext has been disposed error could occur when a Job was enabled. This has been fixed in 1.0.20.
      • Corrections have been made to the links in Home | Help in the MFT Desktop. This has been fixed in 1.0.20.

      Return to top of page

      SureSync MFT 1.0.18 Known Issues

      Version 1.0.18 was posted on February 6, 2023.

      • Significant enhancements have been made to scan performance. The scan process now uses the Rule settings to not scan items that will not be processed. Previously, the entire structure would be scanned and the Rule applied to the scan results to filter items out. This enhancement greatly optimizes the scan process. In addition, a scan buffer will now return results from multiple directories to ensure a full buffer. Previously, a buffer would be returned for each folder which caused scans of folders with only a few files to be slow. All Communications Agent machines must be updated to take full advantage of this enhancement. This has been fixed in 1.0.19.
      • A NullReferenceException error could occur when processing a journal event and trying to save or update a FileState record. This has been fixed in 1.0.19.
      • Code has been added to prevent Duplicate Key errors from happening. If a Duplicate Key error does occur, the Hub will be automatically restarted to repair the problem. This has been fixed in 1.0.19.
      • Endpoint was not correctly recycling the Communications Agent when a change to the connection information was made in the Endpoint Client. This would cause the Job to fail on initial execution until the Communications Agent was recycled. This has been fixed in 1.0.19.
      • On a newly created MFT Hub database, importing a valid trial or MFT license would sometimes fail to clear the Desktop’s unlicensed message. This has been fixed in 1.0.19.
      • A file rename could cause the Job to stick on a “waiting on a folder rename or delete” message. This has been fixed in 1.0.19.
      • A Schedule could incorrectly end before processing all state scans. This has been fixed in 1.0.19.

      Return to top of page

      SureSync MFT 1.0.17 Known Issues

      Version 1.0.17 was posted on December 20, 2022.

      • Performance enhancements to scanning has been implemented. This has been fixed in 1.0.18.
      • A new set of summary counters for Hub activity have been added to the top of the Enterprise Status panel. This has been fixed in 1.0.18.
      • It was possible for scans to be queued and not released for processing. The backlog could prevent scans from starting for other Jobs. Changes have been made to scan processing to further enhance performance and correct this issue. This has been fixed in 1.0.18.
      • In rare circumstances, a duplicate key error could occur on FileState records when a new record was being added. This has been fixed in 1.0.18.
      • A SQL.Exception: Incorrect syntax could occur. This would lead to additional secondary errors. This has been fixed in 1.0.18.
      • A fix was made to prevent Violation of Primary Key Constraint warnings from occurring on the File States table. This has been fixed in 1.0.18.
      • A query to cleanup file state records that were missing a parent was not performed in batches. If a large amount of these records needed to be cleaned up, this could lead to long delays. The processing is now done in batches. This has been fixed in 1.0.18.
      • A “System.ApplicationException: Object synchronization method was called from an unsynchronized block of code” error could occur on the Hub. This has been fixed in 1.0.18.
      • A violation of primary key constraint error could occur on the Hub. This has been fixed in 1.0.18.
      • An error in a database cleanup routine could lead to the Hub service terminating. This has been fixed in 1.0.18.
      • When a file copy was delayed due to a file lock, it was possible for the delay to not be released when the lock was released, leaving the action pending. This has been fixed in 1.0.18.

      Return to top of page

      SureSync MFT 1.0.16 Known Issues

      Version 1.0.16 was posted on August 26, 2022.

      • Endpoint was incorrectly displaying a pop-up to the user when a connection could not be made to the MFT Hub. This message would repeat each time a connection attempt failed. This has been fixed in 1.0.17.
      • Various optimizations have been made to how the Hub service interacts with the SQL database to enhance performance and avoid overwhelming the connections to the database. This has been fixed in 1.0.17.
      • A System.NullReferenceException: Object variable not set to an instance of an object could occur when saving changes to a Job’s Rule(s). This has been fixed in 1.0.17.
      • Changes were made to prevent commands for things like enabling/disabling of Jobs to get stuck behind other processing. This has been fixed in 1.0.17.
      • Additional counters have been added to Detailed Status showing the number of items pending for the Hub. This gives you an idea of how much data is pending across the entire MFT environment. This has been fixed in 1.0.17.
      • Optimizations have been made to minimize the execution of some expensive SQL queries which could cause the processing of the Hub to slow down. This has been fixed in 1.0.17.
      • If a scan request occurred while a Job was finishing initialization, it was possible that the queued scan would not be processed. This has been fixed in 1.0.17.
      • A SQL query to count FileState records was configured as a blocking query instead of a read-only query which could make other database actions wait. This has been fixed in 1.0.17.
      • Changes were made to the database processing to minimize times when blocks were placed on writes to the database. This will enhance performance in environments with many files to process. This has been fixed in 1.0.17.
      • New indexes have been added to some tables in the database to enhance performance. This has been fixed in 1.0.17.
      • A folder can be auto-created if MFT received an event for a file within that folder before the folder create event. These auto-created folders were not being counted or logged which could result in the add counts for a Job being incorrect. This has been fixed in 1.0.17.
      • The priority process of actions was found to not be reliable because the priority list was not sorted properly by priority. This could result in various slowdowns of processing. This has been fixed in 1.0.17.
      • Counters for items such as State Scans Queued and Retries Queued could end up being incorrect, even to a negative number because the counters were not always being correctly initialized when the Job was initialized. This has been fixed in 1.0.17.
      • In the Detailed Status, Enterprise Status and File Status applications the help file would fail to load if you clicked on the ? in the upper right hand corner of the application. This has been fixed in 1.0.17.
      • Internally, multiple FileID values could be assigned to a file in the case of multiple renames in the same millisecond. The extra FileID values may cause incorrect processing of that file. These sequences are often for temporary files. This has been fixed in 1.0.17.
      • Corrections to internal locking have been made to improve performance of large numbers of delete actions. This has been fixed in 1.0.17.
      • Database enhancements have been made to improve scan performance. This has been fixed in 1.0.17.
      • Corrections have been made to folder rename processing when rapid folder renames of the same folder occurred. This has been fixed in 1.0.17.
      • A NullReferenceException error would occur when clicking Cancel on the Open Database dialog box. This has been fixed in 1.0.17
      • A “System.InvalidCastOperationException: Collection was modified enumeration operation may not execute” error could occur when a Job was enabled. This has been fixed in 1.0.17.
      • A bug in the Telerik controls could cause problems with the Status panels operating correctly. This has been fixed in 1.0.17.
      • In folder rename scenarios, it is possible for a FileState record to be incorrectly deleted for a folder. When this occurs, an error will be generated if this condition occurs and the database will be automatically repaired. This has been fixed in 1.0.17.
      • Additional status messages have been added to indicate delays related to loading directory entries from a folder and some other delays. The updated status helps make it more obvious that Jobs are processing and not stuck. This has been fixed in 1.0.17.
      • When processing scans, it was possible for processing to be too severely throttled by internal throttling. This has been fixed in 1.0.17.
      • During a folder delete, duplicate database records could be created. This has been fixed in 1.0.17.
      • Renames on folders or files that were only a change of case were not being processed correctly. This has been fixed in 1.0.17.
      • The MFT Endpoint client could be launched multiple times at the same time on the same computer. This has been fixed in 1.0.17.
      • If Jobs are disabled or on a Schedule and a backlog of journal events are processed at the time a Job or Root Path is enabled for monitoring when using overlapping Root Paths across multiple Jobs, the Change Journal read position may not be properly reset to re-read journal entries. This has been fixed in 1.0.17.
      • A folder rename would occasionally be queued where the rename new journal record was missing from the queue. This would cause the Job to stop processing. This has been fixed in 1.0.17.
      • In rare timing circumstances, a spin lock could end up causing the Hub service to become CPU bound and halt processing. This has been fixed in 1.0.17.
      • It was possible when a Job was disabled and then enabled again for actions to not process. This has been fixed in 1.0.17.
      • It was possible for an action to be replayed multiple times without completing. This has been fixed in 1.0.17.
      • In an active environment with a number of Jobs processing a large amount of file change, it was possible for a rename action to cause multiple Jobs to sit in a “waiting for folder rename or delete” state and not process changes. This has been fixed in 1.0.17.
      • A repair routine was added to the Hub service when initializing to fix database issues from prior builds. This has been fixed in 1.0.17.

      Return to top of page

      SureSync MFT 1.0.15 Known Issues

      Version 1.0.15 was posted on August 16, 2022.

      • Corrections were made to Endpoint. This has been fixed in 1.0.16.
      • With File Locking, the Change Journal service could receive rename new and rename old events. These were incorrectly treated as folder renames and the journal service released the locks. However, the lock release was not sent to the Job. This could result in a file not being copied because the Job though the files were locked. This has been fixed in 1.0.16.
      • When Advanced Open File Support (AOFS) was enabled, it was possible that lock release notifications would not be sent to remote agents. This has been fixed in 1.0.16.
      • A correction was made to Group Folder security in the Desktop. It was possible to be a member of a local Administrators group that had permissions to access a Group Folder and still be blocked access. This has been fixed in 1.0.16.
      • Changes have been made to the MFT SQL connection string to increase the connection pool and allow additional time for a new connection to be created. This has been fixed in 1.0.16.
      • A list of all established locks can now be displayed in Detailed Status. Locks will only display when they have been open for 30 seconds or longer and the list is updated every 15 seconds. The list is capped at showing 500 locks. This has been fixed in 1.0.16.

      Return to top of page

      SureSync MFT 1.0.14 Known Issues

      Version 1.0.14 was posted on August 9, 2022.

      • Detailed Status has been enhanced to show a “waiting for file changes” status when a MFT Job is idle. This has been fixed in 1.0.15.
      • The Communications Agent version has been added to the General tab of a Computer wizard. MFT shares Communications Agent code with SureSync 9 and the version reported back will be a 9.0 version. The current version in 1.0.15 is 9.0.5.2. This has been fixed in 1.0.15.
      • On the Interval Set tab of an Interval Set definition, the display has been enhanced to display End Time and the configured bandwidth throttles. This has been fixed in 1.0.15.
      • When using a MFT Hub on a Server with a license that contains only the Hub and workstation agents, it was possible to get an incorrect license error popup about the server not being licensed. This has been fixed in 1.0.15.
      • The longest retry interval has been shortened from 30 minutes to 15 minutes. This has been fixed in 1.0.15.
      • Improvements have been made to the queuing of actions to avoid situations where file processing could get delayed. This has been fixed in 1.0.15.
      • In Detailed Status, it was possible for the Queued State Scan counter to report a negative number when certain retry conditions were present. This has been fixed in 1.0.15.
      • In Jobs with File Locking enabled and a large lock list, it was possible that files could be delayed, the delay not be released and the file not processed until a Job was restarted. This has been fixed in 1.0.15.

      Return to top of page

      SureSync MFT 1.0.13 Known Issues

      Version 1.0.13 was posted on July 12, 2022.

      • If you attempted to change the agent used to access a storage account such as Azure or FTP, the system would revert back to the original agent setting. This has been fixed in 1.0.14.
      • When a restore job is run, it is retained and placed in a “hold” status because it is attached to a “manual schedule”. Since it is not disabled, it might compute actions when files are updated, which is generally not desired. The actions are not executed, just computed. This has been fixed in 1.0.14.
      • If you rename a storage service and create another storage service with the name of the original service name, the Hub service could crash with a duplicate key error. This has been fixed in 1.0.14.
      • In a couple of rare timing circumstances, file locking could end up causing actions to be blocked. This would prevent files from being processed. This has been fixed in 1.0.14.

      Return to top of page

      SureSync MFT 1.0.12 Known Issues

      Version 1.0.12 was posted on July 6, 2022.

      • If you have either of the options to Skip Temporary Files on the Options tab of the Job enabled, subfolders would not be processed. This has been fixed in 1.0.13.

      Return to top of page

      SureSync MFT 1.0.11 Known Issues

      Version 1.0.11 was posted on May 19, 2022.

      • In certain conditions, a low priority scan of a parent root can delay other scans of subfolders. The scans eventually execute, but not in the expected order. This has been fixed in 1.0.12.
      • If a machine has external drives using BitLocker, a reboot of the computer may generate an error if the drives are accessed before the drivers are unlocked. MFT would mark the root paths as disabled. This has been fixed in 1.0.12.

      Return to top of page

      SureSync MFT 1.0.10 Known Issues

      Version 1.0.10 was posted on April 20, 2022.

      • An error in the licensing routine could result in a server being counted twice, causing the license count to be exceeded. This has been fixed in 1.0.11.
      • When starting File Status from a Detailed Status panel for a Job, the program would immediately try to display a Job Log from the last execution of the Job. The display, however, did not include the name of the Job. This has been fixed in 1.0.11.
      • When a Job is enabled while other Jobs are active, it was possible for the new Job to checkpoint a Journal location before it had fully initialized, causing Journal events to possibly be skipped. The skipped events might cause actions to be skipped. This has been fixed in 1.0.11.
      • If actions are already queued when a Job starts, a Journal for the Job had no activity, and journal entries have been filtered out by the operating system, the Job may not recognize that the Journal has been drained. The actions are waiting for some activity in the Journal so it can recognize all Journal entries have been read. This could cause a delay in processing actions. This has been fixed in 1.0.11.
      • In Enterprise Status, the alert count for a Job could be incorrectly displayed as zero when the group has a count present. This has been fixed in 1.0.11.
      • If you host a MFT database on a remote SQL server, such as in the cloud, communications errors can be much more common. A couple of recoverable error conditions were incorrectly being classified as severe, which would cause the Hub to restart. This has been fixed in 1.0.11.

      Return to top of page

      SureSync MFT 1.0.9 Known Issues

      Version 1.0.9 was posted on October 22, 2021.

      SureSync MFT 1.09 was the initial release of MFT.

      • When processing data to Azure blob storage, it was possible to have files re-copied unnecessarily when a full scan occurred. This has been fixed in 1.0.10.
      • A NullReferenceException error could occur when performing a background cleanup of a deleted root path. This has been fixed in 1.0.10.
      • A SQL timeout could occur on a background cleanup task. This has been fixed in 1.0.10.
      • Enhancements were made to the processing of delayed state scans. This has been fixed in 1.0.10.
      • If an archive rule specified the retention of x recent files and fewer than x were created, the archive thinning queue might skip the thinning of the folder when the entries age. This has been fixed in 1.0.10.
      • In certain circumstances, the processing of change events could be delayed unnecessarily. This has been fixed in 1.0.10.
      • If you did not define a trace path in the local agent configuration utility on a remote machine, any traces defined on a Job could be incorrectly directed to the default trace folder. This has been fixed in 1.0.10.
      • In the Log Viewer, the Destination Machine filter was not working correctly. This has been fixed in 1.0.10.
      • In certain situations, a Hub service shutdown could discard writing pending folder scan records for subfolders. This has been fixed in 1.0.10.
      • In rare timing situations, when many simultaneous requests to transmit were made at once, a NullReferenceException could occur on the source server. This has been fixed in 1.0.10.
      • When a connection was aborted, a busy state for the aborted action could be left busy. This could eventually block other attempted I/O operations when the maximum connection count is reached. This has been fixed in 1.0.10.

      Return to top of page