Features | Add-ons | Bundles | Literature | Licensing | System Requirements | Support

SureSync Support: Known Issues

The latest version of SureSync is 6.0.14. All problems and issues reported for prior versions have been resolved and corrected.

Software Pursuits makes every effort to resolve any issues with SureSync as quickly as possible. Because we know that fixes can not always be instantaneous, we always keep our users informed of any known problems or issues with SureSync that we are working to fix for our next release. For additional information on our release policy click here.

We send an e-mail notification to users when a critical error is found or when a significant version change is released. (You gave us your e-mail address when you downloaded SureSync. If you suspect that we do not have your current email address, please contact our support staff.)  We will not release your address to other companies. Please see our Privacy policy.

Below is our current list of known issues for all versions of SureSync. Unless otherwise indicated, the problems listed for each earlier version were fixed in the later versions. Patches are generally not provided for prior versions, but upgrading to the latest version is even easier than applying a patch.

You can determine your SureSync version by accessing Help, About when running any of the SureSync programs.

Issues affecting all versions   Version 6.0.14 (Latest Version)     Version 6.0.13 Version 6.0.12 Version 6.0.11 Version 6.0.10 Version 6.0.9 Version 6.0.8 Version 6.0.7 Version 6.0.6     Version 5.0.36 Version 5.0.35 Version 5.0.34 Version 5.0.33 Version 5.0.32 Version 5.0.31 Version 5.0.30 Version 5.0.29 Version 5.0.28 Version 5.0.27 Version 5.0.26 Version 5.0.25 Version 5.0.24 Version 5.0.23 Version 5.0.22 Version 5.0.21 Version 5.0.20 Version 5.0.19 Version 5.0.18 Version 5.0.17 Version 5.0.16 Version 5.0.15 Version 5.0.14 Version 5.0.13 Version 5.0.12 Version 5.0.11 Version 5.0.10 Version 5.0.9 Version 5.0.8 Version 5.0.7 Version 5.0.6 Version 5.0.5 Version 5.0.4 Version 5.0.3 Version 4.1.37 Version 4.1.36 Version 4.1.35 Version 4.1.34 Version 4.1.33 Version 4.1.32 Version 4.1.31 Version 4.1.30 Version 4.1.29

Version 4.1.28 Version 4.1.27 Version 4.1.26 Version 4.1.25 Version 4.1.24 Version 4.1.23 Version 4.1.22 Version 4.1.21 Version 4.1.20 Version 4.1.19 Version 4.1.18 Version 4.1.17 Version 4.1.16 Version 4.1.15 Version 4.1.14 Version 4.1.13 Version 4.1.12 Version 4.1.11 Version 4.1.10 Version 4.1.9 Version 4.1.8 Version 4.1.7 Version 4.1.6 Version 4.1.5 Version 4.1.4 Version 4.1.3   Version 4.0.22 Version 4.0.21 Version 4.0.20 Version 4.0.19 Version 4.0.18 Version 4.0.17 Version 4.0.16 Version 4.0.15 Version 4.0.14 Version 4.0.13   Version 3.1.19 Version 3.1.18 Version 3.1.17 Version 3.1.16 Version 3.1.15 Version 3.1.14

The last portion of the version number reflects the application of fixes and patches. Feature changes usually change the middle section of the version number.

Back to prior page

---

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 6.0 requires current Microsoft technologies as outlined on the SureSync System Requirements page. The installer will check to see if your system meets these requirements. If it does not it will offer to install them for you.

Zip Magic

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

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

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

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

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

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

Return to top of page

---

Known Issues in Latest Version (6.0.14)

Version 6.0.14 was posted on July 6, 2010.

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

Version 6.0.13 was posted on June 11, 2010.

File Synchronization

• When using multi-directional Rules, a "changed in multiple locations" warning could be generated erroneously. This occurred only when a directory scan was broken into pieces due to performance of the scan or file locking being enabled. This has been fixed in 6.0.14.
• In some circumstances, the calculation of a root folder scan time was skipped which caused incorrect values to be used when determining if a folder scan would be more efficient than reading change journal entries. This could result in extra folder scans occurring. This has been fixed in 6.0.14.
• Extraneous error messages could be reported when Advanced Open File Support is enabled. In a monitor, with Advanced Open File Support turned on, a file copy could be performed successfully and an error still reported in the job log indicating that the file was not copied. This would be followed by the correct message indicating a successful copy. This has been fixed in 6.0.14.
• With multi-directional Rules, the file history was not always deleted from the database properly for a folder that was deleted. This has been fixed in 6.0.14.

SPIAgent File Locking

• When using SPIAgent File Locking, a Real-Time Monitor could encounter a deadlock situation when attempting to release a lock. When this occurs, the monitor would become unresponsive and would have to be stopped with "End Process". This has been fixed in 6.0.14.
• When using SPIAgent File Locking, if multiple users locked the same file that allows multiple user access, such as an Access database, the locks were not properly reported in status. This has been fixed in 6.0.14.
• When using SPIAgent File Locking, file and folder deletes were generating locks unnecessarily. These locks were not always released properly. Deletes will no longer generate locks. This has been fixed in 6.0.14.
• When using SPIAgent File Locking, file and folder renames could trigger a delete and add instead of a rename. This has been fixed in 6.0.14.
• When using SPIAgent File Locking, cases could occur where a lock would not be released after a file closed. This has been fixed in 6.0.14.

Please note that 6.0.14 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 if your machines are running with the file locking Add-on.

Return to top of page

---

SureSync 6.0.12 Known Issues

Version 6.0.12 was posted on June 3, 2010.

File Synchronization

• When a rescan of an individual Relation with in a Real-Time Monitor is requested, the Relation may not be scanned. Scanning the entire Monitor or from within a Schedule worked properly. This has been fixed in 6.0.13.
• In certain timing situations, a Schedule could hang when a Relation ends while retries are pending. The user could still cancel the Relation and the Schedule would continue. This has been fixed in 6.0.13.
• If an individual job had thousands of records in the job log, the database could timeout while attempting to purge out the records when they become obsolete. This has been fixed in 6.0.13.
• The synchronization engine could loop and consume 100% of the CPU during certian file retry operations until the retry succeeds. This issue is more likely to be common when file locking is used. This has been fixed in 6.0.13.

Installer

• The installer was failing to install the SPIAgent File Locking components on Windows 2008 R2 machines due to a change in the installer application used to build the installer. This problem was introduced in 6.0.12. This has been fixed in 6.0.13.

Real-Time Monitors

• In certain circumstances, a Real-Time Monitor could encounter an "Error: System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_FileHistory_Rel_FileId_RootNumber'. Cannot insert duplicate key in object 'dbo.FileHistory'." message which would cancel the Monitor and place it on hold. This has been fixed in 6.0.13.

SPIAgent

• A SPIAgent service could crash when handling a large number of sessions at the same time. This has been fixed in 6.0.13.
• "Logon as batch job" rights were being enforced for connecting to a SPIAgent. While "logon as batch job" rights are recommended for the logon accessing an Agent, things will work OK without it. The user would see a "You have successfully communicated with the SPIAgent service on [machine name] but your login credentials failed" error on a Test in SPIAgent Setup and SPIAgent Return Code="AAPIError" messages trying to browse to paths on the SPIAgent machine. This has been fixed in 6.0.13.

User Interface

• Enhancements have been made to the Detailed Status panel. Locks are now displayed in a seperate pane of the display, the display can be frozen to allow rapidly changing items to be examined, and new filter capabilities have been added. This has been added in 6.0.13.

Return to top of page

---

SureSync 6.0.11 Known Issues

Version 6.0.11 was posted on May 7, 2010.

Desktop

• Machines configured via a registry setting or a group policy object to prevent the use of non-FTPS certified algorithms for cryptography would prevent SureSync's desktop from loading. The algorithm used for database encryption has been changed to be FTPS certified. If using an existing database, you will have to install SureSync on a machine which allows non-FIPS compliant algorithms and perform a Copy Database to convert the encryption. This has been fixed in 6.0.12.

Enterprise Status

• If you attempt to specify a non-default TCP listen port to connect to the remote Scheduler on in Enterprise Status an error would be generated. This has been fixed in 6.0.12.

File Synchronization

