Skip to content
English
Submit a Support Ticket
Contact us
  • There are no suggestions because the search field is empty.

SureSync 9 Version History

The version history page outlines all fixes and improvements in each SureSync 9 release.

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 9.0 requires current Microsoft technologies as outlined on the SureSync 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 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 only or you can turn off ZipFolders during the time you run your synchronization.

To turn off the ZipFolders for SureSync’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 (9.0.30)

Version 9.0.30 was posted on March 7, 2025.

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 9.0.29 Known Issues

Version 9.0.29 was posted on January 24, 2025.

Communications Agent

  • Connections to a remote machine could get a ServiceModel.FaultException error that was not being retried and this would trigger an alert. This has been fixed in 9.0.30.

File Synchronization

  • A System.NullReferenceException error could place a monitor on hold. This has been fixed in 9.0.30.
  • A Trial Run could duplicate folder scans in some circumstances, making it scan more than necessary. This has been fixed in 9.0.30.
  • Trial Run executions must perform a full scan. If scans were pending, queued folder scans were being cleared one at a time on the startup. This would take a long time and make the Trial Run appear not to be fully executing. A change has been made to purge these scans much more efficiently.  This has been fixed in 9.0.30.
  • A correction has been made to the database upgrade utility used to create v9 databases from older SureSync version databases. A corrupted Alert Profile record in an old database could cause the upgrade to fail.  This has been fixed in 9.0.30.
  • When Advanced Open File Support is configured, a standard open file support copy will be attempted first. If this fails, AOFS will be used. This helps minimize resource usage due to open file support. This has been fixed in 9.0.30.

Licensing

  • If a connection was lost while a workstation machine was performing a license check, the machine would be incorrectly reverted to a server license. This has been fixed in 9.0.30.

User Interface

  • Detailed Status could terminate due to an unhandled exception related to a timer when the form was being closed.  This has been fixed in 9.0.30.
  • When creating a new database for the first time, it was possible to receive a" System.ApplicationException: The configuration database has not been loaded. This has been fixed in 9.0.30.

SureSync 9.0.28 Known Issues

Version 9.0.28 was posted on December 23, 2024.

File Synchronization

  • When setting security on a folder in an archive, an "overlapped I/O event is not in a signaled state" error could occur.  This has been fixed in 9.0.29.
  • In rare timing circumstances, a Change Journal event could be skipped. This has been fixed in 9.0.29.
  • Path recovery corrections and enhancements have been made. This has been fixed in 9.0.29.
  • System.NullReferenceException errors have been corrected. This has been fixed in 9.0.29.
  • Telerik controls updated to 2023.4.1213 version. This has been fixed in 9.0.29.

SureSync 9.0.27 Known Issues

Version 9.0.27 was posted on November 14, 2024.

File Synchronization

  • Corrections have been made to permissions copying where copying of ownership is defined, but the agent's user account does not have permission to copy ownership.  This has been fixed in 9.0.28.
  • Memory usage optimizations have been made. This has been fixed in 9.0.28.
  • Error recovery corrections have been made. It is recommended that all agents be upgraded to this new version to receive all the enhancements. This has been fixed in 9.0.28.

SureSync 9.0.26 Known Issues

Version 9.0.26 was posted on October 28, 2024.

File Synchronization

  • Performance optimizations have been made to folder scans. Internal CPU throttling code was throttling too severely. This has been fixed in 9.0.27.
  • In rare timing circumstances, a folder rename could result in the folder and contents existing in both the old folder location and the new folder location. This has been fixed in 9.0.27.

User Interface

  • The capability to provide your own server certificate has been added. To define this, launch the SureSync Desktop and expand the Computers node. On the General tab of a computer record, when you click on the "Set Credentials for Accessing this Agent" panel, there is a new "Server Certificate" drop-down menu. The certificate needs to be installed on that particular machine with the private key. The default is "use a self-signed certificate" but you can also select a certificate by thumbprint or distinguished server name. Once you have defined the certificate details, you must publish that configuration to the computer by clicking on the Options tab of the computer record and clicking on the "Update Agent Configuration and Restart Service" button. If providing your own certificate, keep in mind that you become responsible for managing the renewal of that certificate so using this functionality adds an additional management task to the SureSync environment.  This has been fixed in 9.0.27.

SureSync 9.0.25 Known Issues

Version 9.0.25 was posted on September 22, 2024.

