Readme.txt for ***SureSync Version 4.1*** from Software Pursuits
Please visit our Web site at www.SoftwarePursuits.com for updates and additional information on this product.
This product is protected by International Copyright Laws and is licensed, not sold. Please refer to the license agreement in License.txt or on our website.
Please use the Help system for this product for troubleshooting information.
Please forward any questions, comments, concerns AND SUGGESTIONS to the address listed at the end of this file.
----------
***SureSync Release Dates
6/09/04 Version 4.1.22
----------
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.1.23 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
-- Close SureSync before installing
BEFORE INSTALLING version 4.1, if you've been running a previous version of SureSync on the same machine, make sure you close down *all* pieces of SureSync before running the installation for 4.1.23. If you've been running the Scheduler service, TURN OFF THE SERVICE. (And if you were using 3.0 or earlier UNINSTALL IT. You can uninstall it by going to the Options panel in SureSync and unchecking the box to configure the service.)
--- SureSync requires MDAC
To make SureSync Windows 2000/XP compatible, SureSync now requires that MDAC 2.71 or higher be installed on Windows NT/98/ME (MDAC is Microsoft Data Access Controls). You can download the MDAC setup from the Microsoft web site at:
http://www.microsoft.com/data
If you download MDAC 2.6 or higher it does not contain all the components necessary to run SureSync. Microsoft separated some of the data components out after version 2.5 If you wish to use MDAC 2.6 or 2.7 you must install MDAC 2.5 first and then upgrade, or you must also install the Microsoft Jet 4.0 Database components. You can download Jet from the Microsoft website at:
http://www.microsoft.com/data
Or for more information go to:
http://support.microsoft.com/support/kb/articles/q239/1/14.asp
MDAC 2.5 and later require that Internet Explorer (version 4.01 or higher) is installed on the machine as well. We regret the necessity of requiring IE in order to run SureSync, but there was little choice if we wanted to be able to become Windows 2000 compliant. You do not need to use IE as your default browser, but it needs to be installed in order to update certain system components to required versions. We apologize for any inconvenience. You can download IE from: http://www.microsoft.com/windows/ie/default.htm
--- Can only upgrade the SureSync database from 3.0x or 3.1.x
Due to database changes you can only directly upgrade from 3.0 (any letter) or 3.1 to the new version. If you are running 2.1 or earlier you will either need to uninstall SureSync before installing 3.1 or you must upgrade your old version to SureSync 3.0 and then upgrade 3.0 to 3.1.
--- You must re-configure DCOM if you were using it for 3.0 (or earlier)
Once you've installed 4.1, you will need to re-setup DCOM (if you were using 3.0 and earlier) and then you can re-install your service and turn it back to automatic. We recommend that you run the program once in standard mode before you re-setup DCOM. The application names displayed in DCOM config will have changed to:
SPISureSyncFile4.SPIFileSync
SPISureSyncSched3.SPIScheduler
If you have 3.1 or 4.0 installed you will not need to go through this process, it will be handled automatically.
The other SPI applications listed in DCOM should also be configured. If you configured them in 3.0 or 3.1.x they should still be configured for 4.1; if you did not, then you should configure them now.
--- Version 4.1 will be installed with Windows Installer
To be more completely Windows 2000/XP complient SureSync now uses the Windows Installer to install the program.
************* General Notes about 4.1
1] SureSync supports Windows NT/2000/XP and Windows 98/ME. Windows 95 will no longer be supported. SureSync will require that if you are running Windows NT4 you have SP6 (or higher).
************* New Features in 4.1 (compared to 4.0)
1] Archive
Archive is a optional feature that creates an Archive from which data can be restored on a disk array, NAS or other media to guard against data being lost or damaged. This is can be used in place of tape backups.
2] File versioning
File version can be used inside of the archive to retain multiple copies of data throughout a specific interval. If a user wishes to restore a particular version of a saved file the version can be retrieve from the archive.
3] MSDE/SQL Database
SureSync will now accept either MSDE or SQL database to store settings and file history. Jet/Access is still the default, but can be migrated to SQL by going to File | Database menu and copying your database to the new format.
************* Features in 4.0 (compared to 3.1)
1] SPIAgent
SPIAgent is a new component that can provide communications services for SureSync. When SPIAgent is installed on your servers, SureSync is able to provide many of the new features below. SureSync can operate without using this agent in the same manner as it operated in prior versions. With the agent, however, new and more efficient methods can be used to transmit your files.
SPIAgent also replaces the SPIWatch program, which powered the Real-Time option in SureSync 3.1.
2] Adaptive Delta Technology
Past versions of SureSync copied entire files whenever a change was detected. With SureSync 4.0, using Adaptive Delta Technology, only the portion of the file that has changed will be transmitted to the specified destinations, making synchronization tasks faster and more efficient across your network's infrastructure.
3] Quality of Service (QoS)
The QoS feature allows SureSync administrators to specify precise network loading for SureSync jobs. You can use this feature to insure that SureSync synchronization traffic does not interfere with more critical transmissions.
4] File Compression
SureSync now gives you the option to transmit files in a smaller package by compressing them. File compression is particularly useful on slower networks because it enables you to transmit the same amount of data faster.
5] TCP/IP Transmissions
SureSync can synchronize any file it can access via the file system. Using remote SPIAgents, it can also access file systems on remote machines via TCP/IP. SureSync can even access its agents through a proxy server, permitting you to synchronize files via the Internet through your firewall.
6] Encryption
SureSync 4.0 offers users the ability to encrypt each and every file transmission for improved security. This is especially important if you want to synchronize files via the Internet.
7] Multicasting
Multicasting allows SureSync to send data to multiple destinations simultaneously with a single transmission. This can greatly reduce the network load required to synchronize files on your servers.
8] Enhanced Preview Mode
SureSync's Preview Mode has a new option to show you your files in a single list. Rather than having to scroll through a Tree, SureSync's new preview option will display which files are changing and where, allowing you to easily process or override operations. You can switch back and forth between the Tree format and the new format as you are viewing the Preview.
************* Fixes Since 4.1.22
1] 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.
2] 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.
3] 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.
4] 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.
5] 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.
6] Real-Time Monitors could report an extraneous error "unable to signal current scan position to agent". This has been fixed in 4.1.23.
7] 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.
8] "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.
9] When running under Japanese Windows jobs would crash during termination of the job. This has been fixed in 4.1.23.
10] 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.
11] Record is deleted errors would sometimes occur when multiple monitors are running at midnight. This has been fixed in 4.1.23.
12] 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.
13] 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.
14] 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.
************* Fixes Since 4.1.21
1] New Feature: Advanced Open File Support.
2] 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
3] SPIDcom.exe produced an error attempting to get DCOM information (could not find SPISecur.dll). This has been fixed in 4.1.22.
4] Alert configuration did not launch from the Tools menu (file not found). This has been fixed in 4.1.22.
5] Alert configuration did not launch from the Alerts tab in Tools | Options. This has been fixed in 4.1.22.
6] Alerts at the end of a schedule were not being sent. This has been fixed in 4.1.22.
7] 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.
8] It was possible to receive timeouts when copying very large databases. This has been fixed in 4.1.22.
9] 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.
10] It is now possible to create SQL databases with a hyphen in the name. This has been fixed in 4.1.22.
11] Concurrency errors on Jet databases were not retried in some cases. This has been fixed in 4.1.22.
12] Improvements have been made to the desktop refreshes. These improvements can be found in 4.1.22.
13] Lock files and databases for SureSync and ArchiveSync can now be stored in the same folder. This change was made in 4.1.22.
14] Unable to preview in Windows 2003. This has been fixed in 4.1.22.
15] 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.
16] Obsolete file history was not being purged from the database properly. This has been fixed in 4.1.22.
17] There were problems creating non-English SQL server databases. This has been fixed in 4.1.22.
18] Unable to change an existing rule to a compare rule. This has been fixed in 4.1.22.
19] 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.
20] Performance of SQL server databases has been improved. This improvement can be found in 4.1.22.
21] Previewing jobs that need to copy security and then not running the job from the preview may prevent the security from being copied on the next run of the job. This has been fixed in 4.1.22.
************* Fixes Since 4.1.20
1] 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.
2] With a SQL database duplicate keys on NodeID.FileName on monitor events were possible. This has been fixed in 4.1.21.
3] In real-time monitors dropped paths were not always retried in a timely manner. This has been fixed in 4.1.21.
4] 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.
5] Real-time monitors may report subscript out of range or variable not set error messages. This has been fixed in 4.1.21.
6] Wrap trace functionality has been added to the SPIAgent. This diagnostic improvement was made in 4.1.21.
7] 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.
************* Fixes Since 4.1.19
1] 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
2] SureSync would fail to reconnect to agents in some cases. This has been fixed in 4.1.20.
3] 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.
4] 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.
5] Remote agent threads could crash in some instances. This has been fixed in 4.1.20.
6] Lock files location and license table are now handled on a database copy. This has been fixed in 4.1.20.
7] 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.
8] 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.
9] In some instances real-time monitors could enter into a timer loop on path retry. This has been fixed in 4.1.20.
10] 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.
************* Fixes Since 4.1.18
1] 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.
2] 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.
3] 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.
4] ArchiveSync restores skipped restoring of files if the folders on the destination did not exist. This has been fixed in 4.1.19.
5] 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.
6] Cache sequence errors could occur in ArchiveSync jobs. This has been fixed in 4.1.19.
7] 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.
************* Fixes Since 4.1.17
1] If the monitor stops with the error "The path is not being monitored by an agent on the same machine..." a secondary error occures "Object variable or with object variable not set". This has been fixed in 4.1.18.
2] Monitor may report that an agent is not running on a path when an agent was specified. This has been fixed in 4.1.18.
3] Database copy did not work when commas were the default decimal separator (most European languages). This has been fixed in 4.1.18.
4] 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.
5] Multiple agent monitor might associate dropped SPIAgent with the wrong server. This has been fixed in 4.1.18.
6] Database open error with SQL Error = 3050 was not being retried. This has been fixed in 4.1.18.
************* Fixes Since 4.1.16
1] Corrected a script problem that would not allow SureSync to install because the MDAC was not up to date with the most recent version.
2] Unable to create or copy a SQL database. This has been fixed in 4.1.17.
************* Fixes Since 4.1.15
1] SQL Server objects might have incorrect ownership values. This has been fixed in 4.1.16.
2] 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.
3] Concurrency errors with SQL Server. This has been fixed in 4.1.16.
4] Path names greater than 255 characters may cause errors when using the SPIAgent. This has been fixed in 4.1.16.
5] Agent may fail to immediately recognize that a monitor path has been lost. This has been fixed in 4.1.16.
6] Missing agent logon errors when reconnecting to dropped monitor path. This has been fixed in 4.1.16.
7] Errors when copying FTP to FTP without any non-FTP access. This has been fixed in 4.1.16.
8] Some Real-Time agent errors were not recognized in a timely manner. This has been fixed in 4.1.16.
9] RAS was not being fully initialized before connecting to a remote agent. This has been fixed in 4.1.16.
10] Deltas suppressed on non-local drives. This has been fixed in 4.1.16.
11] Desktop refresh times improved and multiple requests for refresh handled more efficiently. These improvements can be found in 4.1.16.
12] Monitor hangs saying 'Purge obsolete Job Logs'. This has been fixed in 4.1.16.
13] Files with invalid created dates could cause "error thining 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.
14] Fixed "New Rule" button so it goes through proper panel sequence.
************* Fixes Since 4.1.14
1] Could not update currently locked when running multiple jobs. This has been fixed in 4.1.15.
2] Alternate data streams not supported error after reconnect with monitor. This has been fixed in 4.1.15.
3] UDF file systems for DVDs write incorrect dates. We correct the date when reading UDF systems. This has been fixed in 4.1.15.
4] Cannot monitor drive root when specified by a drive letter not a share. This has been fixed in 4.1.15.
5] Scheduler terminates after 3 failures to open database. This has been fixed in 4.1.15.
6] 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.
7] New error messages when desktop cannot communicate with scheduler. This has been fixed in 4.1.15.
8] Opening SQL databases using a data source fails. This has been fixed in 4.1.15.
9] 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.
10] 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.
11] In some cases when a file copy is aborted, temp files are not cleaned up. This has been fixed in 4.1.15.
12] Failed to warn user if agent is not used in the monitor. This has been fixed in 4.1.15.
13] Monitors cancel when compressed file transmission fails on communications error. This has been fixed in 4.1.15.
14] Alerts fail with "Failure to open database". This has been fixed in 4.1.15.
15] Copying a relation multiple times would fail without renaming the relation. This has been fixed in 4.1.15.
16] Deltas now compress when the option is selected.
17] Improved delta performance.
18] Local agent lost communications with remote connection. This has been fixed in 4.1.15.
19] VBS scripts fail on Invalid Procedure call. This has been fixed in 4.1.15.
************* Fixes Since 4.1.13
1] Failed to recognize stream support on NT4.0 systems. This has been fixed in 4.1.14.
2] Record already exists error for Archive monitor with history. This has been fixed in 4.1.14.
3] Monitors can handle longer paths.
4] Monitors with realtions using the "do not copy if top level folder does not exist" option were copying files anyway. This has been fixed in 4.1.14.
5] Monitors with multiple relations (with different number of paths) will give a "Subscript our of range" error and end the job. This has been fixed in 4.1.14.
6] Database updated to improve performance and security.
7] (Pause) repeats on Progress Panel when cancel button is used with DCOM. This has been fixed in 4.1.14.
************* Fixes Since 4.1.12
1] 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.
2] Reduced memory usage on large folders and fixed memory leaks.
3] "Failed to write all bytes" error on alternate named data stream file. This has been fixed in 4.1.13.
4] May fail to retry lost path in monitor. This has been fixed in 4.1.13.
5] Clicking on desktop tree immediately after the preview (before it finishes refreshing) causes an error. This has been fixed in 4.1.13.
6] 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.
7] The log would not display from the (non-DCOM) scheduler. This has been fixed in 4.1.13.
8] If the latest checkbox was not checked the proper warning was always issued and multi-change files would overwrite. This has been fixed in 4.1.13.
9] Progress panel, when run from a preview, was mis-sized. This has been fixed in 4.1.13.
10] Obsolete archive folders were being deleted. This has been fixed in 4.1.13.
11] Paths lost in the middle of copying a file had errors trying to recover. This has been fixed in 4.1.13.
12] 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 changes status to on hold. Now keeps busy status.
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.
************* Fixes Since 4.1.11
1] Progress Panel not displaying automatically. This has been fixed in 4.1.12.
2] Errors if the user tries to use non-default port numbers. This has been fixed in 4.1.12.
3] RealTime Monitor issues a "subscript out of range" error when new monitor intervals are started. This has been fixed in 4.1.12.
4] Improvements have been made to the scan performance and processing of large directory trees.
5] Display error on the security tab of the rule. This has been fixed in 4.1.12.
6] "Object variable not set" error on file copy retries. This has been fixed in 4.1.12.
7] Folder security values did not display properly after being copied. This has been fixed in 4.1.12.
8] SureSync could not rename destination files on Maxstor NAS devices. This has been fixed in 4.1.12.
9] Error copying permissions on reconnected monitor path. This has been fixed in 4.1.12.
10] A import and export of path lists feature has been added to the current version.
11] Delta block sequence error possible with multiple destnations. Each path being different. This has been fixed in 4.1.12.
12] Performance improvement with large monitor queue.
13] Unable to locate session by index and fails to retry path. This has been fixed in 4.1.12.
14] Local server path move may cause a license error. This has been fixed in 4.1.12.
15] Error writing statistics outside of the USA. This has been fixed in 4.1.12.
16] "Not enough storage" error occurs on the write file for deltas. This has been fixed in 4.1.12.
17] If you detected a root path with an Agent the server would no longer be marked as an agent even if it is still used as an agent on other paths. This has been fixed in 4.1.12.
18] SQL Error on FileHistory on non-USA locales. This has been fixed in 4.1.12.
19] Folder security values may not be set correctly. This could cause a loop in the RealTime monitor. This has been fixed in 4.1.12.
20] FTP may cause an error if "," is imbedded in the directory list. This has been fixed in 4.1.12.
21] If database paths contain a single Quote mark, the job log willnot open the property and alert configuration utility. This has been fixed in 4.1.12.
22] When deleting a pth that will cause a rule to be deleted we will ask before processing the delete.
23] Errors while copying EFS files. This has been fixed in 4.1.12.
************* Fixes Since 4.1.10
1] "Incorrect Function - SetFilePointer" message on delta processing when copying security. This has been fixed in 4.1.11.
2] FTP error recovery fails to set folder causing a folder not found message. This has been fixed in 4.1.11.
3] RealTime Monitor loops if path retry occurs while processing a file or folder. This has been fixed in 4.1.11.
4] Improved delta performance.
5] Monitor with date range rules may skip files until job restarts. This has been fixed in 4.1.11.
6] Get Server
7] 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.
************* Fixes Since 4.1.9
1] 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 has been fixed in 4.1.10.
2] Cosmetic changes to the interface have been made.
3] SQL performance improvements have been made.
4] Fixed inability to convert SQL to Jet if user altered data paths. This has been fixed in 4.1.10.
************* Fixes Since 4.1.8
1] Optimistic concurrency check with SQL Server failing. This has been fixed in 4.1.9.
2] SPIAgent crashes randomly. This has been fixed in 4.1.9.
3] Loop on Archive thinning for Monitor when only thinning is needed. This has been fixed in 4.1.9.
4] Always get trace logging no matter what was requested. This has been fixed in 4.1.9.
5] Multi-mirror monitor might fail to copy added file. This has been fixed in 4.1.9.
6] Interval statistics now logged.
************* Fixes Since 4.1.7
1] SQL server timeout errors. Errors on rename only and only on monitors. This has been fixed in 4.1.8.
2] BOF or EOF true error when renaming a folder during a Real Time Monitor. This has been fixed in 4.1.8.
3] SQL Server could not find the lock path with instance name causing errors. This has been fixed in 4.1.8.
4] Unexpected history found,using a SQL server database when root path is deleted. This has been fixed in 4.1.8.
5] Error in Copy/paste function in Relations when using SQL database. This has been fixed in 4.1.8.
6] Cosmetic changes to desktop.
7] FTP error. Parameter is incorrect on Set time. This has been fixed in 4.1.8.
8] Improved Archive retension periods.
9] Enhanced statistics table.
10] Browse error occurs on Rule subdirectory. This has been fixed in 4.1.8.
11] SQL duplicate key errors. This has been fixed in 4.1.8.
12] If the path is found in a schedule, reporting additional "Object variable with Block variable not set" error. This has been fixed in 4.1.8.
13] Delta performance improvements.
14] Errors writing alternate data streams.
15] If there are server licenses missing, SureSync gave "Path not found" error. Now it says "Path not licensed".
16] 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.
17] Unable to monitor files on Win98. This has been fixed in 4.1.8.
18] When using the Restore file version override on Preview, the incorrect action was displayed. This has been fixed in 4.1.8.
************* Fixes Since 4.1.6
1] Move rule is deleting source files even if copy fails, due to the Open Files Option. This has been fixed in 4.1.7.
2] SQL Server runs too slow and may have timeout errors. This has been fixed in 4.1.7.
3] Copy/Paste of Relations from Jet to SQL was failing with no errors. This has been fixed in 4.1.7.
4] When using SQL databases, and open the desktop on a different machine, busy status was getting reset. This has been fixed in 4.1.7.
5] Lost connection to local agent. This has been fixed in 4.1.7.
6] Improved agent error recovery. This has been fixed in 4.1.7.
7] Compare method now treats all paths equally - there is no source.
8] "SPIAgent request when already busy" fixed.
9] Preview was displaying folder icons incorrectly. This has been fixed in 4.1.7.
10] Archive thinning error causes overscan on archive and possible sequence error in archive. This has been fixed in 4.1.7.
11] Multi-mirror needs to select proper source path on security changes. This has been fixed in 4.1.7.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.1.6 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.1.5
1] Added a Compare function.
2] Agent hangs on copy to remote agents. This has been fixed for version 4.1.6.
3] "Cache sequence error" when archiving Excel files. This has been fixed for version 4.1.6.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.1.5 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.1.4
1] 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.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.1.4 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.1.3
1] Jobs may not be cancelled immediately if connection to SPIAgent is lost. This has been fixed for version 4.1.4.
2] Add/Change priority definition or FTP Profiles, when running with SQL database, causes an error. This has been fixed for version 4.1.4.
3] Jobs may read security values when not requested to causing errors of locked permissions. This has been fixed for version 4.1.4.
4] Preserving security on replaced files does not always work properly. This has been fixed for version 4.1.4.
5] Subscript out of range error if only a delete rule is in the job. This has been fixed for version 4.1.4.
6] Archive orphan file errors. This has been fixed for version 4.1.4.
7] Delta sequence error encountered if multiple paths, each with different older versions. This has been fixed for version 4.1.4.
8] Encrypted files do not get correct dates in archive. This has been fixed for version 4.1.4.
9] Multi-relation monitors sometimes errors on internal changes. This has been fixed for version 4.1.4.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.1.3 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
1] Additional work has been done in version 4.1.3 in order to recover Monitor paths that have dropped and then restored.
2] 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.
Numerous bug fixes and cosmetic changes have been made for bugs reported in 4.1.2 Beta.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.1.2 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.1.1
Numerous bug fixes for bugs reported in the 4.1.1 Beta
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.1.1 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.22
1] In the previous version a monitored path would not be scanned when the job started. This has been fixed for version 4.1.
2] Some people experienced an EOF/BOF error on monitor empty folder. This has been fixed for version 4.1.
3] Security compared before copying and security changes can be previewed.
4] 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.
5] Schedules with multiple relations may not be able to copy security after the first relation. This has been fixed for version 4.1.
6] Negative bytes copied reported on Progress form has been corrected for 4.1.
7] Windows 98 string comparison problem on TM characters has been corrected for 4.1.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.0.22 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.21
1] 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.
2] The busy/standard icons on the SureSync desktop were not properly refreshing at times. This has been resolved in 4.0.22.
3] 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.
4] Version 4.0.22 has improved recovery from WSAENOBUFS errors.
5] 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.
6] 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.
7] 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.
8] 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.
9] 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.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.0.21 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.20
1] 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.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.0.20 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.19
1] There was a problem copying a Relation when the agent was not accessible. This has been fixed in 4.0.20.
2] In previous versions of 4.0 there was problems copying a Relation after changing databases. This has been fixed in 4.0.20.
3] 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.
4] 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.
5] Sometimes there were occasions during a monitor when the agent reported time-out errors. These have been fixed for 4.0.20.
6] 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.
7] 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.
8] 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.
9] 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.
10] Unnecessary table locked errors were occurring. These have been resolved in 4.0.20.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.0.19 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.18
1] In 4.0.19, we have improved performance when copying using deltas.
2] 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.
3] 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.
4] 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.
5] 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.
6] 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.
7] 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.
8] 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.
9] In version 4.0.19, more work has been done on recovering a Monitor when SureSync loses a connection to an Agent.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.0.18 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.17
1] 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.
2] 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.
3] 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.
4] In some rare cases SureSync would have a Delta Block Sequence Error. This has been fixed in 4.0.18.
5] 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.
6] There have been numerous internal and cosmetic changes.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.0.17 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.16
1] 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
2] A few errors were missing descriptions when they were logged. In version 4.0.17, the full description should be available.
3] The SPIAgent was occasionally reporting excessive time reading files when it didn't need to. This has been rectified in version 4.0.17.
4] 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.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.0.16 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.15
1] 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.
2] 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.
3] Expiring trial licenses when mixed with valid perminent license codes were causing all the licenses to be invalidated. In 4.0.16 this is no longer the case.
4] 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.
5] Some open file errors were not properly reported. In 4.0.16 the reporting of these errors is accurate.
6] 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.
7] 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.
8] There have been numerous internal and cosmetic changes.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.0.15 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.14
1] If you upgrade a very large database from 3.x to 4.0 or copy large databases in 4.0, you would see an error that said "too many tables open. This problem has been handled in version 4.0.15.
2] 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.
3] There was an error copy security when using agents. This is no longer a problem in 4.0.15.
4] 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.
5] 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 truely timed out.
6] 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.
7] 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.
8] In some cases browsing using an agent on Windows NT4 SP6 would not work. In 4.0.15, this has been resolved.
9] 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.
10] There was a problem starting the agent service on Windows XP home edition, this has been resolved in 4.0.15.
11] For some types of FTP servers SureSync was periodically getting "Cannot scan folder" errors. This error has been fixed in 4.0.15.
12] 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.
13] 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.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.0.14 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.13
1] 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.
2] 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.
3] 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.
4] Workstation licenses were not letting you do a standard synchronization to a server. In 4.0.14 you can synchronize to upto 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.
5] 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.
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!== Release 4.0.13 !!==!!==!!==!!==!!==!!==
==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==!!==
************* Fixes Since 4.0.12
1] When you previewed a Relation that was setup to copy a root folder with no subfolders if you clicked in the tree section of the 4 pane preview you would receive an error. This has been fixed for 4.0.13
2] The recovery of a monitor when a machine is booted without warning has been improved for 4.0.13.
3] The copying of Netware trustees has been improved in 4.0.13.
4] When copying from an FTP site to a local machine, SureSync was reporting an error. This has been fixed for 4.0.13.
5] In some cases the preview was not displaying files with no actions, this has been corrected for 4.0.13.
6] There were issues copying attributes if the files themselves did not need to be copied. This has been fixed in 4.0.13.
--------
--------
Software Pursuits, Inc.
1500 Fashion Island Blvd, Suite 205
San Mateo, CA 94404
650-372-0900
Fax 650-372-2912
support@spursuits.com
<end readme>