• In some circumstances, a "Failed to enable constraints" error message could occur in the queue table of the database. This has been fixed in 6.0.12.
• Synchronization jobs could generate "SqlTypeException: SqlDateTime overflow" errors which would cause the job to cancel. This has been fixed in 6.0.12.
• If a path dropped from a synchronization job during a folder scan, the job could hang. This has been fixed in 6.0.12.
• Corrections have been made to the network throttling code to enhance accuracy of the throttle. This has been fixed in 6.0.12.
• The ability to filter based on additional attributes has been added to the product. You can now filter off of the offline, symbolic link and indexed attributes. This has been added in 6.0.12.
• A new internal I/O throttle has been added to the multi-threaded engine to slow down I/O requests to a destination machine which is displaying reduced I/O subsystem performance. This has been fixed in 6.0.12.
• A new enhancement has been made to the processing of a full directory scan. When performing a scan over slow connections or when there are pending unlock requests from the SPIAgent File Locking Add-on, the monitor will process the root folder and queue scan events for each subfolder instead of processing the entire tree at once. This allows the scan to resume where it left off and process unlock requests during the scan. This has been added in 6.0.12.

Real-Time Monitors

• "Missing FileHistory" errors could occur in a Real-Time Monitor following a rename. This has been fixed in 6.0.12.

SPIAgent

• Internal corrections have been made to the SPIAgent to reduce CPU and resource usage. This has been fixed in 6.0.12.

SPIAgent File Locking

• Locks generated during an initial scan were not being released until the scan was completed. On long running scans, this could result in files being locked which were not really open anymore. This has been fixed in 6.0.12.
• In rare circumstances, a program check could occur in the Socket I/O thread of the SPIAgent that would crash the service. This has been fixed in 6.0.12.

Return to top of page

---

SureSync 6.0.10 Known Issues

Version 6.0.10 was posted on April 26, 2010.

FTP

• A 'File Not Found' error was possible when using a FTP path as the source. This has been fixed in 6.0.11.

Licensing

• An unnecessary warning message was displayed for a workstation license if the license was activated for the current workstation and no root paths had been referenced. This has been fixed in 6.0.11.

Real-Time Monitors

• In some instances, a folder rename event could be missed in a Real-Time Monitor. This has been fixed in 6.0.11.

SPIAgent

• During a full scan where security must be compared, the SPIAgent service could consume high levels of CPU time while performing the comparisons. This has been fixed in 6.0.11.

SPIAgent File Locking

• A file rename on a file that is locked with the SPIAgent File Locking Add-on could generate an ANotFound error when attempting to release the lock. This has been fixed in 6.0.11.

Please note that 6.0.11 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 if your machines are running with the file locking Add-on.

Return to top of page

---

SureSync 6.0.9 Known Issues

Version 6.0.9 was posted on March 30, 2010.

File Locking

• When using the SPIAgent File Locking Add-on on Windows 2003, file locks were not always released properly. This has been fixed in 6.0.10.

File Synchronization

• VSS Advanced Open File Support would not be used in certain circumstances due to an erorr in a check to determine if the file had changed since initial processing started. Generally, the file copy would succeed using the standard open file handling. This has been fixed in 6.0.10.
• A failure sending an e-mail alert could result in the job being canceled. This has been fixed in 6.0.10.
• "System.NullReferenceException: Object reference not set to an instance of an object" errors could occur due to a timing related error purging internal node items. This has been fixed in 6.0.10.
• InvalidCastException errors could occur when synchronizing with Novell machines. This has been fixed in 6.0.10.
• Open file processing via VSS would not be used if file being processed increased in size during the processing. The standard open file support would be used instead. This has been fixed in 6.0.10.

Installer

• When installing the SPIAgent File Locking Add-on on a Windows 2003 server, the user could encounter an "Installation Failed" pop-up and the driver would not be installed. This has been fixed in 6.0.10.
• Corrected some display errors in the SureSync setup user interface when running on a Windows 2003 machine over remote desktop. This has been fixed in 6.0.10.

Real-Time Monitors

• When replacing a file in a Multi-Mirror with a copy of the file that had an older date, the Monitor would select the file with a newer modification date on another path as the source for the copy when the older dated restored copy should have been selected. This has been fixed in 6.0.10.
• PRIMARY KEY constraint 'PK_FileActions_Rel_NodeId_FileName' errors could occur in a Real-Time Monitor which processed multiple rename events in a particular timing. This has been fixed in 6.0.10.

SPIAgent

• In some instances, the Application Event log would record a large number of "CtlSignalCaller unable to restore ReqB" messages when running with the SPIAgent Add-on. This has been fixed in 6.0.10.

User Interface

• When using the Job Log Viewer with SQL 2000, the user would receive a "System.Exception: 'Row_Number' is not a recognized function name" error. This has been fixed in 6.0.10.
• Some dates in the SureSync desktop user interface were not properly localized. This has been fixed in 6.0.10.

Please note that 6.0.10 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 if your machines are running with the file locking Add-on.

Return to top of page

---

SureSync 6.0.8 Known Issues

Version 6.0.8 was posted on March 18, 2010.

File 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.

Return to top of page

---

SureSync 6.0.7 Known Issues

Version 6.0.7 was posted on March 3, 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.

Return to top of page

---

SureSync 6.0.6 Known Issues

Version 6.0.6 was posted on February 19, 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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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

Return to top of page

---

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.

Return to top of page

---

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

Return to top of page

---

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

Return to top of page

---

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.

Return to top of page