File Synchronization

  • When a script is executed via the Scripts tab, a log entry will now be logged, indicating the script was being executed. This has been fixed in 9.0.26.
  • In a multi-step Schedule, if the "Run the script on each Agent" option, the script was only being executed on the first Job instead of all of them. This has been fixed in 9.0.26.
  • The path recovery process has been optimized to recover brief outages without producing loss and recovery log entries. In some situations, internal retries for a path loss were not triggered before posting the path loss message. This has been fixed in 9.0.26.
  • If a Job was canceled during initialization, a wrap trace was being generated even though one was not requested. This has been fixed in 9.0.26.
  • Enhancements have been made to the path loss and recovery process to speed up processing when a Monitor encounters a number of path losses. This has been fixed in 9.0.26.
  • A change has been made to an internal lock that was blocking status displays from a job during job initialization. This would cause status information to not update appropriately and would be a problem in environments with many frequent path losses. This has been fixed in 9.0.26.
  • When a job starts, connection attempts to all paths are not done in parallel instead of one at a time. This will speed up initialization when paths are offline at the start of a job. This has been fixed in 9.0.26.
  • Internal throttling has been added in the agent and SyncFiles when high CPU usage is detected to avoid overwhelming a machine's resources. This has been fixed in 9.0.26.
  • If a Move Rule is used, the destination path will not be monitored for changes. By default, all paths have the "monitor folder for content changes" option enabled, but this is unnecessary and adds overhead in Move Rule processing. This has been fixed in 9.0.26.
  • Changes have been made to the truncation delete logic not to suppress the use of truncate delete when there are exclusions defined in the Rule. This will allow the truncate delete to execute even if those folders contain items that are generally excluded by Rule. This will produce the expected behavior of a user deleted a folder on one path and expects it to be deleted from the other and will avoid warnings about being unable to delete a folder because it is not empty. This has been fixed in 9.0.26.
  • If a Job has more than 3 destinations, file actions will now be generated as independent actions. This prevents a slow or offline path in the Job from slowing down processing to the other paths. This has been fixed in 9.0.26.
  • Retries have been shortened, and new retry logic has been added to try and recover connections faster and prevent path losses. This has been fixed in 9.0.26.
  • The initialization process on job startup now processes all machines in parallel instead one at a time. This has been fixed in 9.0.26.
  • An index out of range exception could occur. This has been fixed in 9.0.26.
  • An attempt to process a scan could loop when an offline path delayed that scan. This could result in a Job that was "waiting for file changes" with scans queued. This has been fixed in 9.0.26.
  • A loop could occur in error recovery in some timing situations when attempting to build a connection to a machine that was not reachable. This has been fixed in 9.0.26.
  • Changes have been made to address Change Journal request timeouts. This has been fixed in 9.0.26.
  • When starting up a Job, all paths will now be connected to in parallel which will increase the speed of the Job starting up. You will now see a "Connecting to agents for x paths" message instead of seeing each connection happen one at a time. This has been fixed in 9.0.26.
  • When a full scan was requested and paths were offline, the Job could trigger the full scan repeatedly. This has been fixed in 9.0.26.
  • In a Monitor with multiple Jobs, if root scans were pending for offline roots, Change Journal events could be missed because the journals were incorrectly reset to read from their current location when root scans were pending. This has been fixed in 9.0.26.

SQL Protection

  • SQL Protection's relocate database file option on the Restore File Maps tab has been corrected. This has been fixed in 9.0.26.
  • SQL Protection had a one-hour timeout for the restore process. This has been increased to 4 hours. This has been fixed in 9.0.26.

User Interface

  • The message alerting to overlapping root paths when saving a Schedule has been suppressed. This has been fixed in 9.0.26.
  • Options have been added to the Logging tab of Options to turn off all tracing defined in the database and to purge traces after x number of hours automatically. This will make it easier to leave tracing on for a technical problem without encountering hard drive free space limitations. This has been fixed in 9.0.26.
  • When saving a Real-Time Monitor with overlapping root paths in the Jobs, you will now receive a single prompt to ignore the issue and save your change instead of a prompt for each Job with an overlapping path. This has been fixed in 9.0.26.
  • A filter has been added to the job log to show just file action detail and not any warnings, errors or exceptions. This filter is useful for just seeing added, modified and deleted folders and files. This has been fixed in 9.0.26.
  • An option has been added to disable the use of deltas across all Jobs. This has been fixed in 9.0.26.
  • A NullReferenceException error could occur on a Test Connection button. This has been fixed in 9.0.26.

SureSync 9.0.24 Known Issues

Version 9.0.24 was posted on August 1, 2024.

File Synchronization

  • When a script was defined on a Schedule that had multiple Jobs within it, the script would be executed on each agent with each Job that was run. The script should only be executed once per agent per Schedule execution. This has been fixed in 9.0.25.
  • Duplicate calls were being completed to update configuration data. The excess calls could cause the status service to get bogged down processing configuration changes from the Jobs, potentially making it 100% CPU-bound. This has been fixed in 9.0.25.
  • A multi-step Schedule would incorrectly log a "cancel request by SYSTEM" error when completing a step in the Schedule where there was no further work to perform. This has been fixed in 9.0.25.
  • When multiple root paths were reading a large volume of Change Journal events, the agent could consume a large amount of CPU. Changes have been made to the Journal service to protect against excessive CPU usage by the routine. This has been fixed in 9.0.25.
  • SyncFiles was sending configuration data to remote agents when unnecessary. These sends added unnecessary overhead. This has been fixed in 9.0.25.

