April 16th, 2010File Synchronization:
· A job could encounter an "Error on BackupRead. The parameter is incorrect." error in rare circumstances. This has been fixed in 6.0.9.
· A Schedule could get "stuck" when moving between Relations when a Schedule was configured to run multiple Relations. The job would have to be terminated through Task Manager. This has been fixed in 6.0.9.
· If a file system reported that it supports named data streams but the BackupRead API returned a not supported message, it was possible in rare circumstances to get a zero length destination file copy. This has been fixed in 6.0.9.
· When performing a folder rename in a Multi-Mirror rule, it was possible to encounter a "Missing FileActions row" error message. This has been fixed in 6.0.9.
· If using Advanced Open File Support and processing a open file which changes constantly, it was possible to have that file copy not be processed in a timely manner. The file would keep getting queued for retry until the activity slowed down because the file would change between the Rule being processed and the VSS snapshot being opened. This has been fixed in 6.0.9.
Job Log:
· Job log messages were being time stamped with the time they were entered into the log instead of the completed time of the action. This would cause entries to appear out of order in situations such as a path drop. This has been fixed in 6.0.9.
Licensing:
· SureSync was allowing workstation licenses to be activated when only server licenses were present. This would cause issues activating the servers because the workstations had used those licenses. This has been fixed in 6.0.9.
· Corrections have been made to the licenses panel to display workstation license information more clearly. This has been fixed in 6.0.9.
Real-Time Monitors:
· When a Real-Time Monitor encountered an error which should have placed the Monitor on hold, the Monitor would sometimes restart again. This could result in the Monitor looping through the error and restart process. This has been fixed in 6.0.9.
· When a path was dropped from a Real-Time Monitor, the path could be immediately dropped again. Recovery would happen fully on the second retry. This has been fixed in 6.0.9.
· "System.IndexOutOfRangeException: Index was outside the bounds of the array." error messages could occur in a Real-Time Monitor which is configured to not use history. This has been fixed in 6.0.9.
SPIAgent:
· If you configure the local agent in SPIAgent Setup with a DNS name, SureSync would be unable to communicate with the local agent. This has been fixed in 6.0.9.
SPIAgent File Locking:
· If you are monitoring subfolders with a Rule in a Real-Time Monitor with file locking enabled, an "ANotFound" error could occur when attempting to release locks. This has been fixed in 6.0.9.
· When creating a new folder or file using a right click with file locking enabled, it was possible for a lock to not be released. This has been fixed in 6.0.9.
· Please note that 6.0.9 includes a new version of the SPIAgent File Locking Add-on file filter driver. This will require a reboot of each machine when you're applying the upgrade.
April 16th, 2010· File Synchronization
· Advanced Open File Support through VSS was generating errors on 64-bit Windows 2003 machines. This has been fixed in 6.0.8.
· When processing a job, SQL errors could be generated when encountering folder names containing a single ' character. This would cancel the job. This has been fixed in 6.0.8.
· When using a source path that is a VMWare based Virtual Server, it was possible for the operating system to be incorrectly identified as Netware. This resulted in errors enumerating the contents of the folders. This has been fixed in 6.0.8.
· Licensing
· An error in the database upgrade process was clearing server/workstation indicators. This could allow someone to activate a workstation as a server, leading to a licensing problem. This has been fixed in 6.0.8.
· SureSync was incorrectly requiring activation for workstation destinations when using a workstation license. This has been fixed in 6.0.8.
· Real-Time Monitors
· File and folder renames were not always being processed correctly, particularly when the rename was simply a case change. This has been fixed in 6.0.8.
· When running a Real-Time Monitor, the job could generate "System.Data.DeletedRowInaccessibleException" error messages. This has been fixed in 6.0.8.
· When running a Real-Time Monitor which uses Intervals, the Monitor could generate System.NullReferenceException when going between Intervals. This has been fixed in 6.0.8.
· The SureSync desktop will now display that it is "(Between Intervals)" on the Desktop and in the Detailed Status panel. This display had been removed and has been put back. This has been fixed in 6.0.8.
· SPIAgent Add-On
· A job could hang when the connection a source SPIAgent was lost. This has been fixed in 6.0.8.
· A couple of situations where the SPIAgent service would generate 500 repeated errors resulting in the service being stopped with a message "**** Process terminated due to too many error messages. ****" existed. This has been fixed in 6.0.8.
· SPIAgent File Locking Add-On
· With the SPIAgent File Locking Add-on, it was possible to encounter "SPIAgent Return code=ANotFound" errors when releasing a lock. This has been fixed in 6.0.8.
· User Interface
· In some circumstances, the job log viewer would not display the job log records for a Relation, Schedule or Monitor even though the log entries existed in the database. This has been fixed in 6.0.8.
· When previewing a stand-alone Relation, that previewed job could be displayed in Enterprise Status causing problems with the operation of the Enterprise Status panel. This has been fixed in 6.0.8.
· If a Relation had been run in only a Real-Time Monitor, the date on the Statistics tab of the Relation would report 1/1/1900 or later. This has been fixed in 6.0.8.
· Using the Test button in Tools | SPIAgent Setup to test to a machine accessed via UNC path would result in an internal error occurring. This has been fixed in 6.0.8.
· If the user defines a custom location for User Interface traces, this value was not always being used immediately. This has been fixed in 6.0.8.
· When removing a server from the list in Enterprise Status, a SQL error could be generated and the server would not be removed. This has been fixed in 6.0.8.
· Please note that 6.0.8 includes a new version of the SPIAgent File Locking Add-on file filter driver. This will require a reboot of each machine when you're applying the upgrade.
April 16th, 2010· Desktop
· In some circumstances, the SureSync desktop would sit on "Loading Registry Settings" for minutes before proceeding. This has been fixed in 6.0.7.
· When browsing the Network node in the Add a Root Path or Edit a Root Path panels, some machines in the list could be duplicated. This has been fixed in 6.0.7.
· When importing a permanent license, the license could be incorrectly marked with an expire date. Please re-import your license to solve this problem. This has been fixed in 6.0.7.
· If a Root Path was modified in any way with a SureSync installation without ArchiveSync licenses, the "Do Not Monitor Path" option would get turned off and the desktop would prohibit you from turning it back on. This results in Monitors not picking up changes from that path. This has been fixed in 6.0.7.
· File Locking
· When using the SPIAgent File Locking Add-on, it was possible to encounter an "ANotFound" error when attempting to release a lock. This has been fixed in 6.0.7.
· In some circumstances, when deleting files with the SPIAgent File Locking Add-on enabled, files within the Root Path which were not actually open would be locked. This has been fixed in 6.0.7.
· When adding a large number of folders and files to a Real-Time Monitor with File Locking enabled, it was possible for some locks to not be released until the Monitor is stopped. This has been fixed in 6.0.7.
· When viewing a Real-Time Monitor with File Locking enabled in Detailed Status, it was possible to receive a System.InvalidOperationException: DataTable internal index is corrupted error when a large amount of locks were being displayed at once. This has been fixed in 6.0.7.
· FTP
· When using FTP, the connection could be timed out by the FTP server during a directory scan. Changes have been made to prevent the timeout. This has been fixed in 6.0.7.
· When using FTP, status was not being reported correctly. This has been fixed in 6.0.7.
· Real-Time Monitors
· Made corrections to Real-Time Monitor File History when one or more paths were dropped and file changes occurred during the path drop. A full rescan of all Real-Time Monitors is recommended to ensure all files have been synchronized. This has been fixed in 6.0.7.
April 16th, 2010· 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.
April 16th, 2010· 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.
April 16th, 2010· 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.
April 16th, 2010· 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 JobLog, 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.
April 16th, 2010· 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.
April 16th, 2010· 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 Contraint 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.
April 16th, 2010· 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 Montiors
· 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.
April 16th, 2010· 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.
April 16th, 2010· 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 (particuarly 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 Inaccessable 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.
April 16th, 2010· 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 calcuations. This has been fixed in 5.0.27.
Find us on Google+
