SureSync 5
      Back to home
      1. Software Pursuits Support Center
      2. SureSync Documentation
      3. SureSync 5

      SureSync 5 Version History

      Important: SureSync v5 support was discontinued on February 28, 2011

      SureSync 5.0.36 Known Issues

      Version 5.0.36 was posted on December 2, 2009.

      Please see the release notes of SureSync 6.0 for the new features in this major new release.

      SureSync 5.0.35 Known Issues

      Version 5.0.35 was posted on May 27, 2009.

      Desktop

      • In some instances, the SureSync desktop application would fail to display all Relations in the tree because it incorrectly determined that the user lacked permissions. This has been fixed in 5.0.36.
      • The Root Path browse panel would generate local paths incorrectly under Windows 7 and Windows 2008 R2. For example, C:\Test would end up C\Test resulting in errors about being unable to find the path. This has been fixed in 5.0.36.

      File Synchronization

      • The Relative Date Range on the Dates tab of a Rule has been restricted to a maximum of 9,999 days. Larger values would cause SyncFiles to crash. This has been changed in 5.0.36.
      • When running using Publish/Subscribe, IndexOutOfRangeException errors could occur when creating folders. This has been fixed in 5.0.36.
      • A “Primary Key constraint ‘PK_FileActions_Rel_NodeId_FileName'” error could occur when running a job using history or when running a Preview. This has been fixed in 5.0.36.
      • A change was made to prevent Schedules and Monitors from starting while a prior run of the same Relation was still active. This has been fixed in 5.0.36.

      Real-Time Monitors

      • When running a Real-Time Monitor, IndexOutOfRangeException errors could occur if invalid file retry records were queued. Generally, this problem is triggered by changing Relations or Roots under the Monitor. This has been fixed in 5.0.36.

      SureSync 5.0.34 Known Issues

      Version 5.0.34 was posted on March 5, 2009.

      File Synchronization

      • Increased VSS retry time to avoid “VSS Snapshot Busy” errors. This has been fixed in 5.0.35.
      • Minor file locking enhancements. This has been fixed in 5.0.35.

      Preview

      • When performing an override in a Preview, on a file that contains an apostrophe in the file name, a syntax error would occur. This has been fixed in 5.0.35.

      SureSync 5.0.33 Known Issues

      Version 5.0.33 was posted on January 28, 2009.

      Desktop

      • Fixed a display issue with the browse panel for adding or modifying paths under Windows Vista. This has been fixed in 5.0.34.
      • When importing SPIAgent Settings, the test button would fail until closing the SureSync desktop and launching it again. This has been fixed in 5.0.34.

      File Synchronization

      • Fixed a minor licensing issue. This has been fixed in 5.0.34.

      SureSync 5.0.32 Known Issues

      Version 5.0.32 was posted on November 7, 2008.

      Database

      • SQL Server timeout may occur when trying to cleanup Nodes table. Cause unknown. Cleanup will no longer occur automatically. This has been fixed in 5.0.33.

      Desktop

      • “Unexpected error when launching a program. File not found.” error when trying to launch the Job Log, Status or do a Run Job Now when SureSync.exe name had its case altered. This has been fixed in 5.0.33.

      File Synchronization

      • SQLException: The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value errors could occur. This has been fixed in 5.0.33.
      • If a path is missing at the start of a job and it’s the first destination path, then we don’t unnest subfolders when the job is run. This has been fixed in 5.0.33.

      SPIAgent

      • Fixed ReadBuffer timeouts due to slow network. This was resulting in some 900,000 millisecond timeout errors. This has been fixed in 5.0.33.
      • Signal completion when forcing remote agent out of session. This is an improvement for SPIAgent error handling for dropped paths. This has been fixed in 5.0.33.
      • Made a correction to File Locking to release a lock if an ERROR_INVALID_NAME error returned by a file open attempt. This was leaving files in some rare situations locked when they shouldn’t be. This has been fixed in 5.0.33.

      SureSync 5.0.31 Known Issues

      Version 5.0.31 was posted on October 22, 2008.

      Database

      • When using a SQL database, a database upgrade could fail in some instances waiting for SQL to release cached opens on the database. This has been fixed in 5.0.32.

      File Archiving

      • A restore from an Archive might loop if a destination file exists without any corresponding archive file. This has been fixed in 5.0.32.

      File Synchronization

      • FTP destination files may be treated as changed unexpectedly during processing when no change occurred. This happens when replacing files. This has been fixed in 5.0.32.
      • IndexOutOfRangeException error may occur if a file appears to have been changed unexpectedly during processing. This has been fixed in 5.0.32.
      • Initial use of a new path may report that the machine referenced is unlicensed. This has been fixed in 5.0.32.

      Real-Time Monitors

      • Monitors may loop processing the same event over again in some circumstances. This has been fixed in 5.0.32.

      SureSync 5.0.30 Known Issues

      Version 5.0.30 was posted on October 10, 2008.

      Desktop

      • The expand button on the Edit Path dialog was stopping partway through the tree expansion and was never selecting the chosen directory. This has been fixed in 5.0.31.

      File Synchronization

      • Files that didn’t copy because the destination file was in use were still being logged as copied. This has been fixed in 5.0.31.
      • Changes have been made to help prevent dropped paths in a LAN environment. This has been fixed in 5.0.31.

      Real-Time Monitors

      • If one of the paths in a monitor was configured in path options deliberately not to be a monitored path, the monitor wouldn’t use change journal on any of the paths. This has been fixed in 5.0.31.
      • A Primary Key Constraint error could occur in a multi-directional Real-Time Monitor which includes more than two paths. This error would occur when a path dropped and the file was successfully copied to the other paths in the Real-Time Monitor. On retrying the copy to the path which was down, SureSync would attempt to generate file history and action records for all paths resulting in this error. This has been fixed in 5.0.31.
      • In a high volume monitor it was possible to receive a “the conversion of a char data type to a datetime data type resulted in an out of range datatime value” error when a path drop occurred and a large amount of changes needed to be queued. This has been fixed in 5.0.31.
      • Some items in a monitor queue were not being deleted after they were processed causing them to be re-processed. This has been fixed in 5.0.31.

      SPIAgent

      • In some TCP timeout scenarios, the SPIAgent 5 service would crash. This has been fixed in 5.0.31.

      SyncStatus

      • Starting a Schedule from the SyncStatus panel was not always launching the Schedule. This has been fixed in 5.0.31.

      SureSync 5.0.29 Known Issues

      Version 5.0.29 was posted on September 23, 2008.

      File Archiving

      • Archive thinning was generating extra scanning which did not need to be performed. This has been fixed in 5.0.30.

      File Synchronization

      • Scan retries were not being run if the paths in the job were restored before the job was restarted. This has been fixed in 5.0.30.
      • Performance improvements have been made when processing huge numbers of folders. This will increase directory scan speed and generally improve performance in these environments. This has been fixed in 5.0.30.
      • A loop could occur when processing files with an invalid modified date of 0 or no date. This has been fixed in 5.0.30.
      • Subfolders were not being processed if the folder attribute was off. This has been fixed in 5.0.30.

      Real-Time Monitors

      • A loop could occur processing the same queue element in a Real-Time Monitor. This has been fixed in 5.0.30.

      SPIAgent

      • Improved recovery from dropped connections. This has been fixed in 5.0.30.

      SureSync 5.0.28 Known Issues

      Version 5.0.28 was posted on September 3, 2008.

      Database

      • Upgrading or copying a database gives a “null reference exception” error when copying the Servers table. This has been fixed in 5.0.29.
      • Database copies when using an Access database were performing slowly. This has been fixed in 5.0.29.

      File Locking Add-On

      • When using the SPIAgent File Locking add-on, it was possible for some files to remain locked when they shouldn’t be in environments where frequent path drops occurred. This has been fixed in 5.0.29.

      File Synchronization

      • When excluding a subfolder using a skip rule, the files in the excluded subfolders were still being skipped when they should have been synchronized. This has been fixed in 5.0.29.
      • In some situations while copying security, the inherit flag was being incorrectly turned on. This resulted in the security being modified each time the job ran. This has been fixed in 5.0.29.

      Real-Time Monitors

      • “Data type mismatch in criteria expression” errors could occur when recovering a path in a Real-Time Monitor. This has been fixed in 5.0.29.
      • Licensing errors would occur when there were Real-Time Monitors using “(local agent)” and the local machine running SureSync was moved to a different machine. This has been fixed in 5.0.29.
      • It was possible for Real-Time Monitors to get stuck in a directory scanning loop in some instances. The Real-Time Monitor would complete one full directory scan and then start another. This has been fixed in 5.0.29.

      SureSync 5.0.27 Known Issues

      Version 5.0.27 was posted on June 27, 2008.

      Desktop

      • Support has been added to import SPIAgent Setup configuration information in batch mode from a tab delimited text file. See the ‘Batch Import of SPIAgent Settings’ topic in the SureSync help file for detailed information. This has been added in 5.0.28.
      • Support has been added create Relations in a batch mode based off of a “Template Relation”. This can greatly increase the speed of configuring multiple Relations which have the same Relation and Rule settings but different Root Paths. See the ‘Creating Relations Using Templates’ topic in the SureSync help file for detailed information. This has been added in 5.0.28.

      File Archiving

      • Running a Restore Relation by date would give an “index out of bounds” error if it encountered a file added to the archive after the date being restored to. This has been fixed in 5.0.28.

      File Synchronization

      • Attempts to force destination files closed could fail and the files were not replaced. This has been fixed in 5.0.28.
      • Incorrect syntax near TOP errors could occur when loading a Relation from a SQL 2000 database. This caused the job to abort. This has been fixed in 5.0.28.
      • A loop could occur when reading a file with the system attribute turned on. This has been fixed in 5.0.28.
      • SureSync did not properly process files with a modification date of zero. This could result in the job (particularly Real-Time Monitors) appearing to hang on a specific directory containing the problem file. This has been fixed in 5.0.28.
      • Duplicate Key errors could occur on the FileID field in the SureSync database which would cause the job to cancel. This has been fixed in 5.0.28.

      Real-Time Monitors

      • Changing paths in a Relation running under a Real-Time Monitor could cause a full rescan of all paths to occur on every restart of the Real-Time Monitor from that point forward. This has been fixed in 5.0.28.
      • Some files might not have been processed when a monitored path was restored while performing a directory scan. This has been fixed in 5.0.28.
      • Requeued events may be dropped and then would go unprocessed. This has been fixed in 5.0.28.
      • Deleted Row Inaccessible errors could occur when renaming (but not moving) a folder. This has been fixed in 5.0.28.

      SPIAgent

      • Support has been added for multiple IP addresses for a DNS entry. This has been added in 5.0.28.

      SPIAgent File Locking

      • When the SPIAgent File Locking add-on was enabled, the Real-Time Monitor in question would not ignore files and folders based on the File Mask and Rule Subfolder(s) settings properly. This would result in files being synchronized and locked which should not be. This has been fixed in 5.0.28.

      SyncStatus

      • SyncStatus was not displaying User Account Control prompts properly under Windows Vista. This has been fixed in 5.0.28.

      SureSync 5.0.26 Known Issues

      Version 5.0.26 was posted on June 20, 2008.

      Database

      • Database copies now verify and copy valid file history. This has been added in 5.0.27.
      • Orphaned file history was not being correctly purged. This could result in database bloat. This has been fixed in 5.0.27.

      Preview

      • Constraint errors would occur if you performed a Preview and then used the Actions tab. This has been fixed in 5.0.27.
      • Preview was not correctly showing subfolders. This has been fixed in 5.0.27.

      SyncStatus

      • The “wait until” time listed in SyncStatus when a Real-Time Monitor was “between intervals” was off by time zone calculations. This has been fixed in 5.0.27.

      SureSync 5.0.25 Known Issues

      Version 5.0.25 was posted on March 7, 2008.

      Windows 2008 is now supported. This support has been added in 5.0.26.

      Database

      • Upgrading or copying a large SureSync database could fail due to a “too many locks” error. This has been fixed in 5.0.26.

      Desktop

      • When the browse panel failed to load a system icon, it was generating an error rather than displaying a generic icon. This has been fixed in 5.0.26.
      • If a user did not have permissions to view the first group folder listed in the SureSync desktop then the desktop wouldn’t give permission to any of the other group folders listed. This has been fixed in 5.0.26.
      • “This row has been removed from the table” errors could occur when opening or refreshing the SureSync desktop. This has been fixed in 5.0.26.
      • Corrections have been made to the Archive Restore wizard. This has been fixed in 5.0.26.

      File Synchronization

      • It was possible to lose file history if running a multi-mirror and the rule selected subfolders or did not select by folder attribute. This has been fixed in 5.0.26.
      • Errors should not be reported if file sizes differ with the same dates on a Recent Master Copy rule but were being reported. This has been fixed in 5.0.26.
      • If a root path is created by a job, SureSync now purges history to avoid deleting files from the other pre-existing paths in a multi-mirror. This has been fixed in 5.0.26.
      • When adding a path to an existing multi-mirror, if the new path had an old version of a file it was overwriting the more current version on the existing paths. This has been fixed in 5.0.26.
      • SyncCmd was not always starting jobs even if the Scheduler was running. This has been fixed in 5.0.26.
      • Violation of primary key constraint errors could occur when trying to add history for a new subfolder. This has been fixed in 5.0.26.
      • In some cases, when the source file is on a Windows 2000 machine, SureSync would issue an erroneous ‘file changed since initial scan’ message and would not move past the file. This has been fixed in 5.0.26.

      Preview

      • If Preview settings on the Relation was set to “Only actions and errors” and the Relation was previewed, there would be options on the filter tab which were grayed out and shouldn’t be. This has been fixed in 5.0.26.
      • The preview panel could produce a constraint exception error. This has been fixed in 5.0.26.

      Real-Time Monitors

      • Intervals were not always starting on time after being between intervals. This has been fixed in 5.0.26.
      • A real-time monitor was not always increasing the size of the NTFS change journal when encountering journals which were sized to small. This resulted in unnecessary rescans. This has been fixed in 5.0.26.
      • Rename errors were being reported unnecessarily for real-time monitors. This has been fixed in 5.0.26.
      • Folder renames could turn into full copies if a folder was added and then immediately moved or renamed. This has been fixed in 5.0.26.
      • Using Advanced Open File Support with a real-time monitor when copying large files could result in a full file copy not being made. This has been fixed in 5.0.26.
      • The change journal was not being read after a full rescan. This has been fixed in 5.0.26.
      • Subfolders were being scanned unnecessarily on some folder events. This has been fixed in 5.0.26.

      Scheduler

      • More robust error recovery for the Scheduler starting before SQL Server fully started has been added. This has been fixed in 5.0.26.

      SyncStatus

      • The SPIAgent used by SyncStatus was not always being properly disconnected so other agents attempting to communicate with it would receive a timeout error. This has been fixed in 5.0.26.

      SureSync 5.0.24 Known Issues

      Version 5.0.24 was posted on December 7, 2007.

      ArchiveSync

      • When trying to restore from the preview of an Archive Relation, if you select “All paths except source” as the destination you would receive an error stating “you cannot select an archive as a destination for a Restore from an Archive.” This has been fixed in 5.0.25.
      • If a file being archived is zero bytes and the Relation uses CRC on that file, the file will fail validation and not be archived. This has been fixed in 5.0.25.

      Desktop

      • The run time on the Relation statistics tab was being converted from UTC time incorrectly. This has been fixed in 5.0.25.
      • Could not browse a new root path if the path required a user ID and password in path options. It was possible to receive a Null Reference Exception. This has been fixed in 5.0.25.
      • When refreshing a node in the SureSync desktop after starting or stopping a job it was possible to receive a record no longer exists in table error. This has been fixed in 5.0.25.
      • If the alert user panel was launched from the Options panel it would not close properly. This has been fixed in 5.0.25.

      File Synchronization

      • File changed during processing errors could occur. Usually these messages would occur when copying files from a CD. It is possible for them to occur in some other select cases. This has been fixed in 5.0.25.
      • Processing open files without Advanced Open File Support may report that the file has changed during processing. This has been fixed in 5.0.25.
      • If a multi-mirror relation has “add root path if it doesn’t exist” selected in Path Options for an existing path and that path is added later on, files can be deleted unexpected. This has been fixed in 5.0.25.
      • Using Advanced Open File Support on some systems may cause open files to be seen as changed during processing and not copied. This has been fixed in 5.0.25.
      • If a folder is added to a multi-mirror, history was not being updated completely until the second time processing the folder. This has been fixed in 5.0.25.
      • A schedule setup to retry after errors may not always run on time. This has been fixed in 5.0.25.
      • A schedule setup to repeat throughout the day until midnight would not reschedule retries properly when the whole job failed. This has been fixed in 5.0.25.
      • “Unable to copy security” could be reported when renaming a file. This has been fixed in 5.0.25.

      Real-Time Monitors

      • If an interval end time leads into a between intervals space (instead of another interval) that interval may not end on time. This has been fixed in 5.0.25.
      • Renaming a file in a folder that is being monitored may occasionally fail resulting in two copies of the file (one with the old name and one with the new name). This has been fixed in 5.0.25.

      SureSync 5.0.23 Known Issues

      Version 5.0.23 was posted on December 4, 2007.

      SyncStatus

      • Loop would occur in SyncStatus (and possibly other components) if used on a machine that is not in its local database. This happens the first time that SyncStatus is used. This has been fixed in 5.0.24.

      SureSync 5.0.22 Known Issues

      Version 5.0.22 was posted on October 26, 2007.

      Desktop

      • If a user with an apostrophe (single quote) in their username uses SureSync the application would generate a syntax error. This has been fixed in 5.0.23.

      File Synchronization

      • Correction to SuperOpen with standard open files Rules. This has been fixed in 5.0.23.
      • Reset of source archive flag failed if VSS was used. This has been fixed in 5.0.23.
      • Performance improvements for file copies made via UNC path. This has been fixed in 5.0.23.
      • File changed during processing errors could be reported when running from a Preview. This has been fixed in 5.0.23.
      • If SureSync is unable to retrieve volume information, the synchronization would report disk is full. This has been fixed in 5.0.23.

      Real-Time Monitors

      • First run of a Multi-Mirror after a database upgrade from 4.1 was slow. This has been fixed in 5.0.23.
      • Error on BackupRead may be reported when encountering a busy file in a Real-Time Monitor. This has been fixed in 5.0.23.
      • Minor optimizations on Monitor event processing regarding folder rescans. This has been fixed in 5.0.23.
      • An error was reported if a source file changed during processing for a Real-Time Monitor when the message was not necessary. This has been fixed in 5.0.23.
      • Renames when paths are offline in a Real-Time Monitor could cause files to be added back. This has been fixed in 5.0.23.
      • Real-Time Monitor events could be lost when paths are offline. This has been fixed in 5.0.23.
      • Renaming a folder and then quickly renaming it back to the original location with a Multi-Mirror rule in Real-Time could result in files being added back. This has been fixed in 5.0.23.
      • Retry times for open files for a Real-Time Monitor now use the same open file retry time as the Schedules. This has been fixed in 5.0.23.
      • Multi directional Real-Time Monitors will perform an automated full rescan at 1AM local time on the SureSync machine to correct history. This is a one time event. This has been fixed in 5.0.23.

      SyncStatus

      • SyncStatus could report that files were being replaced when the files were actually being added. This has been fixed in 5.0.23.
      • Folder scan process was sometimes not displayed in SyncStatus. This has been fixed in 5.0.23.

      SureSync 5.0.21 Known Issues

      Version 5.0.21 was posted on September 28, 2007.

      Desktop

      • If creating a monitor using the wizard without a mouse, an error was generated when the wizard finished. This has been fixed in 5.0.22.

      File Synchronization

      • File not found may be reported when adding a file and the file exists at the last moment. This has been fixed in 5.0.22.
      • Error when clearing source Archive flag if VSS is used on the file. This has been fixed in 5.0.22.
      • Performance was improved when creating thousands of folders. This has been fixed in 5.0.22.
      • Index out of range error may be reported when job cannot communicate with the SureSync desktop. This has been fixed in 5.0.22.
      • Netware files would report that they had changed during processing. This has been fixed in 5.0.22.
      • Root paths may be incorrectly dropped when a locked folder is encountered. This has been fixed in 5.0.22.

      Real-Time Monitors

      • Eliminated unnecessary “path not found” error for monitors. This has been fixed in 5.0.22.
      • Monitor events may be lost for retries that occurred when a path was offline. This has been fixed in 5.0.22.

      SPIAgent

      • When copying to a remote agent older than 5.0.21, files were not copied and temporary files were left behind. This has been fixed in 5.0.22.

      SureSync 5.0.20 Known Issues

      Version 5.0.20 was posted on July 24, 2007.

      Database

      • Could not copy a database to SQL, the SPI_Control table would not be recognized and the copy process would encounter errors. This has been fixed in 5.0.21.
      • When upgrading or copying a database, in some cases, SureSync would be unable to locate the SPI_Control table. This has been fixed in 5.0.21.

      Desktop

      • The option to specify an amount of time to wait for a script to finish on the Scripts tab was not saving. This has been fixed in 5.0.21.
      • Concurrency errors could occur while using the SureSync desktop which would not clear until the desktop was restarted. This has been fixed in 5.0.21.
      • Copying a Relation would fail. This has been fixed in 5.0.21.
      • Occasionally when you have a Rule node selected in the SureSync desktop tree the property sheet and icon would display Relation information until the next refresh. This has been fixed in 5.0.21.

      File Synchronization

      • Some unnecessary “Root Path Overlap” warnings were eliminated. Some warnings were not reported. This has been fixed in 5.0.21.
      • Better handling of a system shutdown. This has been fixed in 5.0.21.
      • Some “File changed during processing” exceptions were incorrectly reported as errors. This has been fixed in 5.0.21.
      • When editing an existing root path, SureSync may not check licensing information immediately and the job could error with an “unlicensed server” message. This has been fixed in 5.0.21.
      • SyncCmd now waits for a starting Scheduler properly. This has been fixed in 5.0.21.
      • Delta trace log messages were missing. This has been fixed in 5.0.21.

      Real-Time Monitors

      • Monitor events could be lost after a path re-connect if it occurred between monitor intervals. This has been fixed in 5.0.21.
      • Stopping a job that had lost communication with a path wasn’t working correctly. This has been fixed in 5.0.21.
      • Invalid parameter – Drive letter errors were possible if paths were lost from a Real-Time Monitor that was in between intervals. This has been fixed in 5.0.21.

      SPIAgent

      • Performance improvements have been made when using the SPIAgent add-on over slow connections with large amounts of small files. This has been fixed in 5.0.21.

      SureSync 5.0.19 Known Issues

      Version 5.0.19 was posted on May 17, 2007.

      Database

      • A failure to open the SureSync database was not always properly reflected to the user. This has been fixed in 5.0.20.
      • The number of retries when the database gives the error “could not update, currently locked” has been increased. This has been fixed in 5.0.20.
      • If upgrading a SureSync 4.1 database to SureSync 5.0 you could receive a NullReference error. This has been fixed in 5.0.20.
      • SQL deadlock errors could occur in rare cases. This has been fixed in 5.0.20.
      • Minor database upgrade to support additional future functionality. This change has been made in 5.0.20

      Desktop

      • Non-archive Relations should not be changed to Archive Relations. The desktop user interface has been correct to prevent this change from being made. This has been fixed in 5.0.20.
      • Interval overlap warning messages displayed incorrect days for the overlapping intervals. This has been fixed in 5.0.20.
      • The Scripts tab now follows the “convert to UNC path” option defined in Options when handling mapped drives entered into the form. This has been fixed in 5.0.20.

      File Synchronization

      • Subscript out of range errors could occur after requeuing a file that didn’t copy because it had changed since SureSync started processing the file. This has been fixed in 5.0.20.
      • Writing files to an FTP path would cause SyncFiles.exe to crash. This has been fixed in 5.0.20.
      • A timeout on a file read could cause the job to cancel. This has been fixed in 5.0.20.
      • Path UserIDs and passwords defined in Path Options were not used on local paths if defined. This has been fixed in 5.0.20.
      • Advanced Open File Support licenses were not correctly recognized for a multi-way rule. This has been fixed in 5.0.20.

      Real-Time Monitors

      • Folder deletes for a Real-Time Monitor may not be fully processed. This has been fixed in 5.0.20.
      • Events in rapid sequence in a Real-Time Monitor could be ignored if the clocks on the machines were not synchronized. This has been fixed in 5.0.20.
      • Moving a folder from a directory structure being monitored with a Real-Time Monitor to a non-monitored location and then moving it back to a monitored location could in some instances result in events in that folder being ignored. This has been fixed in 5.0.20.
      • An index out of range error could occur when a monitor was reading a new set of queued events. This has been fixed in 5.0.20.

      Scheduler

      • Occasionally specific jobs would stop running and would not be rescheduled until the SureSync Scheduler was stopped and restarted. This has been fixed in 5.0.20.

      SyncStatus

      • SyncStatus could report a “key already exists” error when displaying progress. This has been fixed in 5.0.20.

      SureSync 5.0.18 Known Issues

      Version 5.0.18 was posted on April 19, 2007.

      Database

      • New column on the FileHistory table which was added in an earlier version may not have been filled in properly resulting in Null values in that column which could result in errors being raised. This has been fixed in 5.0.19.
      • Some data (long rule subfolder directory listings or file masks) would be truncated when the database was copied to a new database. This has been fixed in 5.0.19.

      Desktop

      • When changing a schedule to run on specific weekdays or weeks of the month, after clicking apply the settings would be reset to default. This has been fixed in 5.0.19.

      File Synchronization

      • It was possible to get a file lock count exceeded error when trying to purge the job log at the end of a job. This has been fixed in 5.0.19.
      • SPIAgent File Locking add-on released. This new add-on can be found in 5.0.19 and requires an additional license.

      Scheduler

      • In some cases the Scheduler was not properly updating its queue after running a job and some jobs were being skipped. This has been fixed in 5.0.19.
      • Invalid parameter errors when the Scheduler used the agent to communicate. This has been fixed in 5.0.19.

      SureSync 5.0.17 Known Issue

      Version 5.0.17 was posted on March 2, 2007.

      Compatibility

      • SureSync is now compatible with Windows 2003 Service Pack 2 (with 5.0.18 or newer).
      • SureSync is now compatible with Windows Vista (with 5.0.18 or newer).
      • Advanced Open File Support (VSS) is now compatible with Windows 2003 Service Pack 2. This has been fixed in 5.0.18.
      • Advanced Open File Support (VSS) is now compatible with Windows Vista. This has been fixed in 5.0.18.

      Database

      • Upgrading a SQL database from SureSync 4.1 to 5.0 could sometimes fail with a “cannot drop database” error. This has been fixed in 5.0.18.

      Desktop

      • Fixed a desktop display issue where part of the Rule Wizard form was covering the “copy latest” checkbox. This has been fixed in 5.0.18.
      • If you changed just the port number in SPIAgent Setup the Save button was not becoming active. This has been fixed in 5.0.18.

      File Synchronization

      • If a Relation has more than 19 paths it will fail with a “not enough paths” error message. This has been fixed in 5.0.18.
      • Relative date ranges on a rule would generate an error if the value was too large. This has been fixed in 5.0.18.
      • NullReference errors could occur in ReadFileHistory. This has been fixed in 5.0.18.
      • Access Dates are now preserved on file copies if the option “Copy date created and Access date for files copied to this path” is checked in Path Options. This works for both source and destination paths. This has been fixed in 5.0.18.
      • A change of the inherited permissions flag was not always properly recognized. This has been fixed in 5.0.18.
      • NullReference errors could occur when trying to log an agent disconnect error during a file copy. This has been fixed in 5.0.18.
      • Changing a rule to use Advanced Open File Support would cause a license error the first time the Relation was run. This has been fixed in 5.0.18.

      Preview

      • Preview would fail when overriding files with no actions. This has been fixed in 5.0.18.
      • Preview would return a null reference error when overriding from the tree view in some instances. This has been fixed in 5.0.18.
      • Running a Preview when you have a rule selected in the desktop tree can result in a “this row has been removed from a table and does not have any data” error. This has been fixed in 5.0.18.

      Real-Time Monitors

      • Performance improvements have been made on folder renames with Real-Time Monitors. This has been fixed in 5.0.18.

      Scheduler

      • Scheduler could return a “key was not present in the dictionary” error in rare cases. This has been fixed in 5.0.18.
      • The Scheduler control panel in the desktop now works properly with Windows Vista. This has been fixed in 5.0.18.
      • It was possible for the Scheduler to return a “System.InvalidOperationException: Collection was modified; enumeration operation might not execute.” error in the Event Log and then fail to launch jobs. This has been fixed in 5.0.18.

      SyncStatus

      • SyncStatus may get an invalid parameter error “data exceeds SPIAgent buffer size” when launching. This has been fixed in 5.0.18.
      • SyncStatus could occasionally get caught in a loop (become unresponsive) when adding a server or trying to talk to an agent. This has been fixed in 5.0.18.

      SureSync 5.0.16 Known Issues

      Version 5.0.16 was posted on February 6, 2007.

      Database

      • Timeouts could occur on database upgrades. This has been fixed in 5.0.17.

      Desktop

      • If you added a machine name in SPIAgent Settings but canceled before saving it would error out and would have problems until the desktop was restarted. This has been fixed in 5.0.17.
      • If there was a machine name in SPIAgent Settings that sorted before the “Add Machine Name” item in the drop down list then the “Add Machine Name” would no longer function properly. This has been fixed in 5.0.17.
      • In a few cases the desktop tree was constantly blinking with refreshes. This has been fixed in 5.0.17.

      File Synchronization

      • Null Reference Exception “Object reference not set to an instance of an object” was occurring in some instances when trying to get NextFile. This has been fixed in 5.0.17.
      • Loop opening A FTP file if the open fails with certain errors. This has been fixed in 5.0.17.

      Preview

      • Database records from a Preview were not always cleared when the job was run from Preview. This has been fixed in 5.0.17.

      Real-Time Monitors

      • Filtering by file size on Monitors failed to process events on the next interval which were filtered out of the previous interval. This has been fixed in 5.0.17.

      Scheduler

      • The SureSync Scheduler was logging errors and sending alerts for a Schedule being missed when there was actually no problem. This has been fixed in 5.0.17.

      SyncStatus

      • SyncStatus was giving “Invalid Parameter” errors when the user requesting status was a member of a large number of Windows security groups. This has been fixed in 5.0.17.

      SureSync 5.0.15 Known Issues

      Version 5.0.15 was posted on January 3, 2007.

      Database

      • Database performance improvements have been made for previews and multi-directional jobs. This has been fixed in 5.0.16.
      • Performance improvements have been made for databases which contain hundreds of root paths. This has been fixed in 5.0.16.
      • “Invalid Cast Exception” error messages could occur when creating a new database. This has been fixed in 5.0.16.

      Desktop

      • Japanese language files will now update to new versions properly. This has been fixed in 5.0.16.
      • References to the local machine registry key have been removed. This has been fixed in 5.0.16.
      • When first bring up the archive rule dialog, the “recent versions to keep” textbox was not being updated. This has been fixed in 5.0.16.
      • Property updates could be lost during a refresh of items in the user interface. This has been fixed in 5.0.16.

      File Synchronization

      • Erroneous “attempted to read or write from protected memory” errors could occur when trying to access a FTP root when the user does not have appropriate permissions. This has been fixed in 5.0.16.
      • User name and password supplied in Path Options was not always submitted to non-Windows paths which would lead to problems accessing that non-Windows path. This has been fixed in 5.0.16.

      Real-Time Monitors

      • Security changes in a multi-directional rule will now use the event location as the source instead of comparing file access dates. This has been fixed in 5.0.16.
      • Database connection closed errors can occur between monitor intervals at midnight. This has been fixed in 5.0.16.
      • “Configuration Registry Key is Invalid” errors could occur. This has been fixed in 5.0.16.

      Scheduler

      • In some cases every day schedules were being incorrectly rescheduled two days later instead of to the next day. This has been fixed in 5.0.16.

      SyncStatus

      • If displaying status of a job when the SureSync Scheduler shuts down SyncStatus could generate an “index out of range” error. This has been fixed in 5.0.16.

      SureSync 5.0.14 Known Issues

      Version 5.0.14 was posted on December 11, 2006.

      Database

      • When upgrading a SQL database to 5.0 it was possible for an error “The file named is already in use.” to occur. This has been fixed in 5.0.15.

      Desktop

      • When you edit a monitor interval and use the “Select All” button you would receive a “The value of ‘7’ is not valid for index.” error. This has been fixed in 5.0.15.
      • When you edit a root path for a Relation and check the button to select a path in the tree, the nodes of the freshly expanded tree would be out of order. This has been fixed in 5.0.15.
      • Changing a path on the Roots tab of a Rule would not always activate the “Apply” and “Cancel” buttons. This has been fixed in 5.0.15.
      • Japanese language translations updated. This has been fixed in 5.0.15.
      • Users were able to create jobs in the SureSync database that they lacked permission to access once created. A user must have Modify or greater permissions to create a job. This has been fixed in 5.0.15.
      • New Restore Relations were not placed in the proper group folder. This has been fixed in 5.0.15.
      • When a Scheduler rescheduled a Schedule or put it on hold it wasn’t always properly notifying the desktop. This could cause concurrency errors when a user tried to update properties for the changed Schedule. This has been fixed in 5.0.15.

      File Archiving

      • Archive licensing was not properly recognized for a machine that is both an Archive source and destination. This has been fixed in 5.0.15.

      File Synchronization

      • It was possible for “primary key violation” errors to occur on the Servers table of the SureSync database when running Real-Time Monitors. This has been fixed in 5.0.15.
      • Minor FTP corrections were made. This has been fixed in 5.0.15.

      Preview

      • Preview performance improvements when a Multi-Mirror rule is used. This has been fixed in 5.0.15.

      SyncStatus

      • If multiple Schedulers are running using the same database SyncStatus was showing all jobs under every server whether they were running there or not. This has been fixed in 5.0.15.

      SureSync 5.0.13 Known Issues

      Version 5.0.13 was posted on November 10, 2006.

      Desktop

      • The browse trees were not always being sorted properly. This has been fixed in 5.0.14.
      • Errors would occur when changing from a Multi-Mirror rule to a Mirror rule if you failed to set a source path. This has been fixed in 5.0.14.
      • If you delete and add a path to an existing relation (at the same time) and the deleted path causes a rule to be deleted, the changes to the paths would error out and would not let you save. This has been fixed in 5.0.14.
      • Fixes to the Japanese translations. This has been fixed in 5.0.14.

      File Archiving

      • Archive delete events may be recorded out of sequence. This has been fixed in 5.0.14.

      File Synchronization

      • If the agent was changed for a Root Path with history, the user was not being asked if history should be purged. This has been fixed in 5.0.14.
      • May have some data integrity problems with synchronizations with an FTP source and a non-FTP destination. This has been fixed in 5.0.14.
      • Jobs with root paths that used mapped drives (not UNC) were sometimes failing to find the path when the synchronization was run. This has been fixed in 5.0.14.

      Preview

      • Constraint errors could occur on a preview or multi-mirror when a folder is missing. This has been fixed in 5.0.14.
      • Null reference errors could occur when performing overrides in the preview from the node tree. This has been fixed in 5.0.14.

      Real-Time Monitors

      • In some cases when running a monitor using a SQL database the error “@paramRelationID is not a parameter for procedure DelQueueDups#” could occur. This has been fixed in 5.0.14.
      • When a user moves a file from a monitored folder to a folder excluded from the monitor by a rule, instead of removing the file from the matching paths on the other roots it would attempt an attribute change on the non-existing source file. This has been fixed in 5.0.14.
      • Undefined message 753 showing up in the job log when a monitor is connecting to an agent in some instances. This has been fixed in 5.0.14.
      • Violation of primary key constraint errors were possible when trying to write file history which could result in the monitor being canceled. This has been fixed in 5.0.14.

      SyncStatus

      • Null reference errors could occur when SyncStatus was closed while SyncFiles was in the middle of sending a status update. This has been fixed in 5.0.14.

      SureSync 5.0.12 Known Issues

      Version 5.0.12 was posted on October 9, 2006.

      Database

      • Upgrading a SQL database would error out if the database name contains a – (dash) character. This has been fixed in 5.0.13.

      Desktop

      • The invert button on the Add/Edit Intervals form caused an error. This has been fixed in 5.0.13.
      • Displaying Archive Rules may generate an error when the Rule contains a value of zero days. This has been fixed in 5.0.13.
      • Errors could occur when browsing Rule Subfolders. This has been fixed in 5.0.13.
      • Opening database with hundreds of Relations or Paths was slow. This has been fixed in 5.0.13.

      File Synchronization

      • Netware servers may show as unlicensed. This has been fixed in 5.0.13.
      • Insufficient disk space may be reported for Unix NFS servers. This has been fixed in 5.0.13.

      Preview

      • Preview totals did not include files that just need security or attribute changes. This has been fixed in 5.0.13.
      • Obsolete history was not always being purged and this caused confusion in the preview display and constraint errors. This has been fixed in 5.0.13.

      SureSync 5.0.11 Known Issues

      Version 5.0.11 was posted on September 13, 2006.

      Database

      • There were problems upgrading databases which contained null values in some database fields. This has been fixed in 5.0.12.

      Desktop

      • The toolbar button to display selected job log wasn’t selecting the appropriate job. This has been fixed in 5.0.12.
      • Running jobs from the desktop could result in a job initialization failure and a “duplicate operand” error in some cases. This has been fixed in 5.0.12.
      • When browsing for a rule subfolder the checkboxes for which subfolders to include were not always correctly marked. This has been fixed in 5.0.12.
      • Turning off tool tips from the view menu didn’t work. This has been fixed in 5.0.12.
      • Importing paths would cause the desktop to freeze. This has been fixed in 5.0.12.

      File Synchronization

      • In a multi-mirror where a file was deleted on 2 or more paths the rule would incorrectly add the file back instead of deleting it from the remaining paths. This has been fixed in 5.0.12.
      • The verify licenses process took too long. This has been fixed in 5.0.12.
      • SureSync will now report undetermined license types. This has been added in 5.0.12.

      Preview

      • Preview could encounter “failed to enable constraint” errors when increasing the items to be displayed. This has been fixed in 5.0.12.

      Real-Time Monitors

      • Real-Time Monitors could go into a scan loop if more than 5,000 events are queued along with other unusual circumstances. This has been fixed in 5.0.12.

      Scheduler

      • Scheduler did not always start in a timely fashion. This has been fixed in 5.0.12.

      SyncCmd

      • SyncCmd /XStart would not always start the defined job. This has been fixed in 5.0.12.
      • Remote agents can now be updated using SyncCmd. This has been added in 5.0.12.

      SyncStatus

      • Null reference exception errors could occur in SyncStatus. This has been fixed in 5.0.12.

      SureSync 5.0.10 Known Issues

      Version 5.0.10 was posted on September 11, 2006.

      Desktop

      • Group Folder security may be cleared when a job starts. This has been fixed in 5.0.11.

      File Synchronization

      • History may not be updated properly in some instances for a multi-mirror. This has been fixed in 5.0.11.

      Preview

      • Unable to override a “changed in multiple paths” error using the preview application. This has been fixed in 5.0.11.

      SureSync 5.0.9 Known Issues

      Version 5.0.9 was posted on August 18, 2006.

      Database

      • Database performance improvements for multi-mirror and exchanging copies rule types have been made. This improvement has been made in 5.0.10.

      Desktop

      • Errors were reported if a user was a member of a security group which contained a quote mark. This has been fixed in 5.0.10.
      • Null reference errors were possible when selecting groups. This has been fixed in 5.0.10.
      • After saving a change in the SureSync desktop frequent changes clicking on a node could cause the desktop to ask to save changes again even if no changes were made. This has been fixed in 5.0.10.
      • Changing a Rule would ask if a preview should be run but it would not properly check to see if a Scheduler was running. This has been fixed in 5.0.10.
      • The SPIAgent Configuration Utility could not set the Multicast option properly. This has been fixed in 5.0.10.

      File Synchronization

      • Using CRC for open files is now the default option for new Relations. If you want CRC checks to be performed on open files for an existing Relation you must specify this option manually on the Performance tab of the Relation in question. This change has been made in 5.0.10.

      Preview

      • Run from a preview may not process all files when overrides were used. This has been fixed in 5.0.10.

      Real-Time Monitors

      • In some instances monitor events may be lost for the local agent if a full scan is performed. This has been fixed in 5.0.10.
      • Unnecessary folder rescans could be triggered from a dropped path on an archive run in a real-time monitor. This has been fixed in 5.0.10.
      • Errors could occur when renaming folders in a multi-mirror Real-Time Monitor. This could result in the Monitor being placed on hold. This has been fixed in 5.0.10.
      • Change events for a Real-Time Monitor could be lost if there were multiple Intervals configured with gaps of time between them. This has been fixed in 5.0.10.

      Scheduler

      • If the SQL service was not fully initialized when our SureSync Scheduler service attempted to start our service would not retry and would not error out which resulted in an unresponsive SureSync Scheduler service. This has been fixed in 5.0.10.
      • The SureSync Scheduler was not stopped before a compact was performed on an Access database. This has been fixed in 5.0.10.

      SureSync 5.0.8 Known Issues

      Version 5.0.8 was posted on August 17, 2006.

      Preview

      • In some instances jobs would not run when launched from the Preview panel. This has been fixed in 5.0.9.
      • Index out of range errors could occur when running a restore job from a preview. This has been fixed in 5.0.9.
      • When previewing a job which was missing a root path the Preview would not be properly notified that the job was canceled. This would result in the Preview panel becoming unresponsive. This has been fixed in 5.0.9.

      SPIAgent

      • The SPIAgent would fail to initialize if a selected set of IP addresses is used in the SPIAgent Configuration Utility. This has been fixed in 5.0.9.

      SureSync 5.0.7 Known Issues

      Version 5.0.7 was posted on July 31, 2006.

      Alerts

      • Null reference errors could occur at the end of a job when trying to send an e-mail alert (if one was configured). The alert was then not sent. This has been fixed in 5.0.8.

      Desktop

      • The SureSync desktop was unable to update Schedules or Monitors if the description field contained the “[” character. This has been fixed in 5.0.8.

      File Synchronization

      • It was possible for “ASyncMsgSent request when request is already busy” errors to occur in some instances. This has been fixed in 5.0.8.
      • Duplicate key errors could occur with a Multi-Mirror. This has been fixed in 5.0.8.

      Preview

      • Constraint errors could occur when previewing an archive or restore job. This has been fixed in 5.0.8.

      Real-Time Monitors

      • Real-Time Monitors were unable to monitor paths local to an agent if they were represented in UNC path format. Please remember that in a Real-Time Monitor each path must be referenced using the SPIAgent on that machine. This has been fixed in 5.0.8.
      • Real-Time Monitors may not be restarted when a machine is rebooted in some rare cases. This has been fixed in 5.0.8.
      • It was possible for multi-mirror Real-Time Monitors to retain old folder names during a rename or it may not delete folder contents. This has been fixed in 5.0.8.
      • Change journal use was discontinued if a root path was offline when a Monitor started. This has been fixed in 5.0.8.
      • Monitor events could be ignored in some unusual cases, especially when clocks on the machines involved are not properly synchronized. This has been fixed in 5.0.8.
      • Object not set errors could occur when reconnecting a path to a Monitor. This has been fixed in 5.0.8.

      Scheduler

      • There were problems with multiple schedulers sharing the same database. This has been fixed in 5.0.8.
      • The SureSync Scheduler may fail to launch in some rare cases. This has been fixed in 5.0.8.

      SureSync 5.0.6 Known Issues

      Version 5.0.6 was posted on July 13, 2006.

      Database

      • In some cases, converting a database with relative date ranges specified on a rule will cause an error when the job is run (or the Dates tab of the rule is displayed). Databases that have already been converted prior to this fix should be checked for valid date ranges on the Dates tab of the Rule. This has been fixed in 5.0.7.
      • The SureSync database could bloat in size due to a logging loop. This has been fixed in 5.0.7.

      Desktop

      • Adding a group folder via right click causes an error #91 object reference not set to an instance of an object. This has been fixed in 5.0.7.
      • Fixed minor display issues. This has been fixed in 5.0.7.
      • Object not set errors when creating a root path could occur in some instances. This has been fixed in 5.0.7.
      • If local groups were used in group folder security the group membership was not being resolved correctly. This has been fixed in 5.0.7.
      • Group folder security “select user or group” dialog box would search only by common name and not by user name. This has been fixed in 5.0.7.
      • Default group folder security on the creation of a database has been modified (when the machine is a member of a domain) to be the user that creates the database, the domain administrators group, and the local administrators group. This allows you to use a local administrator account to run the Scheduler without the need for modifying security. If you want stricter security settings for your database this can be changed in the SureSync desktop after database creation. If the machine is standalone the permissions remain the user who created the database and the local administrators group. This has been fixed in 5.0.7.
      • User and group accounts in the security tabs were being represented in an incorrect format. This has been fixed in 5.0.7.

      File Synchronization

      • Improved performance of multi-mirror jobs. This has been fixed in 5.0.7.
      • The memory requirement has been reduced for multi-mirror jobs which contain a huge number of files. This has been fixed in 5.0.7.

      Real-Time Monitors

      • When a monitor stops due to a system shutdown it was being placed on hold instead of restarting when the system was rebooted. This has been fixed in 5.0.7.
      • Fixed problems with real-time monitor recovery. This has been fixed in 5.0.7.
      • Monitor events for publish\subscribe rules may be ignored in some instances. This has been fixed in 5.0.7.

      SyncStatus

      • SyncStatus could produce a object not set error when canceling a job in some instances. This has been fixed in 5.0.7.

      SureSync 5.0.5 Known Issues

      Version 5.0.5 was posted on July 11, 2006.

      Database

      • During a database upgrade some Scheduler names would be incorrectly converted to “Unknown” on the Options tab of Schedules or Monitors. Schedules or Monitors referencing this “Unknown” Scheduler would not be started. This has been fixed in 5.0.6.

      Desktop

      • When deleting a Rule or other object from the desktop tree, the tree may not be displayed properly until refreshed. This has been fixed in 5.0.6.
      • An error may be reported when a change is made on the desktop to a job while that job was starting or stopping. This has been fixed in 5.0.6.

      Real-Time Monitors

      • New or modified Monitors were not performing a full directory scan before switching to change journal monitoring. This has been fixed in 5.0.6.

      SureSync 5.0.4 Known Issues

      Version 5.0.4 was posted on June 23, 2006.

      Desktop

      • Fixed a few minor display issues. This has been fixed in 5.0.5.
      • Loading the security user list for group folder security was taking too long with large domains. This has been fixed in 5.0.5.

      File Archiving

      • Constraint errors may occur when previewing an archive job with an existing archive. This has been fixed in 5.0.5.
      • “Out of sequence” errors may occur when running an archive job from a preview. This has been fixed in 5.0.5.
      • “Object reference not set to an instance of the object errors occurred when trying to select a version of an archived file to restore from a preview. This has been fixed in 5.0.5.

      Job Log

      • Errors could occur in a job log export if SureSync was using a SQL database. This has been fixed in 5.0.5.

      Real-Time Monitors

      • Error writing queued event errors could occur if a monitor was started between intervals. This has been fixed in 5.0.5.

      Scheduler

      • The SureSync Scheduler may loop on start or fail to start. This has been fixed in 5.0.5.
      • The SureSync Scheduler install process was leaving a log on the desktop. This has been fixed in 5.0.5.

      SyncCmd

      • SyncCmd may report a constraint error when starting a job. This has been fixed in 5.0.5.

      SyncStatus

      • Destination paths were not being displayed in SyncStatus for some jobs. This has been fixed in 5.0.5.
      • If job initialization timed out for a job then SyncStatus would not notify the user. This has been fixed in 5.0.5.
      • If a job being displayed in SyncStatus terminated unexpectedly SyncStatus would not notify the user. This has been fixed in 5.0.5.
      • The tree of jobs in SyncStatus was not being sorted properly. This has been fixed in 5.0.5.

      SureSync 5.0.3 Known Issues

      Version 5.0.3 was posted on June 9, 2006

      Desktop

      • Column length errors may occur if you exit the desktop when a rule is selected which contains many file masks. This has been fixed in 5.0.4.
      • Errors could occur when re-sequencing rules. This has been fixed in 5.0.4.

      Database

      • Database security values could be lost when copying the database from Jet to SQL. This has been fixed in 5.0.4.

      File Archiving

      • Archived files were not always being thinned evenly if created at regular intervals. This has been fixed in 5.0.4.

      File Synchronization

      • Moving a folder and then moving it immediately back to the old location could cause the monitor to terminate only when the monitor was copying security. This has been fixed in 5.0.4.
      • “Entry with same key exists” errors could occur in a Relation with an unusual Rule sequence. This has been fixed in 5.0.4.

      Preview

      • Overrides from the preview were being ignored in the root folder. This has been fixed in 5.0.4.
      • A constraint error could occur during a preview. This has been fixed in 5.0.4.

      SPIAgent

      • Deltas were not being used if only a small change at the start of a file was made. This has been fixed in 5.0.4.
      • A SPIAgent license was sometimes incorrectly required for the local agent. This has been fixed in 5.0.4.

      SyncStatus

      • If you try to cancel a job from SyncStatus right after selecting it in the tree, it sometimes was unable to pause or stop the job. This has been fixed in 5.0.4.
      • When starting a job manually from SyncStatus it was not automatically selecting the job from the tree once the job was running. This has been fixed in 5.0.4.