Communications Agent

  • A loop could occur within the Communications Agent if it encountered delayed, out of sequence blocks for a file. This has been fixed in 9.0.25.

SureSync 9.0.23 Known Issues

Version 9.0.23 was posted on July 2, 2024.

File Synchronization

  • Delta copies were not being used. This has been fixed in 9.0.24.
  • Corrections have been made to how SyncFiles was handling more than 30 destinations in a single action. This has been fixed in 9.0.24.
  • Corrections have been made to Execution Context flows. Issues here were leading to occasional NullReferences internally which would cause different types of problems depending on where they occurred. This has been fixed in 9.0.24.
  • SPIServiceUpdate.exe was failing to restart the service after starting it. This program is used when publishing agent configuration details that require a service restart. This has been fixed in 9.0.24.
  • A performance optimization has been made to the process of deleting file history when an entire job is deleted or a request is made from the Desktop to purge all file history for a Job. This has been fixed in 9.0.24.
  • When defining an Alert Filter to not alert until x number of minutes has passed, the path recovery alert e-mails were being sent even if the path recovery message was for a path loss that did not exceed the alert threshold. This has been fixed in 9.0.24.
  • A correction was made to license validation that may have cleared the indicator when SureSync failed to get server information on a license validation query. This could cause a machine previously validated as a workstation to revert to a server if the machine was offline when the license validation was executed. This has been fixed in 9.0.24.

SureSync 9.0.22 Known Issues

Version 9.0.22 was posted on June 18, 2024.

File Synchronization

  • After a folder rename, scans and retries could be queued that were not processed. This has been fixed in 9.0.23.

Status Web

  • With Status Web, the SyncFiles process would calculate Group Folder permissions incorrectly. In some circumstances, this would result in a running Job disappearing from Status Web and then reappearing. This has been fixed in 9.0.23.

User Interface

  • Attempting to change settings for more than one user or group on the Security tab of a Job, Schedule, or Monitor at once would produce a "System.Data.Entity.Core.UpdateException: An error occurred while updating the entries" error. This has been fixed in 9.0.23.

SureSync 9.0.21 Known Issues

Version 9.0.21 was posted on May 13, 2024.

File Synchronization

  • In a Job with open file processing enabled, retries for the open file might delay unrelated scans and journal events. This has been fixed in 9.0.22
  • In a Schedule with multiple destinations, if one destination path was offline, it was possible for the Schedule to cancel instead of processing the other online destination paths. This has been fixed in 9.0.22.
  • Truncate deletes were being incorrectly suppressed in a Job with Backup Roots defined for one or more Root Paths. This has been fixed in 9.0.22.
  • In a multi-step Schedule, the Schedule could get stuck at the end of a step, sitting on "waiting for file changes." This has been fixed in 9.0.22.

Status Web

  • When applying a Job Name filter to Status Web, an enhancement has been made to hide empty groups that do not contain the Job specified. This makes it easier to locate the Job in question. This has been fixed in 9.0.22.
  • Corrections have been made to calculation and assignment of group folder security to Jobs in Status Web. This could cause display issues in Status Web where a user would not see Jobs they actually had access to. This has been fixed in 9.0.22.
  • Status Web could produce a "Job was not Found" message when executing a Job. This has been fixed in 9.0.22.
  • In Status Web, some browsers did not correctly format the links for alerts and the job log. The format of those links has been changed to make it clearer that they can be clicked on. This has been fixed in 9.0.22.
  • Status Web optimizations have been introduced. This has been fixed in 9.022.

SureSync 9.0.20 Known Issues

Version 9.0.20 was posted on April 23, 2024.

File Synchronization

  • In rare circumstances, a remote agent could time out sending a response back to the Job. The Job actually received the message and did not notice a connection drop, but the remote agent assumed that the timeout meant that the connection dropped.  The agent would then stop processing that Job's changes and wait for a reconnect. This would lead to the Job not receiving new events from that remote agent, which would prevent changes from being processed. The Change Journal connection on the agent will now detect this scenario and retry the connection. This has been fixed in 9.0.21.
  • A "FileID in FileHistory does not match the FileID in FileActions" error could occcur. This has been fixed in 9.0.21.

Scheduler

  • In a multiple Scheduler environment, when one of the Scheduler machines lacks permissions to query the status of processes on the other machine, the Job could start reporting "[Job/Schedule/Monitor Name] is already busy. You cannot run the same Job/Schedule/Monitor multiple times concurrently" due to an error in the busy reset code. This has been fixed in 9.0.21.

SureSync 9.0.19 Known Issues

Version 9.0.19 was posted on April 1, 2024.

File Synchronization

  • A "System.Data.SQLClient.SQLException: Violation of PRIMARY KEY constraint. Cannot insert duplicate key in object 'dbo.QueuedScans" error could occur due to a rare SQL timeout. This has been fixed in 9.0.20.
  • Some retries and scans were delaying other scans. The blocking items were related to open and locked files, which should not have blocked other retries. This has been fixed in 9.0.20.
  • A Job could cancel with a "System.ApplicationException: Object synchronization method was called from an unsynchronized block of code" error. This has been fixed in 9.0.20.
  • When a file was copied into the SureSync 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.

