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.
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 Latest Version (9.0.9)
Version 9.0.9 was posted on March 26, 2023.
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.8 Known Issues
Version 9.0.8 was posted on February 6, 2023.
- 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.
- 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.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- A NullReferenceException error could occur in the Scheduler. This has been fixed in 9.0.5.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 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.
- 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