---

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 (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.

Return to top of page

---

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 calcuations. This has been fixed in 5.0.27.

Return to top of page

---

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 intial 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 constaint 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 attepmting to communicate with it would receive a timeout error. This has been fixed in 5.0.26.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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 chould 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.

Return to top of page

---

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.

Return to top of page

---

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

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

SureSync 5.0.17 Known Issues

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

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.

Return to top of page

---

SureSync 4.1.37 Known Issues

Version 4.1.37 was posted on January 31, 2006

File Synchronization and Archiving

• If a connection was recovered too quickly after a path loss, the path may not be used. This has been fixed in 5.0.3.
• Archive paths were not being monitored for path loss and were not retried properly if the path was lost. This has been fixed in 5.0.3.
• If a multi-mirror rule had "copy folder security objects to existing folders" turned on then SureSync would copy security but it would always select the first path as the source even if permissions changed on a different path. This has been fixed in 5.0.3.
• If a rule without *.* in the File Masks was set to "copy folder security objects to existing folders" it wasn't copying security even though it should. This has been fixed in 5.0.3.

SPIAgent

• Performance improvements were made to TCP transmissions. All agents must be upgraded to benefit. This improvement can be found in 5.0.3.

Return to top of page

---

SureSync 4.1.36 Known Issues

Version 4.1.36 was posted on December 16, 2005.

Installer

• The SureSync Scheduler Start service was not removed by the installer on uninstall. This has been fixed in 4.1.37.

Real-Time Monitors

• Subfolders may not be immediately processed in a monitor if a folder is renamed. This has been fixed in 4.1.37.

Return to top of page

---

SureSync 4.1.35 Known Issues

Version 4.1.35 was posted on December 9, 2005.

File Synchronization

• If a user is running a multi-directional Relation using UNC paths, has a large number of file retry attempts configured (which is not the default setting), and encounters the error "network path not available" the job could potentially experience a problem where SureSync creates a file with incorrect values. This has been fixed in 4.1.36.

Return to top of page

---

SureSync 4.1.34 Known Issues

Version 4.1.34 was posted on November 11, 2005.

Desktop

• Invalid handle possible during the launch of the desktop which could result in the desktop failing to launch. This has been fixed in 4.1.35.
• Minor changes made to comply with Microsoft Platform Tests for ISV Solutions. These fixes are included in 4.1.35.

Return to top of page

---

SureSync 4.1.33 Known Issues

Version 4.1.33 was posted on August 25, 2005.

Desktop

• If a user changed servers on the Server Settings panel while a save was needed SureSync would ask if they wanted to save the changes, but if they selected yes the save would fail. This has been fixed in 4.1.34.

File Synchronization

• SureSync would loop retrying database error #3709. This has been fixed in 4.1.34.

Real-Time Monitors

• Root Paths could be dropped unnecessarily in rare error recovery instances. This has been fixed in 4.1.34.
• Improved error recovery on temporarily lost connections. This improvement can be found in 4.1.34.

Return to top of page

---

SureSync 4.1.32 Known Issues

Version 4.1.32 was posted on July 15, 2005.

File Synchronization

• If a stand alone Relation was run from the desktop the job log record was not being written with information to identify the Relation name in the summary. This has been fixed in 4.1.33.
• A Multi-Mirror that drops a path might add files from the lost path back to the other paths when that lost path is reconnected in a later job. This has been fixed in 4.1.33.
• Machines that have been running for months without a reboot could encounter a timer overflow in SureSync which can then cause other errors (for example, Type Mismatch). This has been fixed in 4.1.33.
• Open files may not have been processed in rare instances. These files would be processed when they were closed. This has been fixed in 4.1.33.
• SPIFiles.exe would application fault when running under Windows XP x64 edition. This has been fixed in 4.1.33.
• If "Purge log entries older than" is unchecked in Tools | Options on the Reporting tab log entries would still be purged. This has been fixed in 4.1.33.

Real-Time Monitors

• Priorities did not change if a Real-Time Monitor interval changed during the initial scan. This has been fixed in 4.1.33.
• Attempting to run a Monitor with a Rule using wildcards in the folder may generate an error. This has been fixed in 4.1.33.

Return to top of page

---

---

SureSync 4.1.31 Known Issues

Version 4.1.31 was posted on June 3, 2005.

Desktop

• If attempting to stop a monitor from the right-click popup menu or from the file menu the monitor would show as held but the job would still be running. This has been fixed in 4.1.32.

File Synchronization

• False renames could be triggered in a monitor if deletes are immediately followed by adds within the same second in the same root folder. This has been fixed in 4.1.32.
• FTP root paths could be incorrectly altered in some instances. This has been fixed in 4.1.32.

Return to top of page

---

---

SureSync 4.1.30 Known Issues

Version 4.1.30 was posted on May 23, 2005.

Alerts

• Alerts were not being sent at the end of a job when requested. This has been fixed in 4.1.31.

File Synchronization

• It was possible for file history not found errors to occur. This has been fixed in 4.1.31.
• FTP could sometimes report a folder already exists error or the root path folder could be duplicated internally causing a path not found error. This has been fixed in 4.1.31.

Return to top of page

---

SureSync 4.1.29 Known Issues

Version 4.1.29 was posted on April 14, 2005.

Advanced Open File Support

• Incorrect function errors occurred on Windows 2003 SP1 machines using Advanced Open File Support. This has been fixed in 4.1.30.

File Synchronization

• Force Archive attribute on/off without copying files did not perform any action. This has been fixed in 4.1.30.
• It was possible for errors to occur in determining if a root path exists. This has been fixed in 4.1.30.
• When running a VBScript with a space in the path from a Schedule the script would fail to execute. This has been fixed in 4.1.30.
• When copying mount points the mount point link was copied instead of the contents of the mount point. This has been fixed in 4.1.30.
• With some FTP servers it was possible for part of the FTP root path to be duplicated and appended to the existing root path. This has been fixed in 4.1.30.

Real-Time Monitors

• File and folder moves within a monitor resulted in copying instead of renaming. This has been fixed in 4.1.30.

SPIAgent

• If remote agent communication link was broken it was possible for the local agent session to hang. This has been fixed in 4.1.30.

Return to top of page

---

SureSync 4.1.28 Known Issues

Version 4.1.28 was posted on March 18, 2005.

Real-Time Monitors

• Real-Time Monitors would retry short file name conflicts endlessly. Now an error is logged. This has been fixed in 4.1.29.
• Statistics records are now written between all monitor intervals. This change has been made in 4.1.29.

SPIAgent

• Get FileSizeEx errors on Windows NT 4.0 which would prevent the SPIAgent service from starting on NT4 machines. This has been fixed in 4.1.29.

Return to top of page

---

SureSync 4.1.27 Known Issues

Version 4.1.27 was posted on January 12, 2005.

File Synchronization

• Wrap traces now generate trace logs for errors classified as "warning" or higher. This change has been made in 4.1.28.
• Importing paths into a relation with the replace option on was not replacing the old paths. This has been fixed in 4.1.28.
• Importing paths into a relation made them appear in the display but they would not be active when the job was run. This has been fixed in 4.1.28.
• If a path in a Relation had the option "create root folder if it doesn't exist" turned on then when the job was run it would create the folder but stop saying it doesn't exist. This has been fixed in 4.1.28.

Real-Time Monitors

• In real-time monitors change events may have been dropped. This has been fixed in 4.1.28.
• Alerts were not sent for a monitor when an agent went down until after the agent recovered. This has been fixed in 4.1.28.

SPIAgent

• Improvements in delta performance have been made, especially with larger files. This change has been made in 4.1.28.

Return to top of page

---

SureSync 4.1.26 Known Issues

Version 4.1.26 was posted on November 24, 2004.

Real-Time Monitors

• In some situations it was possible for the application to fail to retry the copy of an open source file in a real-time monitor. This has been fixed in 4.1.27.

SPIAgent

• The SPIAgent now resets its error counter every 4 hours instead of maintaining the counter for the lifetime of the job. This prevents agents from being stopped inappropriately in some situations due to "too many errors". This has been fixed in 4.1.27.
• Files were sometimes being retransmitted unnecessarily when delta processing was being used. This has been fixed in 4.1.27.

Return to top of page

---

SureSync 4.1.25 Known Issues

Version 4.1.25 was posted on November 4, 2004.

Database

• It was possible for a loop to occur when a SQL SureSync database becomes unavailable during a file copy. This has been fixed in 4.1.26.

Desktop

• The Priorities options panel will now accept European time formats for the minimum delay before copying files field. This has been fixed in 4.1.26.

File Synchronization

• It was possible for the hidden attribute on the folder to be lost when folder security is copied. This has been fixed in 4.1.26.
• If the Advanced Open File Support option is turned on for a rule while you are using a trial license you would not be able to turn it off after switching licenses. This has been fixed in 4.1.26.
• The maximum number of errors recorded before a job is automatically stopped has become a daily counter rather than over the life of a job. This change has been made in 4.1.26.
• A "parameter is incorrect" error could occur when attempting to copy security in unusual cases. This has been fixed in 4.1.26.
• Overflow errors could occur when a file copy was aborted after 2GB or more of the file was trasfered. This has been fixed in 4.1.26.

Real-Time Monitors

• If running multiple Relations in a monitor with different drive paths for each Relation an "folder to be monitored does not exist" error could occur. This has been fixed in 4.1.26.
• Real-Time Monitors could loop on folder events (a change being detected for a folder). This has been fixed in 4.1.26.

Return to top of page

---

SureSync 4.1.24 Known Issues

Version 4.1.24 was posted on October 25, 2004.

Desktop

• If a drive or share only was selected as a root path (no directory after it in the path specification) then the user interface would report it as not existing. This has been fixed in 4.1.25.
• If you attempted to copy the same Schedule or Real-Time Monitor more than once you would receive an error and the copy would fail. This has been fixed in 4.1.25.

File Synchronization

• If you have an invalid or missing path when you start a Relation with a move rule, SureSync would delete the source files as if it had synchronized the missing path correctly. This has been fixed in 4.1.25.

Real-Time Monitors

• When attempting to recover a dropped path it was possible for a loop to occur on "Monitoring of path successfully restored". This has been fixed in 4.1.25.

Return to top of page

---

SureSync Version 4.1.23 Known Issues

Version 4.1.23 was posted on August 24, 2004.

Alerts

• Alert e-mail subject lines now include the job name. This enhancement has been made in 4.1.24.
• Changing the SMTP profile name in the Alerts Configuration would not change the profile name the alert user was using. This has been fixed in 4.1.24.

Database

• Type mismatch errors could occurring during upgrading a database (on job log entries). This has been fixed in 4.1.24.
• When copying a Relation the priority settings were not being copied. Now they will be copied if the Relation is copied in the same database. This has been fixed in 4.1.24.

File Synchronization

• A synchronization would be canceled if an error occurred when setting the QoS settings for the job. This has been fixed in 4.1.24.
• If running with only Backup and Restore privileges the SureSync user still needed file permissions. This has been fixed in 4.1.24.
• FTP files could not be found if an "invisible" root directory was used. This has been fixed in 4.1.24.
• VSS open file copies (Windows 2003) caused high virtual memory usage in the SPIAgent. This has been fixed in 4.1.24.
• If the database has many jobs referencing many servers it was possible to encounter an overflow error. This has been fixed in 4.1.24.
• Overflow errors could occur in SPIFiles.exe when previewing. This has been fixed in 4.1.24.
• Changes to path validation routines. This improvement can be found in 4.1.24.

Real-Time Monitors

• If a monitor loses a path and the end of an interval happens while we are re-trying the path the monitor would not recognize the end of the interval. This has been fixed in 4.1.24.

SPIAgent

• The SPIAgent Configuration Utility could give overflow errors on machines with high uptime. This has been fixed in 4.1.24.

Return to top of page

---

SureSync Version 4.1.22 Known Issues

Version 4.1.22 was posted on June 9, 2004.

Alerts

• In some cases pressing the Alert Users button on the Alerts option panel would fail to launch the Alert configuration tool. This has been fixed in 4.1.23.
• "Alert Users" buttons on Schedules and Real-Time Monitor property sheets did not always successfully launch the Alert configuration tool. This has been fixed in 4.1.23.

Archive

• If running an archive in real-time and archive corruption is being automatically repaired you may see an "object variable or with block variable not set" or a "subscript out of range" error. The monitor was then stopped and placed on hold. This has been fixed in 4.1.23.
• Restoring files from an archive in a preview would produce an error and not allow the restore. This has been fixed in 4.1.23.
• Attempting to add or edit archive rules produced an "cannot find the input table or query" error. This has been fixed in 4.1.23.

Desktop

• In the copy database dialog it was not possible to type in paths which included a space. This has been fixed in 4.1.23.
• The job log entries for a stand alone Relation (not run by a Schedule or Real-Time Monitor) would not display the Relation name in the drop down list. This has been fixed in 4.1.23.

File Synchronization

• When running under Japanese Windows jobs would crash during termination of the job. This has been fixed in 4.1.23.
• An optimization has been made to the security copy process. When SureSync copies security it copies the status of the inherit flag and any explicitly set permissions. In previous versions it would then compare all of the security on the file which can be different if the inherited permissions are different on the root paths. This would result in SureSync copying security repeatedly when it was not needed. To resolve the problem SureSync now does not compare inherited permissions; only explicitly set permissions. This improvement has been included in 4.1.23.
• The relation options to warn/cancel the job if there were a specified number of deletes were not working. This has been fixed in 4.1.23.
• VSS is now supported on Windows 2003 machines allowing the copying of locked open files without the need for an Advanced Open File Support license. The AOFS driver and licenses are needed for locked open file copies on Windows 2000 and Windows XP. This improvement has been included in 4.1.23.

Real-Time Monitors

• Real-Time Monitors could report an extraneous error "unable to signal current scan position to agent". This has been fixed in 4.1.23.
• If a path was dropped from a real-time monitor and then returned to the network while the monitor was between intervals the path may not get properly restored. This has been fixed in 4.1.23.
• Record is deleted errors would sometimes occur when multiple monitors are running at midnight. This has been fixed in 4.1.23.

Return to top of page

---

SureSync Version 4.1.21 Known Issues

Version 4.1.21 was posted on May 11, 2004.

New Feature

• Advanced Open File Support. This new feature is available in 4.1.22.

Alerts

• Alert configuration did not launch from the Tools menu (file not found). This has been fixed in 4.1.22.
• Alert configuration did not launch from the Alerts tab in Tools | Options. This has been fixed in 4.1.22.
• Alerts at the end of a schedule were not being sent. This has been fixed in 4.1.22.

Archive

• It was possible to receive "object variable or with block variable not set" errors when creating a new archive rule. This has been fixed in 4.1.22

Database

• It is now possible to create SQL databases with a hyphen in the name. This has been fixed in 4.1.22.
• Concurrency errors on Jet databases were not retried in some cases. This has been fixed in 4.1.22.
• Lock files and databases for SureSync and ArchiveSync can now be stored in the same folder. This change was made in 4.1.22.
• There were problems creating non-English SQL server databases. This has been fixed in 4.1.22.
• It was possible to receive timeouts when copying very large databases. This has been fixed in 4.1.22.
• Performance of SQL server databases has been improved. This improvement can be found in 4.1.22.

Desktop

• Improvements have been made to the desktop refreshes. These improvements can be found in 4.1.22.
• It was possible to receive "object variable or with block variable not set" errors when pressing the cancel button on a progress panel. This has been fixed in 4.1.22.
• SPIDcom.exe produced an error attempting to get DCOM information (could not find SPISecur.dll). This has been fixed in 4.1.22.

File Synchronization

• Unable to preview in Windows 2003. This has been fixed in 4.1.22.
• Obsolete file history was not being purged from the database properly. This has been fixed in 4.1.22.
• Unable to change an existing rule to a compare rule. This has been fixed in 4.1.22.

Real-Time

• If you are running multiple monitors at once, you may get "record is deleted" errors at midnight. This has been fixed in 4.1.22.
• With real-time monitors it was possible to receive "subscript out of range" errors on lost connections which occurred between intervals. This has been fixed in 4.1.22.
• It was possible to receive "object variable or with block variable not set" errors when reconnecting to a path during a real-time monitor. This has been fixed in 4.1.22.

Return to top of page

---

SureSync Version 4.1.20 Known Issues

Version 4.1.20 was posted on March 22, 2004.

Database

• With a SQL database duplicate keys on NodeID.FileName on monitor events were possible. This has been fixed in 4.1.21.

File Synchronization

• Running a Relation or job from a remote client may say that the Relation is already busy. This has been fixed in 4.1.21.
• If running a multi-mirror rule and a file copy was attempted to a disk without enough free space and the file already exists on that destination (not an add) then the file could be deleted. If this happened and was not corrected manually before the next run of the job then all other copies would be deleted. This has been fixed in 4.1.21.

Installer

• The default install locations have been changed with this release. On new installations SureSync is installed to C:\Program Files\Software Pursuits\SureSync. The SPIAgent components are installed to C:\Program Files\Software Pursuits\SPIAgent and there is a new location in Common Files for shared components at C:\Program Files\Common Files\Software Pursuits. If you're installing 4.1.21 as an upgrade to an older version your current SureSync install location will not change but the SPIAgent and Common Files locations will be created. This change was made in 4.1.21.

Real-Time

• In real-time monitors dropped paths were not always retried in a timely manner. This has been fixed in 4.1.21.
• Real-time monitors may report subscript out of range or variable not set error messages. This has been fixed in 4.1.21.

SPIAgent

• Wrap trace functionality has been added to the SPIAgent. This diagnostic improvement was made in 4.1.21.

Return to top of page

---

SureSync Version 4.1.19 Known Issues

Version 4.1.19 was posted on January 16, 2004.

Database

• Log files were not being purged from the database if your database contained only real-time monitors. This resulted in some database growth. This has been fixed in 4.1.20
• Lock files location and license table are now handled on a database copy. This has been fixed in 4.1.20.

Desktop

• Browsing rule subfolder(s) when two root paths are the same but using different SPIAgents would work but would product an error. This has been fixed in 4.1.20.
• In some instances deleting a path that explicitly specifies an agent may cause that agent server to be unmarked as an agent in Server Settings. This has been fixed in 4.1.20.

File Synchronization

• Object variable or with block variable not set when unable to connect to an agent during the start of the job. This has been fixed in 4.1.20.
• QOS values specified in a Priority were being ignored. QOS settings have been removed from the SPIAgent Configuration Utility. They should now be specified in Options | Priorities. This has been fixed in 4.1.20.

Real-Time Monitors

• In some instances real-time monitors could enter into a timer loop on path retry. This has been fixed in 4.1.20.
• An optimization was made to suppress subfolder events if we are processing the entire folder tree in real-time. This enhancement has been made in 4.1.20.

SPIAgent

• SureSync would fail to reconnect to agents in some cases. This has been fixed in 4.1.20.
• Remote agent threads could crash in some instances. This has been fixed in 4.1.20.

Return to top of page

---

SureSync Version 4.1.18 Known Issues

Version 4.1.18 was posted on December 3, 2003.

ArchiveSync

• ArchiveSync restores skipped restoring of files if the folders on the destination did not exist. This has been fixed in 4.1.19.
• Cache sequence errors could occur in ArchiveSync jobs. This has been fixed in 4.1.19.

Desktop

• Performing a copy/paste of a relation and then altering the root paths can cause SureSync to incorrectly identify servers associates with the paths. This has been fixed in 4.1.19.

Real-Time Monitors

• If a path was not available on startup of a real-time monitor an object variable not set error message would occur and cause the job to go to held status. This has been fixed in 4.1.19.
• Changes in monitor interval would interrupt a full folder scan causing the folder scan to start over. This has been fixed in 4.1.19.

SPIAgent

• The SPIAgent default port ranges have changed to 8002-8033 (TCP) and 8034-8065 (Multicast). This change allows for more jobs to run at once by default. If you have changed your port range using the SPIAgent Configuration Utility you will need to change these manually if you want to use the new range. All others will be updated automatically.
• Chain corruption could occur in the SPIAgent due to timing errors which would cause the job to crash. This has been fixed in 4.1.19.

Return to top of page

---

SureSync Version 4.1.17 Known Issues

Version 4.1.17 was posted on October 22, 2003.

Database

• Database tries to open and get error "SQL Error = 3050" and was not being retried. This has been fixed in 4.1.18.
• Database copy did not work when commas were the default decimal separator (most European languages). This has been fixed in 4.1.18.

Real Time Monitor

• Monitor may report that an SPIAgent is not running on a path when an SPIAgent was actually specified and running. This has been fixed in 4.1.18.

SPIAgent

• Windows 2000 patch caused SPIAgent logons to be rejected if the Agent account was different than the user's account. Solution: place the SureSync UserID in the Local Security Policy > Act as part of the operating system.
• If the monitor stops with the error "The path is not being monitored by an agent on the same machine..." a secondary error occurs "Object variable or with object variable not set". This has been fixed in 4.1.18.
• Multiple agent monitor might associate dropped SPIAgent with the wrong server. This has been fixed in 4.1.18.

Return to top of page

---

SureSync Version 4.1.16 Known Issues

Version 4.1.16 was posted on October 2, 2003.

Desktop

• Corrected a script problem that would not allow SureSync to install because the MDAC version was incorrect.

Database

• Unable to Create or copy a SQL database. This has been fixed in 4.1.17.

Return to top of page

---

SureSync Version 4.1.15 Known Issues

Version 4.1.15 was posted on July 24, 2003.

ArchiveSync

• Files with invalid created dates could cause "error thinning archive" messages when using ArchiveSync. Now files with invalid created dates are forced to the current date and time. This has been fixed in 4.1.16.

Database

• SQL Server objects might have incorrect ownership values. This has been fixed in 4.1.16.
• Concurrency errors with SQL Server. This has been fixed in 4.1.16

Desktop

• Desktop refresh times improved and multiple requests for refresh handled more efficiently. These improvements can be found in 4.1.16.

File Synchronization

• Errors when copying FTP to FTP without any non-FTP access. This has been fixed in 4.1.16.
• RAS was not being fully initialized before connecting to a remote agent. This has been fixed in 4.1.16.

Real-Time Monitors

• Agent may fail to immediately recognize that a monitor path has been lost. This has been fixed in 4.1.16.
• Missing agent logon errors when reconnecting to dropped monitor path. This has been fixed in 4.1.16.
• Some Real-Time agent errors were not recognized in a timely manner. This has been fixed in 4.1.16.
• Monitor hangs saying 'Purge obsolete Job Logs'. This has been fixed in 4.1.16.

Scheduler

• If a scheduler is set to run at log in and is not shut off before user logged off last SureSync will generate an error 'Scheduler is already running via DCOM' at next logon (even though it isn't). This has been fixed in 4.1.16.

SPIAgent

• Path names greater than 255 characters may cause errors when using the SPIAgent. This has been fixed in 4.1.16.
• Deltas suppressed on non-local drives. This has been fixed in 4.1.16.

Return to top of page

---

SureSync Version 4.1.14 Known Issues

Version 4.1.14 was posted on June 13, 2003.

Alerts

• Alerts fail with "Failure to open database" in the Event Viewer. This has been fixed in 4.1.15.

Database

• Could not update, currently locked errors when running multiple jobs. This has been fixed in 4.1.15.
• Attempting to open a SQL database using a data source fails. This has been fixed in 4.1.15.
• New databases were upgraded on opening SureSync for the first time. Database dialogs were omitted on certain errors. This has been fixed in 4.1.15.

Desktop

• Copying a relation multiple times would fail due to SureSync not naming each copy differently. This has been fixed in 4.1.15.
• New error messages when desktop cannot communicate with scheduler.
• Overflow error in certain cases when clicking on a relation used only in a Real Time Monitor. This has been fixed in 4.1.15.

File Synchronization

• Alternate data streams not supported error after reconnect with monitor. This has been fixed in 4.1.15.
• UDF file systems for DVDs write incorrect dates. We correct the date when reading UDF systems. This has been fixed in 4.1.15.
• Running a VBS script on the scripts tab would fail with an Invalid Procedure Call error. This has been fixed in 4.1.15.
• In some cases when a file copy is aborted temp files are not cleaned up. This has been fixed in 4.1.15.

Real-Time Monitors

• SureSync failed to warn user if agent is not used in the monitor. This has been fixed in 4.1.15.
• When running a monitor with multiple relations and agents occasionally if a path becomes invalid the wrong path in the monitor was disabled. This has been fixed in 4.1.15.
• Attempting to monitor a drive letter instead of a share would result in a 'could not monitor folder' error message. This has been fixed in 4.1.15.
• Monitors could cancel when compressed file transmission fails with a communications error. This has been fixed in 4.1.15.

Scheduler

• Scheduler terminates after 3 failures to open database even if they do not occur in a row. This has been fixed in 4.1.15 and now stops only after 3 errors in a row.

SPIAgent

• Improved delta performance.
• Delta blocks are now compressed with compression is enabled.
• Communication with local agent could be losted when a remote connection dropped. This has been fixed in 4.1.15.

Return to top of page

---

SureSync Version 4.1.13 Known Issues

Version 4.1.13 was posted on May 21, 2003.

Database

• Database updated to improve performance and security.
• MDAC 2.7 and Jet 4.0 SP6 or newer is now required.
• Optimistic Concurrency Check occurred with synchronization monitor intervals. This has been fixed in 4.1.14.
• Record already exists errors could occur for an ArchiveSync real-time monitor with history. This has been fixed in 4.1.14.

Desktop

• (Pause) repeats on Progress Panel title bar when cancel button is used with DCOM. This has been fixed in 4.1.14 so (Pause) is only displayed once.
• Override subfolder in Preview and a file in that folder does not exist in the new source folder SureSync give "This array is fixed or temporarily locked" error. This has been fixed in 4.1.14.

File Synchronization

• Failed to recognize stream support on NT4.0 systems. This has been fixed in 4.1.14.

Real-Time Monitors

• Monitors can handle longer paths.
• Monitors running relations using the "do not copy if top level folder does not exist" option were copying files even if the top level folder did not exist. This has been fixed in 4.1.14.
• Monitors which contain multiple relations (with different number of paths) could give a "Subscript out of range" error and end the job. This has been fixed in 4.1.14.

Return to top of page

---

SureSync Version 4.1.12 Known Issues

Version 4.1.12 was posted on April 8, 2003.

ArchiveSync

• Obsolete archive folders were being deleted. This has been fixed in 4.1.13.

Desktop

• Progress panel, when run from a preview, was mis-sized. This has been fixed in 4.1.13.
• Checking the box to put a monitor on hold and saying no when it asks if you would like to stop processing let the job continue but incorrectly changed status to on hold. Now keeps busy status.
• If you closed the import/export path form with the 'X' in the corner an error would be generated. This has been fixed in 4.1.13.
• Clicking on the desktop tree immediately after the preview (before it finishes refreshing) causes an error. This has been fixed in 4.1.13.
• When copying a relation if Agents are not available, nodes, action and history tables were not created. This caused errors when attempting to run the Relation. This has been fixed in 4.1.13.
• The job log would not display from the (non-DCOM) scheduler. This has been fixed in 4.1.13.
• When running a job from preview and using a SQL database the progress panel would display but no files would copy. This has been fixed in 4.1.13.

File Synchronization

• If the "resolve multiple updates by copying the latest" checkbox was not checked the proper warning was always issued but the file with the latest date would overwrite anyway. This has been fixed in 4.1.13.
• "Failed to write all bytes" error could occur on files with alternate named data streams. This has been fixed in 4.1.13.

Real-Time Monitors

• Reduced memory usage when monitoring large folders and fixed memory leaks.
• May fail to retry lost path in monitor. This has been fixed in 4.1.13.
• Paths lost in the middle of copying a file had errors trying to recover. This has been fixed in 4.1.13.

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

Return to top of page

---

SureSync Version 4.1.11 Known Issues

Version 4.1.11 was posted on March 6, 2003.

Database

• SQL Error on FileHistory on non-USA locales. This has been fixed in 4.1.12.
• Error writing statistics outside of the USA. This has been fixed in 4.1.12.

Desktop

• Progress Panel not displaying automatically. This has been fixed in 4.1.12.
• Display error on the security tab of the rule. This has been fixed in 4.1.12.
• If database paths contain a single Quote mark, the job log will not open the property and alert configuration utility. This has been fixed in 4.1.12.
• When deleting a path that will cause a rule to be deleted we will ask before processing the delete.
• If you deleted a root path which referenced an Agent the server would no longer be marked as an agent in Server Settings even though it is still used as an agent on other paths. This has been fixed in 4.1.12.
• Import and export of path lists feature has been added to the current version.

File Synchronization

• Improvements have been made to the scan performance and processing of large directory trees.
• Errors while copying EFS (encrypted) files. This has been fixed in 4.1.12.
• FTP may cause an error if "," is imbedded in the directory list. This has been fixed in 4.1.12.
• "Object variable not set" error on file copy retries. This has been fixed in 4.1.12.
• Folder security values did not display properly after being copied. This has been fixed in 4.1.12.
• SureSync could not rename destination files on Maxtor NAS devices. This has been fixed in 4.1.12.

Licensing

• Local server path move may cause a license error. This has been fixed in 4.1.12.

Real-Time Monitors

• Performance improvement with large monitor queue.
• Real-Time Monitor issues a "subscript out of range" error when new monitor intervals are started. This has been fixed in 4.1.12.
• Errors copying permissions on reconnected monitor path. This has been fixed in 4.1.12.
• Folder security values may not be set correctly. This could cause a loop in the Real-Time monitor. This has been fixed in 4.1.12.

SPIAgent

• Errors if the user tries to use non-default port numbers. This has been fixed in 4.1.12.
• "Not enough storage" error occurs on the write file for deltas. This has been fixed in 4.1.12.
• Delta block sequence error possible with multiple destinations. Each path being different. This has been fixed in 4.1.12.
• Unable to locate session by index and fails to retry path. This has been fixed in 4.1.12.

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

Return to top of page

---

SureSync Version 4.1.10 Known Issues

Version 4.1.10 was posted on February 25, 2003.

File Synchronization

• FTP error recovery fails to set folder causing a folder not found message. This has been fixed in 4.1.11.

Licensing

• Get Server Info may fail on stand-a-lone workstations causing a license error. This has been fixed in 4.1.11.

Real-Time Monitors

• RealTime Monitor loops if path retry occurs while processing a file or folder. This has been fixed in 4.1.11.
• When a RealTime multi-directional synchronization encounters a file that includes any special characters in the file name, it will error out with the error: "Cannot insert duplicate key row" "The statement has been terminated". This error repeats until the job cancels. This has been fixed in 4.1.11.
• Monitor with date range rules may skip files until job restarts. This has been fixed in 4.1.11.

SPIAgent

• Improved delta performance.
• "Incorrect Function - SetFilePointer" message on delta processing when copying security. This has been fixed in 4.1.11.

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

Return to top of page

---

SureSync Version 4.1.9 Known Issues

Version 4.1.9 was posted on February 7, 2003.

Database

• Fixed inability to convert SQL to JET if user altered data paths.
• SQL performance improvements.

Desktop

• Cosmetic changes to interface were made.

File Synchronization

• File history for deleted files was not immediately deleted for non-real-time jobs, so if a file with the same name was added back before the next run SureSync would delete the file. This was fixed in 4.1.10.

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

Return to top of page

---

SureSync Version 4.1.8 Known Issues

Version 4.1.8 was posted on January 21, 2003.

Database

• Optimistic concurrency check with SQL Server failing. This has been fixed in 4.1.9.

Desktop

• Always get trace level logging no matter what was requested. This has been fixed in 4.1.9.
• Interval statistics now logged.

Real-Time Monitors

• Multi-mirror monitor might fail to copy added file. This has been fixed in 4.1.9.
• Loop on Archive thinning for Monitor when only thinning is needed. This has been fixed in 4.1.9.

SPIAgent

• SPIAgent crashes randomly. This has been fixed in 4.1.9.

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

Return to top of page

---

SureSync Version 4.1.7 Known Issues

Version 4.1.7 was posted on December 13, 2002.

Database

• SQL server timeout errors. Errors on rename only and only on monitors.
• SQL Server could not find the lock path with instance name causing errors.
• Enhanced statistics table.
• Unexpected history found when using a SQL server database when root path is deleted.
• SQL duplicate key errors.

Desktop

• Cosmetic changes to desktop.
• Error in Copy/paste function in Relations when using SQL database.
• Browse error occurs on Rule subdirectory.
• When using the Restore file version override on Preview, the incorrect action was displayed

File Synchronization

• If the path is not found in a schedule, reporting additional "Object variable with Block variable not set" error.
• If a file mask does not end in an asterisk and the mask does not contain a period, an implied period is assumed at the end of the mask and only files or folders with no file extension are selected. If the mask ends with an asterisk (*), no implied period is assumed and files with and without extensions would be selected. To use an ending asterisk and still only select only files without file extensions, add a period after the asterisk. This behavior differs from prior releases of SureSync, which always added the implied period, even after an asterisk. With the change, syntax processing is more accurate, allowing a file mask of just “*” to select all files, with and without extensions.
• FTP error. Parameter is incorrect on Set time.
• Improved Archive retention periods.

Real-Time Monitors

• BOF or EOF true error when renaming a folder during a Real Time Monitor.
• Unable to monitor files on Win98.

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

Return to top of page

---

SureSync Version 4.1.6 Known Issues

Version 4.1.6 was posted on November 22, 2002.

Database

• When using SQL databases, and open the desktop on a different machine, busy status was getting reset.
• SQL Server runs too slow and may have timeout errors.

Desktop

• Preview was displaying folder icons incorrectly.
• Copy/Paste of Relations from Jet to SQL was failing with no errors.

File Synchronization

• Move rule is deleting source files even if copy fails, due to the Open Files Option.
• Compare method now treats all paths equally - there is no source.
• Archive thinning error causes overscan on archive and possible sequence error in archive.
• Multi-mirror needs to select proper source path on security changes.

SPIAgent

• Improved agent error recovery.
• Lost connection to local agent.
• "SPIAgent request when already busy" fixed.

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

Return to top of page

---

SureSync Version 4.1.5 Known Issues

Version 4.1.5 was posted on November 20, 2002.

File Synchronization

• Added a Compare function.
• "Cache sequence error" when archiving Excel files. This has been fixed for version 4.1.6.

SPIAgent

• Agent hangs on copy to remote agents. This has been fixed for version 4.1.6.

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

Return to top of page

---

SureSync Version 4.1.4 Known Issues

Version 4.1.4 was posted on November 15, 2002.

File Synchronization

• It was discovered in SPI testing that there is a minor chance that data was not being written correctly to the destination when Deltas are being used. The last block in the file was truncated and therefore not written. This causes the file to be corrupted. This has been fixed for version 4.1.5.

Return to top of page

---

SureSync Version 4.1.3 Known Issues

Version 4.1.3 was posted on October 31, 2002.

File Synchronization

• Jobs may not be cancelled immediately if connection to SPIAgent is lost. This has been fixed for version 4.1.4.
• Jobs may read security values when not requested to causing errors of locked permissions. This has been fixed for version 4.1.4.
• Subscript out of range error if only a delete rule is in the job. This has been fixed for version 4.1.4.
• Delta sequence error encountered if multiple paths, each with different older versions. This has been fixed for version 4.1.4.
• Encrypted files do not get correct dates in archive. This has been fixed for version 4.1.4.
• Preserving security on replaced files does not always work properly. This has been fixed for version 4.1.4.

Options Panel

• Add/Change priority definition or FTP Profiles, when running with SQL database, causes an error. This has been fixed for version 4.1.4.

Archive

• Archive orphan file errors. This has been fixed for version 4.1.4.

Monitors

• Multi-relation monitors sometimes errors on internal changes. This has been fixed for version 4.1.4.

Return to top of page

---

SureSync Version 4.0.22 Known Issues

Version 4.0.22 was posted on September 19, 2002.

Monitor

• In the previous version, a monitored path would not be scanned when the job started. This has been fixed for version 4.1.3.
• Some people experienced an EOF/BOF error on monitor empty folder. This has been fixed for version 4.1.3.
• If a server is specified in the Monitor option, instead of the default, to "process monitor from scheduler on" the monitor would not start and go into a "waiting to start mode". This has been fixed for version 4.1.3.
• Additional work has been done in version 4.1.3 in order to recover Monitor paths that have dropped and then restored.

Scheduler

• If there is database corruption or some other reason that the Scheduler can suddenly no longer access the SureSync database, in version 4.1.3 the Scheduler will shut down after three(3) retries instead of infinitely retrying. This will hopefully minimize any problems with the Jet engine throwing COM+ errors.

File Synchronization

• Schedules with multiple relations may not be able to copy security after the first relation. This has been fixed for version 4.1.3.
• Negative bytes copied reported on Progress form has been corrected for 4.1.3.
• Windows 98 string comparison problem on special characters (trademark, copyright, etc.) has been corrected for 4.1.3.

Preview

• Security compared before copying and security changes can be previewed.

Return to top of page

---

SureSync Version 4.0.21 Known Issues

Version 4.0.21 was posted on August 26, 2002.

Monitor

• Sometimes when a Monitor attempted to open a file for copying SureSync would report "cannot locate object pointer" errors. This has been resolved in 4.0.22.
• On the Monitor interval there is a filter to exclude files by file size, this filter would not always function. This has been fixed in 4.0.22.
• Some people were experiencing "excessive time accessing database" on monitors that had been running for a while. This issue is no longer a problem in 4.0.22.

Desktop

• Occasionally when you stop a monitor from the SureSync desktop interface, SureSync will produce a "Cannot Update Row" error. This has been fixed for version 4.0.22.
• The busy/standard icons on the SureSync desktop were not properly refreshing at times. This has been resolved in 4.0.22.
• On the general tab of Rule properties, if you clicked the browse button for the Rule Subfolder path when there was a path besides \ in the box, the desktop would crash. This has been fixed in 4.0.22.

Agent

• Version 4.0.22 has improved recovery from WSAENOBUFS errors.

File Synchronization

• If SureSync was copying to a file that was open on the destination and Delta copying was in use, the job would error out and cancel. Monitors will properly handle this situation in 4.0.22.
• When running SureSync in Windows 98/ME there were some cases where unusual characters in the file name (such as the trademark symbol) caused SureSync to produce an Invalid Procedure Call and skip the file. This has been fixed for 4.0.22.

Return to top of page

---

SureSync Version 4.0.20 Known Issues

Version 4.0.20 was posted on July 25, 2002.

Licensing

• When checking for licenses SureSync was erroneously classifying Windows 98/ME machines as servers. This was making it impossible for a workstation only license to operate on those machines. This problem has be fixed for 4.0.21.
• When creating a Relation on one machine and running it on another with a workstation license, SureSync would say you needed a path on the local machine even when you had one. This has been resolved in 4.0.21.

File Synchronization

• If there was a monitor running for an extended amount of time with a lot of activity SureSync would start reporting "Excessive time accessing database" errors and the file synchronization engine would sometimes be sent into a loop. This is fixed in SureSync 4.0.21.

Database

• When SureSync needed to keep track of file history for a synchronization it was occasionally producing database errors saying there was a missing add or edit command. This is no longer a problem in 4.0.21.
• If you compact the database with the Scheduler running there are times when the Scheduler does not shut down completely before the compact and that results in a error when attempting to restart the Scheduler after the compact. This issue has been resolved in 4.0.21.
• When a Monitor is stopped by clicking the checkbox on the property sheet that says 'Stop the monitor and place it on hold' then the database gets into a locked state and when another Schedule attempts to reschedule you will get a cannot update error because the table or database is locked. This is fixed for 4.0.21.

Desktop/User Interface

• If you tried to add a path on a machine with several Dial-up/Network Connections there were times you would receive a "subscript out of range" error or the main desktop SureSync interface would crash. This has been fixed for 4.0.21.

SPIAgent

• By default in 4.0.21 the SPIAgent service will run in silent (non-multicast) mode to help limit traffic noise.
• In 4.0.21 you can specify IP Addresses for agent communication from the Agent Configuration utility.

Preview

• Making an Override in Preview could cause a 'Subscript Out of Range' error. This has been fixed in 4.0.21.

Return to top of page

---

SureSync Version 4.0.19 Known Issues

Version 4.0.19 was posted on June 13, 2002.

Desktop/User Interface

• There was a problem copying a Relation when the agent was not accessible. This has been fixed in 4.0.20.
• In previous versions of 4.0 there was problems copying a Relation after changing databases. This has been fixed in 4.0.20.
• In 4.0.20, the Copy Database option now renames the new database to the original database name and the original database gets renamed to a file with a .bak extension.

Real-Time Monitors

• If you were running a Monitor that encountered a file that it could not replace because it was locked since it was in use then the monitor would continually re-queue that file to be copied and enter a loop until the file was closed and the lock released. This has been resolved in 4.0.20.
• Sometimes there were occasions during a monitor when the agent reported time-out errors. These have been fixed for 4.0.20.

Scheduling

• If a job tries to reschedule and encounters a database error it would start a loop of trying to reschedule. This has been fixed for 4.0.20.
• If there was an error or delay in updating a Schedule record to mark it busy, the job could be started twice at the same time which would cause collisions as they both tried to run. This is no longer a problem in 4.0.20.

Logging

• If you set the logging level on the Tools | Options panel to less than "Summary and All Errors" then SureSync would no longer log the Job Started line. Without that line there was no way to select and view individual jobs in the job log. In 4.0.20 you will be able to select individual jobs no matter what your reporting level is set to.

SPIAgent

• If a connection to an agent was lost, SureSync was sometimes having difficulty recovering the connection when it was available again. Recovery has been improved in 4.0.20.

Database

• Unnecessary table locked errors were occurring. These have been resolved in 4.0.20.

There have been numerous internal and cosmetic changes.

Return to top of page

---

SureSync Version 4.0.18 Known Issues

Version 4.0.18 was posted on May 16, 2002.

File Synchronization:

• In 4.0.19, we have improved performance when copying using deltas.
• For some multiple stream files of certain types SureSync would produce an error that said "Not all bytes copied". This has been fixed in 4.0.19.
• When scanning a single folder (no subfolders) with over approx. 10,000 files and no changes, SureSync would out run its transaction limit and produce an error, "File sharing lock count exceeded". This has be fixed for 4.0.19.
• When root paths were beening specified using drive letters instead of UNC paths, SureSync was experiencing a problem copying security. This has been resolved in 4.0.19.

SPIAgent:

• If you're using a remote agent to access a path on a machine not running SureSync or SPIAgent, then SureSync may report that path as unlicensed for the Agent, even though there are enough Agent licenses. This has be resolved in 4.0.19.
• SureSync was producing unneeded multicast messages. This was not affecting the scanning or copying of files, but it did cause extra network traffic. In version 4.0.19, the unnecessary broadcasts have been stopped.

Monitor:

• In version 4.0.19, more work has been done on recovering a Monitor when SureSync loses a connection to an Agent.

Communications:

• When SureSync encountered a NIC running using more than 16 IP addresses it developed some communication issues. In 4.0.19 communication should go through no matter how many IP addresses are in use on a single card.

Desktop:

• In 4.0.19, a new Option on the Rule level has been added to allow the user to turn on (or off) the copying of Netware Extended Attributes.

There have been numerous internal and cosmetic changes.

Return to top of page

---

SureSync Version 4.0.17 Known Issues

Version 4.0.17 was posted on May 3, 2002.

File Synchronization:

• There were circumstances when a multi-mirror monitor would delete files if a path was lost while the Monitor was running. These files would be added back when the missing path came back on line, but the latest changes might be lost. This has been fixed in 4.0.18.
• In some rare cases SureSync would have a Delta Block Sequence Error. This has been fixed in 4.0.18.

SPIAgent:

• There were some SPIAgent communication errors such as not being able to communicate with the local agent and remote agents going off line. Several changes have been made to improve communication in 4.0.18.
• When an SPIAgent goes off line while a synchronization is running it often took a long time to notice and report the problem. The recognition process has been streamlined in 4.0.18.

Monitor:

• If a remote agent was not running when a Monitor was started then SureSync would disable the path (as expected), but produce extra errors (usually "Object Variable or With Block Variable Not Set"). When the path came back on line it would often still not be recognized. This has been resolved in 4.0.18.

There have been numerous internal and cosmetic changes.

Return to top of page

---

SureSync Version 4.0.16 Known Issues

Version 4.0.16 was posted on April 30, 2002.

SPIAgent:

• The SPIAgent was reporting a non-error message as an error message. Error 207, End of List, is not an error and will not be reported as such in version 4.0.17
• The SPIAgent was occasionally reporting excessive time reading files when it didn't need to. This has been rectified in version 4.0.17.

Error Reporting:

• A few errors were missing descriptions when they were logged. In version 4.0.17, the full description should be available.

Database:

• When running a monitor, if too many events and messages were occurring at one time the database would produce error 3218, Could Not Update; Currently Locked. In version 4.0.17 this should no longer be a problem.

Return to top of page

---

SureSync Version 4.0.15 Known Issues

Version 4.0.15 was posted on April 18, 2002.

SPIAgent:

• If a Monitor is canceled between intervals, the job stops waiting for SPIAgent to close down. If SPIAgent produces a timeout error and never reports back, the job will hang. This is fixed in 4.0.16.
• 4.0.16 fixes a Multicast Loopback error. This error was causing a synchronization job to fail in some cases if it referenced a remote agent, and it also produced UDP errors in the event log.

File Synchronization:

• Sometimes when SureSync copied files with alternate data streams you would see an error that said "Not all bytes have been written" and the copy would fail. This has been resolved in 4.0.16.
• When running synchronizations to a Solaris FTP site SureSync would report "Cannot add file when file already exists". This has been fixed for 4.0.16.

Licensing:

• Expiring trial licenses when mixed with valid permanent license codes were causing all the licenses to be invalidated. In 4.0.16 this is no longer the case.

Error Reporting:

• Some open file errors were not properly reported. In 4.0.16 the reporting of these errors is accurate.

Real-Time Monitors

• If the Relations you defined for a Monitor used the Rule Subfolder field to filter the folders to be monitored, then the resulting Monitor would occasionally fail to perform the initial scan of the folders. This problem is resolved in 4.0.16.

There have been numerous internal and cosmetic changes.

Return to top of page

---

SureSync Version 4.0.14 Known Issues

Version 4.0.14 was posted on April 4, 2002.

SPIAgent:

• There was an error copy security when using agents. This is no longer a problem in 4.0.15.
• Multi-homed network machines were having difficulties seeing remote agents on one of their two subnets. Many changes were made to 4.0.15 to handle multi-homed machines and this should no longer be a problem.
• The local agent was reporting superfluous time-out errors in the event log. In 4.0.15 the time-outs are handled differently and the errors should only be reported when the agent has truly timed out.
• In some cases browsing using an agent on Windows NT4 SP6 would not work. In 4.0.15, this has been resolved.
• There was a problem starting the agent service on Windows XP home edition, this has been resolved in 4.0.15.

Real-Time Monitor:

• Monitoring overlapped root paths at the same time with the same agent on different jobs, change events would be only reported to the first job and the second job would not have the information. This is fixed in 4.0.15.

File Synchronization:

• When copying from a non-Netware drive to a Netware drive, SureSync was reporting errors copying read-only attributes. This has been fixed for 4.0.15.
• For some types of FTP servers SureSync was periodically getting "Cannot scan folder" errors. This error has been fixed in 4.0.15.
• Occasionally at the end of a schedule the File Synchronization component of SureSync would crash or get a Dr. Watson error, even though the job completed properly. This has been handled in 4.0.15.
• If you had a job with Open File support turned on but no retries set up, then SureSync was unable to copy open files with alternate streams. If retries were enabled the file could be copied. In 4.0.15 the open file will copy properly whether or not there are retries set.

Desktop Interface:

• If you edited a root path to change it's agent you sometimes received a subscript out of range error. This has been fixed for 4.0.15.

Database:

• Additional work done in 4.0.15 on the database error that said "too many tables open".
• If you are running multiple jobs with lots of updates concurrently sometimes you see an error stating tables are locked. This has been fixed for 4.0.15.

Return to top of page

---

SureSync Version 4.0.13 Known Issues

Version 4.0.13 was posted on April 2, 2002.

Licensing:

• There was a problem with some of the new version 4 serial numbers being seen as invalid. The validation procedure is now properly identifying serial numbers in 4.0.14.
• Workstation licenses were not letting you do a standard synchronization to a server. In 4.0.14 you can synchronize to up to 2 servers with a workstation license. However, by design, running a real-time synchronization to a server will require the server to have an agent license.

Real-Time Monitor:

• If you have a Monitor with multiple Relations there were certain cases where you would lose some file history. This would mainly effect multi-mirrors (it would add files back instead of deleting them, or attributes only changes might occur in the wrong direction). This problem was fixed in 4.0.14.
• When a file in a monitored folder was renamed, SureSync would properly rename the file on the destination, however it was issuing an extraneous "File changed in multiple places" error message. This has been fixed in 4.0.14.

Database:

• When you attempted to copy or upgrade large databases (over 150 Relations) the operation would fail with an error that said there were too many tables open. This has been handled in version 4.0.14.

Return to top of page

---

SureSync Version 3.1.19 Known Issues

Version 3.1.19 was posted on January 30, 2002.

Attribute Changes

• If files are different by only their attributes, the attributes are not being altered on the destinations. This problem was corrected in version 4.0.

Return to top of page

---

SureSync Version 3.1.18 Known Issues

Version 3.1.18 was posted on October 31, 2001.

Real-Time Monitor:

• If SureSync was running a monitor that encountered a problem and needed to re-queue a file to attempt to copy it again the path was get garbled in some cases. This was causing some changes not to be copied over to the destination. In version 3.1.19 the correct paths are being passed to the queue.

Scheduler:

• Occasionally when running as a service the Scheduler would hit a problem and fall into a loop, using all available CPU time. It would also begin to report COM+ errors in the Event Log. This problem has been solved for version 3.1.19.

DCOM setup:

• If you were running SureSync on Windows XP and attempted to set up DCOM, the Scheduler and File Synchronization engine would not function properly if you left the Authentication Level on default. This has been fixed in version 3.1.19.

Job Log:

• If you tried to display the help file from the SureSync log, it would produce an error. The log should be able to access the help file properly in version 3.1.19.

File Synchronization:

• When when running a synchronization that had an FTP destination, on some servers SureSync would not be able to get information on files during the scan. This caused "file already exists" errors and the synchronization would fail. This issue has been resolved in version 3.1.19.

Return to top of page

---

SureSync Version 3.1.17 Known Issues

Version 3.1.17 was posted on August 22, 2001.

Real-Time Monitor:

• There were occasional problems with monitors correctly handling fail-over in cluster servers. Improvements have been made to Real-Time monitor in version 3.1.18 to always recover properly from a cluster server fail-over.

Error Handling:

• There was a built-in limit on the number of errors a job would accept before automatically canceling. In 3.1.18 and later you can use special registry settings to control the maximum errors before the automatic program cancel. Contact Software Pursuits for instructions on how to implement this feature.

Preview:

• The preview was unable to display in the file list more than 32,767 files in a single folder, this limitation has been removed in version 3.1.18.

Return to top of page

---

SureSync Version 3.1.16 Known Issues

Version 3.1.16 was posted on June 6, 2001.

Real-Time Monitor:

• When monitoring a file that was open, we sometimes failed to copy the file when it was finally closed. This seemed to especially affect Excel files. In version 3.1.17 these files are now requeued to wait for closure.
• For monitors with long delays between the file changes and the actual copying of files (low priority), SureSync was sometimes logging extraneous "file changed on multiple roots" warnings. This has been fixed in 3.1.17.
• If a problem occurred while scanning a folder, the specifics about what error occurred were not being properly reported. This has been fixed in 3.1.17.

Database:

• Occasionally a SureSync database will corrupt due to system crashes or other unexpected stresses, to help recover if the standard database repair and compact don't fix the corruption, we have added the ability to copy a database information to a new database to eliminate the corruption. In version 3.1.17, just use File | Copy Database from the SureSync desktop program to get a clean database with duplicate info.

Priorities/Load Balancing:

• The network load balancing option has been upgraded to use a high resolution timer. We were finding that if you asked for a 50% load on the network, the jobs were not necessarily taking twice as long as they should. As networks and computers got faster, our timer accuracy introduced larger errors in our calculations. The new timer is incorporated in version 3.1.17.

Return to top of page

---

SureSync Version 3.1.15 Known Issues

Version 3.1.15 was posted on May 11, 2001.

Installation:

• The install would not properly recognize network installs to allow you to install a client to run from a network copy. This has been fixed in 3.1.16

Client/Server Issues:

• When shifting between databases an erroneous error would be displayed saying the program was already synchronizing with another database. This error was harmless as it did not stop you from opening the new database, but we have been fixed that message in 3.1.16 to only display when there is a true discrepancy.
• When running a client version of SureSync and referencing a database for a server copy, there was a problem getting a synchronization executed by doing a 'Run Now' to run from the server it should. This has been fixed in 3.1.16.

Return to top of page

---

SureSync Version 3.1.14 Known Issues

Version 3.1.14 was posted on April 12, 2001.

File Synchronization:

• There were certain cases where an FTP synchronization that referenced the FTP root with no folder information following would not be able to scan the FTP site. This seemed to happen when there was an unexpected or unknown default folder set for the FTP server (usually set to the user name). The synchronization was then directed to a location where it did not have permissions to scan and hence it returned 0 files. In version 3.1.15 SureSync will be able to properly redirect the scan request to the appropriate folder.

Real-Time Monitors:

• SureSync real-time Monitors were occasionally producing unnecessary warnings that communication was lost to the SPIWatch agent on the remote machines. This has been fixed in 3.1.15.

Return to top of page

Sales: 800-367-4823
Email Sales Team
Technical Support

Search SPI's Site:

 

Additional Resources

• Upgrade to Version 6.0
• Download Free Trial
• Request SureSync Quote