User Interface

  • The Usage tab on a Computer record in the SureSync Desktop could fail to populate. This has been fixed in 9.0.20.
  • Validation of a remote agent by the SureSync Desktop has been removed. This validation process happens during a Job run, so removing it from the Desktop will increase the speed of the Desktop. This has been fixed in 9.0.20.

SureSync 9.0.18 Known Issues

Version 9.0.18 was posted on March 17, 2024.

File Synchronization

  • A multi-step Schedule could fail to advance from one Job to the next with Detailed Status showing the Schedule was a "waiting for tasks to complete" message. This would occur in specific timing situations where a folder delete had to be retried. This has been fixed in 9.0.19.
  • During an upgrade, the Communications Agent configuration was incorrectly copied from the SureSync v8 folder to the SureSync v9 configuration folder. This caused the agents to attempt to listen on the wrong port. This has been fixed in 9.0.19.
  • If a File Mask definition contained a parathesis, it would not be handled correctly resulting in the Job dropping the path. This has been fixed in 9.0.19.

SureSync 9.0.17 Known Issues

Version 9.0.17 was posted on January 19, 2024.

Database

  • Some indexes were not being created correctly in the SureSync database, which could negatively impact performance. If they are missing, the indexes will be created with the new version. This has been fixed in 9.0.18.

File Synchronization

  • A Trial Run could loop in certain conditions when folder deletes were present. This has been fixed in 9.0.18.
  • With a Schedule, if a file copy action came in right at the end of the Schedule processing, it would be missed until the next Schedule execution, when it should have been processed before terminating the Schedule. This has been fixed in 9.0.18.
  • A Schedule could terminate before all busy actions had completed processing, which would result in those pending actions not being logged. This has been fixed in 9.0.18.
  • When making exclusion changes to a Rule, a scheduled Job could try and process folders because there were history records that used a Rule from a prior run. This has been fixed in 9.0.18.
  • In certain timing circumstances, when a folder was deleted, a FileAction record could be deleted while the node was still active, which would cause SyncFiles.exe to terminate. This has been fixed in 9.0.18.
  • When running a multi-mirror job without the "Use database history for multi-way Rules" option enabled, it was possible for the Job to select an incorrect source for the file copy. The "Use database history for multi-way Rules is enabled by default. This has been fixed in 9.0.18.
  • If a folder was deleted and re-created within a few minutes, the history for the folder was deleted. However, a reference remained in memory, which caused the synchronization process to think the FileAction record still existed. This would cause the job to be canceled with a database error. In some timing circumstances, the SyncFiles.exe process could remain in Task Manager on the machine and need to have an End Process performed. This has been fixed in 9.0.18.
  • A multi-step Schedule could get stuck on a "waiting for tasks to complete" message and not move between Jobs. This has been fixed in 9.0.18.

User Interface

  • The license check and validation process has been changed to only validate the type of machine when referenced in a job or when the Test Connection button is used on the Desktop. This avoids a potential performance issue when importing many machine references using the import functionality at once. This has been fixed in 9.0.18.
  • The installer no longer checks for Internet Explorer. This change allows the agent-only installation to run successfully on Windows Server Core edition. This has been fixed in 9.0.18.

SureSync 9.0.16 Known Issues

Version 9.0.16 was posted on November 22, 2023.

File Locking

  • A correction has been made to file locking to address issues where a lock could be incorrectly released with applications that perform renames on their files during operations like a save. This has been fixed in 9.0.17.
  • A Job with File Locking could end up with retries queued that don't clear. This has been fixed in 9.0.17.

File Synchronization

  • When there were a large number of scans queued, the performance of the scan could decline. This has been fixed in 9.0.17.
  • If a file copy destination was on the main SureSync machine and a file transfer took longer than 15 minutes, the file copy action would be incorrectly retried because the copy operation was assumed to be aborted because the agent was not correctly querying file copy progress. This has been fixed in 9.0.17.
  • A change has been made to skip initializing configurations for machines that have never been accessed when saving server changes / validating licenses. This should reduce the time consumed when testing a connection. This has been fixed in 9.0.17.
  • The scans queued counter could report a negative number. This has been fixed in 9.0.17.

SQL Protection

  • When defining the “Relocate database files to” or “Manually set files in file list” options on a Restore File Maps tab of a SQL Protection Job, an “item with the same key has already been added” error would occur. This has been fixed in 9.0.17.
  • An “item with the same key has already been added” error could occur when creating a SQL Protection Job that includes a restore to another server. This has been fixed in 9.0.17.
  • A large SQL restore could cause a timeout that would drop a path. This has been fixed in 9.0.17.

User Interface

  • When importing a large number of Communications Agent configurations, performance would degrade. Improvements have been made to performance and the reporting of the status of an import. This has been fixed in 9.0.17.
  • When clicking on "Test Agent Connection," it was possible to get a NullReference exception. This has been fixed in 9.0.17.

SureSync 9.0.15 Known Issues

Version 9.0.15 was posted on November 12, 2023.

File Synchronization

  • An "object synchronization method was called from an unsynchronized block of code" error could occur that would cancel the running Job, Schedule or Monitor. . This has been fixed in 9.0.16.
  • If a SQL Protection backup took longer than 5 minutes, it would incorrectly cause a timeout that would drop a path. This has been fixed in 9.0.16.

SureSync 9.0.14 Known Issues

Version 9.0.14 was posted on October 26, 2023.

File Synchronization

  • Corrections have been made to the processing of security copying. The scan returned security values on all files even if the "copy file security objects even if the file is not copied" option was not selected. This would slow down scan performance. Copying security objects to files that have not changes introduces a large amount of overhead and should only be used when absolutely necessary. This has been fixed in 9.0.15.
  • Corrections have been made to FTP processing. This has been fixed in 9.0.15.
  • Retries related to offline paths would incorrectly increase retry counts when they should not. This could result in the retries queued count in the Detailed Status panel showing retries queued when there were not any. This has been fixed in 9.0.15.

SQL Protection

  • In SQL Protection, if you configured the Job to restore to another SQL server, a "System.IndexOutOfRangeException: Index was outside the bounds of the array" error would be produced. This has been fixed in 9.0.15.

User Interface

  • If you clicked on the FTP tab in Options without making any changes, clicked off the tab and closed the Options panel it would produce a dialog asking if you wanted to save your changes. This has been fixed in 9.0.15.

SureSync 9.0.13 Known Issues

Version 9.0.13 was posted on August 30, 2023.

File Synchronization

  • Skip rules could be ignored. This has been fixed in 9.0.14.
  •  A correction has been made to diagnostic tracing. This has been fixed in 9.0.14.
  • A NullReferenceException could occur which could cancel the Schedule or Real-Time Monitor. This has been fixed in 9.0.14.

SureSync 9.0.12 Known Issues

Version 9.0.12 was posted on July 14, 2023.

File Synchronization

  • A System.NullReferenceException could occur when processing the completion of a folder truncate delete while trying to process a subfolder within the deleted folder. This has been fixed in 9.0.13.
  • Reparse points on files could cause slow scan performance. When a reparse point was found, it was thought to be a symbolic link, and an additional API call was sent to verify file size and dates. This API call added multiple seconds to each file, causing slow scan performance. This is likely to occur with volumes using deduplication. This has been fixed in 9.0.13.
  • If a script was defined in the “Script for start of each Schedule” field on the Scripts tab, it was not being executed when the Schedule ran. This has been fixed in 9.0.13.
  • The behavior of the “Run Scripts on Destinations” option on the Scripts tab has been changed. From the perspective of the Scripts tab, destinations were defined as any path in the Job marked as a destination that was not on the SureSync machine. If a Job contained a remote source and remote destinations, there was no way to execute a script on the remote source. This option has been renamed “Run the script on each Agent instead of by the Job.” If this option is defined, a script should be present on each machine involved in the Job in the location defined. On the paths where you want the script actions performed, the script should have contents. On the paths where you don’t want the script actions performed, the script should be blank, resulting in the executed script doing nothing. This change allows a script to be executed on a remote source machine. This has been fixed in 9.0.13.
  • 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. This has been fixed in 9.0.13.
  •  Job could get stuck on "x history record deletes pending" when a timeout occurred on the database when performing history deletes. Retries would also timeout, which would stop job progress. This has been fixed in 9.0.13.
  • On a Schedule, it was possible for a deadlock to occur when the end of the Journal was read. This would prevent the Schedule from completing. This has been fixed in 9.0.13.
  • When a Job deleted a delayed scan, it could have a negative number in the retries queued counter. This was harmless. This has been fixed in 9.0.13.

User Interface

  • When saving a new Priority in Options, a DbUpdateConcurrencyException: System.Data.Entity.Infrastructure.DbUpdateConcurrencyException: Store update, insert, or delete statement affected an unexpected number of rows (0)." error could occur. This has been fixed in 9.0.13.

SureSync 9.0.11 Known Issues

Version 9.0.11 was posted on July 10, 2023.

File Synchronization

  • In a Job configured with Skip rules, it was possible for folders to not be deleted. In this scenario, truncate deletes are not used. If a delete was a "delete to recycle bin" or a move out of a monitored location, the folder delete was being suppressed because the Job identified that a scan of the folder contents was required. The contents scan was discarded because the Job thought the folder delete was queued which would result in the folder not being deleted. This has been fixed in 9.0.12.
  • In rare circumstances, it was possible for a Job to loop on a duplicate scan. This has been fixed in 9.0.12.

SureSync 9.0.10 Known Issues

Version 9.0.10 was posted on June 19, 2023.

Database

  • A correction has been made to converting SureSync v6 databases to v9 in the database conversion utility. This has been fixed in 9.0.11.
  • In the Database Conversion Utility, if the default port number had been entered on a Listen Configuration as the port number instead of the default 0 to represent the default port, the utility was not converting those connections to the new 9031 SureSync 9 port number. This would cause test connections to fail and require manually changing the port to the correct port number. This has been fixed in 9.0.11.

File Synchronization

  • When running a Job, a "The query processor ran out of internal resources and could not produce a query plan" error could occur in SyncFiles. This has been fixed in 9.0.11.

Status Web

  • In Status Web, you could not apply a filter for both Job names and Group Folder names at the same time and get correct results. This has been fixed in 9.0.11.

User Interface

  • A correction has been made to the SureSync Desktop to allow the selection of “this is an archive path” in path options of a Root Path. This has been fixed in 9.0.11.
  • Clicking “Apply” after making changes to the Security tab of a Job Group Folder could produce a primary key constraint error. This has been fixed in 9.0.11.
  • When changing an existing root path in the SureSync Desktop for a Job with Change Journal support enabled, it was not scheduling a necessary full scan. This has been fixed in 9.0.11
  • Clicking on the "Update Agent Configuration and Restart Service" button on the Options tab of a Computer in the SureSync Desktop would not always publish all changes correctly unless the Desktop was closed and relaunched first. This has been fixed in 9.0.11.
  • On the Security tab of a Job, if the Job had both inherited and explicitly defined permissions, the permissions were not all being displayed correctly. This has been fixed in 9.0.11.

Return to top of page

SureSync 9.0.9 Known Issues

Version 9.0.9 was posted on March 26, 2023.

Archiving

  • With Archive thinning, it was possible for the thinning routine to not be called which would result in the thinning action not occurring. This has been fixed in 9.0.10.
  • If an existing Job with an Archive path was edited to remove the “This is an archive path” option from the Archive root and you clicked apply, it would not allow you to re-select the option. This has been fixed in 9.0.10.

File Synchronization

  • With a Schedule, it was possible to get into a situation where retry counts were not incremented because new scans were being generated and queued scans were not removed when child scans were deleted. This would result in the Schedule looping on retries and not completing. This has been fixed in 9.0.10.
  • With a Schedule, it was possible for a retry to be incorrectly deleted when a new retry was triggered by an existing retry. This has been fixed in 9.0.10.
  • Duplicate key errors could occur that would lead to a System.NullReferenceException error that would cancel the Job following a truncate delete being performed. This has been fixed in 9.0.10.
  • A performance improvement related to scanning a large number of folders has been implemented. This has been fixed in 9.0.10.

Return to top of page

SureSync 9.0.8 Known Issues

Version 9.0.8 was posted on February 6, 2023.

File Synchronization

  • A System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary error could occur. This has been fixed in 9.0.9.
  • The deleting of file history could be slow. This has been fixed in 9.0.9.
  • A System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary error could occur that would cause paths to drop in a Real-Time Monitor. This has been fixed in 9.0.9.
  • A performance enhancement has been made to processing large batches of Change Journal events where no actions were triggered. This has been fixed in 9.0.9.
  • A System.ArgumentException error could occur while attempting to save a Journal event related to a rename. This has been fixed in 9.0.9.
  • A "cannot create a file when that file already exists" error could occur on a rename. This has been fixed in 9.0.9.

User Interface

  • A NullReferenceException error would occur when locks were displayed in Detailed Status. This would prevent status from being updated as long as there were locks active. This has been fixed in 9.0.9.
  • Deleting an archive Rule from Home | Archive Rules could result in the Desktop becoming unresponsive. This has been fixed in 9.0.9.

SureSync 9.0.7 Known Issues

Version 9.0.7 was posted on December 16, 2022.

Archiving

  • Archives were not always being thinned correctly based on the Archive Rule which could leave additional copies in the archive. This has been fixed in 9.0.8.

File Synchronization

  • It was possible for the enabling of privileges on a UNC path to be very slow. An update has been made to avoid retrying failed attempts to enable these privileges. This has been fixed in 9.0.8.
  • In rare circumstances, it was possible for a loop to occur when scans were delayed by retries. This would degrade performance. This has been fixed in 9.0.8.
  • When doing a drag and drop operation to move files from one subfolder to another within a monitored Root Path, unnecessary retries were being queued related to the rename processing. This has been fixed in 9.0.8.
  • Changes have been made to skip retries in queue because of an offline root until all roots are online. This helps prevent other work from getting stuck behind the retries that are not going to complete because of the offline path. This has been fixed in 9.0.8

Scheduler

  • In a multiple Scheduler environment, a “System.Data.Infrastructure.DbUpdateConcurrencyException” error could occur that would cancel a Job. This has been fixed in 9.0.8.

User Interface

  • Preview would produce an error on load and terminate. This has been fixed in 9.0.8.
  • When performing a copy/paste of a Rule from one Job to another, a “DbUpdateConcurrencyException” error would occur. This has been fixed in 9.0.8.

Return to top of page

SureSync 9.0.6 Known Issues

Version 9.0.6 was posted on November 7, 2022.

File Synchronization

  • A change has been made to expedite the processing of folder scans related to renames so they do not get stuck behind a long queue of other folder scans. This has been fixed in 9.0.7.
  • If using a UNC path that cannot be accessed by the Communications Agent credential, a delay would occur when trying to get server information about the path. The database was not correctly updated to prevent testing the path again which would cause a 2 to 4 minute delay when trying to access the problem machine. This has been fixed in 9.0.7.
  • If a Schedule ran with a UNC path offline and there were scans queued for that path, it was possible for the Schedule to not complete. This has been fixed in 9.0.7.
  • If a Job was executed with a FTP path and no defined FTP profile, a System.NullReferenceException would occur. This has been fixed in 9.0.7.
  • In circumstances where scans or actions were delayed due to other activity, a SQL database query could start to take a long time to complete which would cause all processing to slow. This has been fixed in 9.0.7.
  • If a FTP server name is the same name as the Agent name on the path, the FTP server would not be properly licensed. This has been fixed in 9.0.7.
  • With UNC paths, it was possible for a license check to fail to use the agent defined for accessing that path when performing the check. This would cause the license check to fail. This has been fixed in 9.0.7.
  • In certain circumstances, Agent IDs were not being correctly set for root paths due to an error in earlier versions of SureSync 9. This could result in machines not being properly reflected in the licensing count. This has been fixed in 9.0.7.

User Interface

  • Changing the order of Rules on the Rules tab of a multi-Rule Job would result in a “SyncSQLDBLib.RelationRule failed because another entity of the same type already has the same primary key value” error. This has been fixed in 9.0.7.
  • The database conversion utility failed to copy security values for the default group when converting databases from prior versions. This could result in a user that had permissions to access Jobs in the old version not having access in the new version. This has been fixed in 9.0.7.

Return to top of page

SureSync 9.0.5 Known Issues

Version 9.0.5 was posted on August 26, 2022.

File Locking

  • If a rename was processed at the same time as a locked file is closed, the lock could be moved to the renamed file. In that case, the lock was not released when the original file name processing completes. This would result in a lock remaining. This has been fixed in 9.0.6.
  • Changes have been made to the Journal service to attempt to correct a rare instance where file locking get removed from the list of locks to test, resulting in the lock not being released. Additional tracing has been added as well. This has been fixed in 9.0.6.

File Synchronization

  • It was possible to receive a System.Data.SqlClient.SqlException deadlock error from the SQL database that was not retried properly in non-English language systems. This error would cancel the Job. This has been fixed in 9.0.6
  • When tracing was enabled on a Schedule or Monitor, it was possible to receive a “System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument” error which would cancel the Schedule or Monitor. This has been fixed in 9.0.6.
  • In a multi-mirror with security copying enabled, the Job was failing to detect the source of the security change and would produce a “Unable to determine the source for changed security values” warning unless a source for multi-way security was defined. This has been fixed in 9.0.6.
  • On the Scripts tab of a Schedule, defining a End of Schedule script and selecting the “Run script on Destinations” option would result in a “No direct connection is available from ServerA to ServerB” error and the script would not be launched. This has been fixed in 9.0.6.
  • If you have a Schedule with multiple Jobs, some that use Journals and some that do not, and the same volume is referenced by the Jobs, a Job in the Schedule could get stuck and not complete. This has been fixed in 9.0.6.
  • A Job could timeout on waiting for the Journal service on offline servers. This could take over 5 minutes and would make the Job appear to be dead. This has been fixed in 9.0.6.
  • If a server was referenced by both an agent and a UNC path in the same database, it was possible for a path to drop and not recover. This occurred because the Job could sometimes incorrectly decide to use the UNC path and UNC path credentials to try and validate the agent. This would fail and cause the path to drop. It will now use the Agent credentials if defined when checking licensing in this situation. This has been fixed in 9.0.6.
  • A “System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. System.Data.SqlClient.SqlException: Incorrect syntax error near ‘OFFSET’ error could occur. This has been fixed in 9.0.6.
  • SyncCmd has been enhanced to allow the execution of remote Jobs without needing to provide credentials in the command. The user account defined for the agent issuing the request is used. This has been fixed in 9.0.6.

Scheduler

  • The Scheduler error recovery has been enhanced to retry starting a Job that just started and is found to immediately fail. This condition is caused by a stack overflow error that happens occasionally from what appears to be an operating system bug. Other executions of the same Job will work without issue. This has been fixed in 9.0.6.

User Interface

  • Corrections have been made to the Database Conversion Utility to address issues encountered converting databases from SureSync 7 and older. This has been fixed in 9.0.6.

Return to top of page

SureSync 9.0.4 Known Issues

Version 9.0.4 was posted on July 12, 2022.

File Locking

  • 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 9.0.5.
  • 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 9.0.5.
  • 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 9.0.5.

Scheduler

  • A NullReferenceException error could occur in the Scheduler. This has been fixed in 9.0.5.

SyncLockStatus

  • SyncLockStatus could report that it connected to the server, but no licensing was found when licensing was present in the database. This has been fixed in 9.0.5.

User Interface

  • Corrections have been made to the Communications Agent Import and Job Template functions. This has been fixed in 9.0.5.
  • When moving to the SQL Protection tab, the Desktop would report a “You must specify at least one security item, or no one will be able to access the Jobs in this Group” error. This has been fixed in 9.0.5.
  • 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 9.0.5.

Return to top of page

SureSync 9.0.3 Known Issues

Version 9.0.3 was posted on July 6, 2022.

File Synchronization

  • If you have either of the options to Skip Temporary Files or Skip Hidden and System Files on the Options tab of the Job enabled, subfolders would not be processed. This has been fixed in 9.0.4.
  • The processing of subfolders could be skipped if a case change is detected for a folder during a scan. A re-scan later would pick up the skipped files and folders. This has been fixed in 9.0.4.
  • A Job ran from a Preview panel would produce an error indicating that the JobLog object could not be found. This has been fixed in 9.0.4.
  • Databases that were upgraded from older SureSync versions may not generate Scheduler traces where those traces were requested. This has been fixed in 9.0.4.
  • The database cleanup routines could report history is being deleted, but no progress was being made. This has been fixed in 9.0.4.
  • If you create a UNC path referencing a new server, you may get an error reporting that the Server record was not found. This has been fixed in 9.0.4.
  • When switching tabs in the SureSync Desktop, it was possible to receive a System.NullReferenceException error. This has been fixed in 9.0.4.
  • The Scheduler could potentially confuse UTC and local times in certain circumstances, causing Schedules to not start on their scheduled start time. This has been fixed in 9.0.4.
  • When an action occurred that involved deleting history, such as deleting a root path or deleting a Job, it was possible for the routine cleaning up the history records to loop. This has been fixed in 9.0.4.

Return to top of page

SureSync 9.0.2 Known Issues

Version 9.0.2 was posted on June 3, 2022.

File Locking

  • In rare timing circumstances, when File Locking was enabled, it was possible that a new file could be added, deleted and renamed in manner that might not release a file lock. This can block the copying of the file until the Job is restarted and all locks are released. This has been fixed in 9.0.3.

File Synchronization

  • A System.NullReferenceException error could occur in SyncFiles when disposing a NodeItem class when looking up a new path. This has been fixed in 9.0.3.
  • An error in the Change Journal service within the Communications Agent could cause an event to be missed in rare circumstances. This has been fixed in 9.0.3.
  • A System.NullReferenceException: Object reference not set to an instance of an object error could occur during a rename action that involved a case change on a folder. The error would only occur on a second reference to the renamed folder. This has been fixed in 9.0.3.

Scheduler

  • If a connection to the SQL Server hosting the SureSync database was lost, the Scheduler could loop and would eventually cancel. This would prevent Schedules and Monitors being launched at their appropriate times until the Scheduler was restarted. This has been fixed in 9.0.3.

User Interface

  • If you select a Job within a running Schedule or Real-Time Monitor, right click on the tree node and select “rescan,” the command is rejected with a “Job Package Not Found” error. This has been fixed in 9.0.3.

Return to top of page

SureSync 9.0.1 Known Issues

Version 9.0.1 was posted on May 16, 2022.

File Synchronization

  • A NullReferenceException error could be thrown from the folder handling routine in certain unusual circumstances. This has been fixed in 9.0.2.
  • If you configured a Job to use the publish-subscribe option, you would receive a “dictionary entry not found” error. This has been fixed in 9.0.2.
  • A NullReferenceException might be reported if a Job is aborted during its initialization. This has been fixed in 9.0.2.
  • Corrections were made to the processing of Schedules and Monitors in a multiple Scheduler environment. This has been fixed in 9.0.2.
  • Corrections were made to the Schedulers busy status processing. In scenarios where a computer was very slow to launch a Job run by a Schedule, the Scheduler could incorrectly try and reschedule the Schedule thinking it had been missed. This has been fixed in 9.0.2.
  • In rare timing circumstances, it was possible to receive a “Overlapped I/O event is not in a signaled state” error message. This has been fixed in 9.0.2.

SQL Protection

  • SQL Protection Jobs may not scan the staging folder paths to thin out old versions. This has been fixed in 9.0.2.
  • SQL Protection Jobs could encounter a NullReferenceException error that prevented the thinning of additional full SQL backup copies from the staging folders. This has been fixed in 9.0.2.

User Interface

  • If you create a new computer with the SureSync Desktop and that machine needs a DNS name for access or some other non-default setting, a test of the connection to the agent may fail until you restart the Desktop. This has been fixed in 9.0.2.
  • Improvements have been made to the Usage tab for Computers in the SureSync Desktop. This has been fixed in 9.0.2.
  • If you specify the location of a SQL Server SureSync Database using a period for the server name, if status is displayed on a different machine it will look for the database on the current machine. This has been fixed in 9.0.2.

Return to top of page