Download OsaSync update

Upgrade OsaSync PRO

Upgrade OsaSync PRO to version 6.1.1

This download will update your installation of OsaSync PRO to the latest version 6.1.1.

Installation instructions

Installing the upgrade is very easy, it won't take more more then a minute per computer!

Only install the upgrade when you are sure your subscription to upgrades and support has not expired! You can find this expiration date on the OsaSync options page.

Make sure you DO have a previous version of OsaSync PRO installed on you system! If you do not have a version of OsaSync PRO installed yet, download the full version from the download page.

Click the download link below and the update will be downloaded to your computer.

Do NOT uninstall the previous version. Uninstalling removes the support files and registry settings from your system. The upgrade doesn't contain the support files and assumes the registry info is still there.

Make sure there are no changes anymore for OsaSync to process. Click Check for changes on other computers in the OsaSync menu to force OsaSync importing any changes. This is important because it is possible that the new OsaSync version cannot handle the update files created with a previous version anymore.

Close Outlook if Outlook is still running.

After the download has completed run the upgrade installation wizard by double clicking the file OsaSyncProUpd.exe. The installation wizard will guide you through the installation process.
Make sure to install OsaSync in the setup wizard's default folder. This will be the same folder as the previous OsaSync installation folder.

If you run outlook with OsaSync for the first time you can expect a message from your firewall asking if you want to allow OsaSync.exe to be able to access your local network. Please answer Yes.

Copy the downloaded file to your other computer(s) running OsaSync and also install the upgrade there.

All configuration settings made by your previous installation will be retained so there is no need to run the OsaSync connection wizard again. You also do not have to resynchronize any folders after applying the upgrade.

If you upgrade from OsaSync Lite:
First uninstall the Lite version. Use the Uninstall OsaSync from the Windows Start menu - Programs - OsaSync. It is not necessary to remove the OsaSync IDs before doing this. After you have installed the full PRO version you will have to rerun the connection wizard and resync your contacts folders.

Upgrade OsaSync PRO to version 6.1.1 (2.9 Megabytes)

Outlook 2000 users: make sure to run in CW mode!
This latest version contains all previous upgrades so it is not necessary to install previous upgrades first!

If, for some reason you are not satisfied with the 6.0 version you can download the previous 5.10.1 version:
download previous OsaSync 5.10.1 upgrade (install on top of current version)
download previous OsaSync 5.10.1 full version (necessary after uninstallation)

OsaSync PRO Upgrades

New in version 6.1.1 (March 13, 2008)

solved problems:

error# 424 in proc: clsManager.Timerfired. Object Required. This error could occur when Outlook was closed.

New in version 6.1 (March 10, 2008)

new functions:

Read-Only folder syncing has been improved. If a folder is synced as being Read-Only it is not possible anymore to stop the folder synchronization on the computer on which the folder is Read-Only. Similarly it's also not possible to add another computer or to resync the Read-Only folder. These actions can only be executed on a computer on which the folder is NOT Read-Only. It is now possible to undo the Read-Only status of another computer without the necessity to resync the folder. To do this go to the OsaSync folder properties (OsaSync - Synced folder - Properties...) on a computer on which the folder is not Read-Only, select a Read-Only computer in the list and click Undo Read-Only.

A Read-Only folder now gets the suffix '(SY-RO)' if the checkbox 'append (SY) to the name of a synced folder' is set on the OsaSync Advanced Options page.

FTP syncing: when Outlook shuts down OsaSync will upload any pending files to the FTP server before terminating.

solved problems:

If a folder was synced as Read-Only to a subset of the selected target computers (in other words: some computers are RO and some are not) then OsaSync would mark the wrong computer as Read-Only.

When multiple items were moved from a non-synced folder to a synced folder and Outlook was shut down immediately thereafter then OsaSync would be terminated before all changes were processed. This could lead to folders going out of sync. OsaSync will now finish all processing before terminating..

error# 91 in proc: clsManager.ProcessMasterCatsChanges. This error happened when a new category was added in Outlook 2007 while the default pst file (the top level folder that has the inbox folder) is excluded for OsaSync.

Appointments syncing: if a new appointment is created and the property Show time as is changed from busy (which is the default value) to free then this would not be synced and the appointment would show as 'busy' on the synced computers.

New in version 6.0.12 (January 9, 2008)

solved problems:

error # 265 in proc: ItemGeneral.ShareItems. Error in IMAPIProp::SaveChanges: MAPI_E_OBJECT_CHANGED. Happened when an appointment was shared (not synced but shared).

Improvements to the synchronization mechanism for folders syncing with 2 or more computers.

New in version 6.0.11 (January 3, 2008)

solved problems:

error # 91 in proc: clsAImanager.CreateItmsOpenInInspStr. Object variable or With block variable not set

The OsaSync PRO tab in Outlook - Tools did not show the correct license information but always displayed the text 'unregistered'.

error # 271 in proc: clsFolderMonitor.CreateWrappersForStore. Error in GetDefaultFolder - HrGetOneProp(Store): MAPI_E_NOT_FOUND

New in version 6.0.10 (December 19, 2007)

solved problems:

Resynchronization of a folder that was previously synced with an alternative folder name failed if during resync the alternative folder name was not specified anymore.

Improvement of the synchronization of meetings in the Calendar. Some scenario's could lead to duplication of meeting appointments.

Duplicate items were not recognized in the Calendar if the location for the appointment was not filled out.

New in version 6.0.8 (December 14, 2007)

solved problems:

error# 424 in clsManager.TimerFired. When this error occurs it is possible that deleted items were not synced.

error #91 when adding a new Post item to a folder.

0 minute reminders where not correctly synced.

New in version 6.0.7 (December 12, 2007)

solved problems:

In some cases an update to an Appointment, Task or Contact item would not be immediately synced. This could happen if the 2 or more items were still open in separate Outlook windows.

Connection wizard: when the connection wizard ran for the second time the option was chosen to configure OsaSync in Client-Server mode for FTP only while previously OsaSync was configured for LAN or LAN + FTP then a small bug in 6.0 could have OsaSync accidentally delete folders

A computer configured for both LAN + FTP could not connect to the FTP server when the LAN was not available due to the same small bug as above.

New in version 6.0.6 (November 14, 2007)

solved problems:

error# 52 in proc: clsRemDataProcessor.CompDataStart. Bad file name or number

Message OsaSync is not responding is asked too soon. This will now be asked only if OsaSync.exe truly doesn't respond anymore.

small bug that causes a delay in the syncing of snoozed or dismissed reminders. They eventually would get synced but not immediately

New in version 6.0.5 (November 8, 2007)

solved problems:

OsaSync never finishes initialization. The OsaSync menu keeps displaying ' - initializing' and OsaSync.exe keeps consuming a lot of CPU time. OsaSync is unusable and Outlook behaves sluggish. Happened mainly with Outlook 2003 and never with Outlook 2007.
If you experience this problem it is also necessary to create a new Outlook profile. Please click here for a detailed explanation.

Because this new OsaSync version doesn't respond anymore to added or closed Outlook Data files it is necessary to restart Outlook when you manually add an Outlook data file that has one or more synced folders (Outlook File menu - Open - Outlook Data file...). It's also necessary if you are going to MOVE items from an existing synced folder to a folder in the added file.

New in version 6.0.1 (November 2, 2007)

new functions:

This new OsaSync version has little feature changes compared to the previous version. However, much has changed internally. OsaSync is now split in two parts, one part is the Outlook Add-in and the second part is a separate program called OsaSync.exe. A large majority of OsaSync functions has been transferred to this new exe program. This makes the connection between Outlook and OsaSync less tight and results in a faster and more stable Outlook experience (and solves freezing problems with Outlook 2007!).
If you run outlook with this new OsaSync version for the first time you can expect a message from your firewall asking if you want to allow OsaSync.exe to be able to access your local network. Please answer Yes.

OsaSync has become Profile aware. If work with multiple Outlook profiles it is now possible to specify the profiles for which OsaSync should run on the OsaSync Advanced Options page..

solved errors:

If a computer was deleted in client-server mode from the button on the osasync options window then the other computers would not refesh there computer list correctly if they are configured for both LAN and FTP access.

Error# -196609 in proc: clsJournalProc.pmsgImportJournal. Error in _HrGetIDsFromNames - mp == NULL object errorcode: -2147418113. These errors could occur when osasync was merging folder contents during a 'prepare folders for sync' operation and found duplicate items.

Error# 91 in proc: clsManager.SetDataTimersAndMnuBtns. Object variable or With block variable not set. Happened when 2 or more Outlook explorer windows were opened and one window was closed without clicking on the remaining open window.

Several minor tweaks

New in version 5.10.1 (Five point Ten point One; March 2, 2007)

new functions:

In client-server mode it is now possible to remove a computer from the configured computers group. To do this select a computer on the the OsaSync options page and click the 'Delete config info' button. So when a computer is removed it is not necessary anymore to manually edit the CnfComputers.txt file on the LAN and/or FTP server.

When a computer is removed from the configured computers group other computers are notified immediately and refresh their list of configured computers. In previous OsaSync versions this list was refreshed only when Outlook was restarted.

The shortest interval period allowed for FTP file transfers has been decreased to 1 minute.

When OsaSync is started and still busy initializing then some OsaSync menu items like 'checking for changes' are not yet available (grayed out). To make this more clear these menu items names will now be appended with 'initializing...'. These menu items are also not available when OsaSync periodically checks all folders for changes. This will now be visible by the menu item name suffix 'processing...'

solved errors:

OsaSync logging & error tab on the OsaSync advanced options windows has now been translated in French, Spanish, Italian and German. Due to a problem with our translation agency these translations were not ready when we released version 5.9.

Outlook 2000: if PDA support was enabled by right-clicking the folder and choosing folder properties; OsaSync tab then this setting wouldn't 'catch'.

If the notes of a contact, appointment or task was completely deleted this deletion was not seen by OsaSync so the deletion did not sync.

Error# 91 in proc: clsContactImp.ImportContact. Object variable or With block variable not set LineNumber: 33. Happened in Outlook 2007 when OsaSync was importing new contacts and reminders are not synced.

If a contact was open in an window while OsaSync received an update for this same contact then the contact window would be closed and possible changes would be lost. OsaSync will now show a message and postpone the update of the contact until the contact window has been closed.

New in version 5.9 (February 14, 2007)

new functions:

Enhanced conflict resolution for the contact notes and new conflict resolution for the notes of appointments and tasks. If the notes on two computers were updated at the same time it was possible that those notes were swapped: computer A got the updated notes field from computer B while B got the updated notes from A. Previous OsaSync versions also checked to prevent this swapping but that check allowed a time difference of 15 minutes and would only signal differences if the notes field on the other computer was updated longer than 15 minutes ago then the update on the current computer. This was useful to prevent incorrect signaling if the computers' time setting was up to 15 minutes apart. Because most computers nowadays sync the time with an internet time server this period of 15 minutes has now been changed to 2 minutes. If you have just updated the contact notes while OsaSync imports the same notes field that was updated more than 120 seconds before your update then OsaSync will show a window on which you have to choose which update you want to use or you can have OsaSync append the notes from the other computer to the current notes so that you can merge the notes manually. If you find the 120 seconds slack period still to long then this can be changed by setting the Windows registry value BodyDiffSec to a smaller value (In HKEY_CURRENT_USER\Software\OsaSync).

FTP file transfer: when files are zipped it was possible that a large zip file was being downloaded before if was fully uploaded by the remote computer. This resulted in a corrupt downloaded zip file is and can't be opened. OsaSync is now updated to prevent this. A zip file is now uploaded with the file extension 'xxx' and is renamed to 'zip' when the upload is ready. Downloading computers ignore 'xxx' files so the file will remain on the server until the upload is ready.

Whenever OsaSync encounters an error when OsaSync is processing an item outlook, OsaSync will also display the subject of the item.

The location of the log files created by OsaSync has changed. The location \Program files\OsaSync\Log has been changed to \Documents and Settings\All Users\Application Data\OsaSync. On Windows Vista this location is \ProgramData\OsaSync. This change was necessary because Windows Vista doesn't allow applications to create data in a '\Program files' subfolder (unless Outlook runs in elevated mode).

The OsaSync advanced options page has been enhanced with a tab called Logging and errors. This tab shows the log file folder. Both the logging folder and the vosaddin.log file can be opened directly from this tab. A Create email button facilitates the creation of an email to technical support with the vosaddin.log and sync log files attached.

When OsaSync wants to import a contact, appointment or task and sees that this item is already present in the folder then OsaSync will now also present the option to delete the existing item and to continue the import.

Syncing or not syncing of reminders for appointments, tasks, contacts (outlook 2007) and emails has become more consistent. If 'sync reminders' has been disabled on the OsaSync advanced options page then reminders won't fire for new items created by others. In this way you will only get reminders for appointments created by yourself in a common calendar.

FTP transfer: the shortest interval time allowed between two ftp file transfers has been reduced to 10 minutes to 5 minutes.

The OsaSync advanced options page now has a setting to have OsaSync append folder names of synced folders with (SY) in the Outlook folder list. Example: the synced inbox will be shown as 'Inbox (SY)'. By default this option is not set.

solved errors:

Dismissing a reminder did not sync although the box "Also sync reminder changes" in Advanced Options / Outlook Items Options was checked.

Outlook being unresponsive when OsaSync was checking for changes. When at least one other synced computer was offline then OsaSync would cause Outlook to be unresponsive for several seconds.

In peer-to-peer mode the OsaSync options page erroneously displayed 'OsaSync in client-server mode' above the computers list. This off course should have been 'OsaSync in peer-to-peer mode'.

If 'enable PDA support' was set then a delay could be experienced when outlook was closed.

When OsaSync was configured for the first time in peer-to-peer mode the CnfComputers.txt file would be created in the c:\ root folder while this had to be the OsaSync_Data folder.

Several minor tweaks

New in version 5.8.1 (September 14, 2006)

solved errors:

Enabling PDA support for a folder from the OsaSync folder properties window (OsaSync - synced folder - properties...) did not work.

Syncing of snoozed appointments did not work (when OsaSync is set to sync reminder changes on the appointments tab in Advanced Options).

Error# -196609 in proc: clsFldMon.CreateItemNewMsg. Error in _HrGetIDsFromNames - mp == NULL object errorcode: -2147418113 LineNumber: 13

New in version 5.8 (September 7, 2006)

new functions:

Synchronization support for the Outlook Journal folder. Journal items were not supported in previous OsaSync versions.

The OsaSync Options window now lists the current syncing mode for computers configured for both LAN and FTP. Now you can easily see if syncing takes place via the LAN or via the FTP server.

The FTP Options window now has a section which enables the LAN/FTP switching for a selected computer. The existing section to switch modes applies to ALL other (for both configured) computers. This is relevant for laptops. The new section applies to a computer which is still connected to the LAN but has received a message from a laptop to sync through FTP. If for some reason a message to start or stop syncing through FTP is not received then this section enables the switching for that computer only.

OsaSync does not check for duplicate emails in the Drafts folder anymore. This makes it possible to create multiple drafts with the same subject.

By default OsaSync does not sync reminder changes anymore so if you snooze an appointment, task or email reminder this change is not synced. If you do want to sync reminder changes you can click the checkbox Also sync reminder changes on the Outlook item tab on the OsaSync advanced options window.

Supported features for Outlook 2007:
* Contact's business card layout is synced
* Follow up flags and reminders for contacts, tasks, distribution lists, emails and posts are synced.
* The master Categories are synced

Small changes necessary for Windows Vista (beta 2). If you want to run OsaSync on Windows Vista then a small security related setting has to be changed. Please check out our technical support page for details.

solved errors:

Error# 91 in proc: clsFoldermonitor.SyncFldInitOnThis. Object variable or With block variable not set.

Outlook freezing during the import of large Distribution Lists (> 300 members)

Performance enhancement for the moving of multiple emails at once to another folder. There could be a noticeable sluggishness when 5 or more emails were moved, especially when one or more other computers are offline for some time.

Some other minor tweaks

New in version 5.7.6 (June 8, 2006)

solved errors:

The OsaSync folder resynchronization wizard now has an extra step for instructing the wizard to create a new OsaSync folder ID. If folder ID's don't match on all computers then resyncing with the creation of a new folder ID solves this.

If the subject of an email is changed AND the email is moved then the subject change would not always sync correctly.

Adding members to a distribution lists in outlook 2000 or 2002 sometimes resulted in the member being added by OsaSync without an email address.

Error# -196609 in proc: clsContactImp.ImportContact. Error in _HrGetIDsFromNames - IMAPIProp == NULL object errorcode: -2147418113

New in version 5.7.5 (May 4, 2006)

solved errors:

Birthday and Anniversary appointments could be deleted by OsaSync if the Calendar folder is synced and the Contacts folder isn't. Whenever you set a contact's birthday or anniversary Outlook creates a corresponding appointment in the calendar (in Outlook 2002 and higher). OsaSync uses a mechanism to ensure that these new appointments are synced correctly. OsaSync also changes the appointment to a new date if you set the contact's birthday to another date. In order to keep the contact's birthday/anniversary the same with the corresponding appointment and in sync with other computers OsaSync uses a mechanism to link the contact with it's appointment(s). This worked fine except if the default contacts folder was not synced.

clsContactImp.UpdateProperty: error# -2147352567. Error: Property is read-only. This happened when OsaSync tried to update the email display name in Outlook 2000.

A deleted category or user defined field of a contact, appointment, task or email was not deleted on the synced computers.

New in version 5.7.4 (April 13, 2006)

solved errors:

Error# 91 in proc: clsFldMon.RemDuplicatesInFld. FindTaskOnLogicalID: Object variable or With block variable not set LineNumber: 3. This error happened when OsaSync removed duplicate tasks and found a tasks without a due date set.

Email display name fields for contact items did not sync properly.

Error# 459 in proc: clsManager.Start. Object or class does not support the set of events ór:
Error# 196734 in proc: clsManager.Start. Automation error. The specified module could not be found

New in version 5.7.3 (March 5, 2006)

WHEN SYNCING CALENDARS: MAKE SURE TO INSTALL THIS VERSION ON ALL COMPUTERS!

solved errors:

Outlook 2000:
When outlook was closed it could remain in memory (visible in windows task manager). When Outlook was then restarted. OsaSync was not started.

Calendar synchronization with a computer that is set to another time zone: the start- and end times of non-recurring appointments on both computers are the same. This is not correct: they have to take into account the time-zone time difference.

Outlook hanging or crashing. This happened when OsaSync was importing an email and could not save the imported email (for whatever reasons). The alternative approach used by OsaSync for again trying to save the email could crash Outlook.

New in version 5.7.2 (February 27, 2006)

solved errors:

Error# 13 in proc: clsMailProc.pmsgImportMsgFile. Type mismatch. This happened when a forwarded email was synced and could cause Outlook to crash.

Outlook crashed while importing sync calendar sync data. This happens when appointments were synced with the notes field containing text and/or links.

Error# 438 in proc: clsContact.HasContactChanged. Object doesn't support this property or method

Error# 5 in proc: clsDLproc.IsSameMember. Invalid procedure call or argument

Error# 9 in proc: frmSyncWiz.cmdNext_Click. Subscript out of range. /Could happened when syncing in Advanced Mode and multiple folders were selected.

New in version 5.7.1 (February 19, 2006)

new functions:

New folder resynchronization wizard.
If a folder has become out-of-sync it is now very easy to repair this. The new folder resynchronization wizard will guide you through all necessary steps. The resync wizard is similar to the 'prepare folders for synchronization' wizard but adds a few extra's:
- You can choose to have OsaSync delete all items on the target computers. If so, OsaSync will first backup the folder contents to a backup folder.
- Duplicate items can be removed prior to the creation of sync data.
- If there are still many unprocessed OsaSync files from a previous synchronization attempt then the wizard will offer the possibility to delete those files
With this new wizard it's a snap to get your folders back in sync again! To run this wizard choose OsaSync - Synced folder - Resynchronize...

Syncing support for contact attachments. If you attach a file to a contact item this attachment is now also synced.

Syncing support for the contact picture (Outlook 2003)

Syncing support for the links in contacts and appointments

The OsaSync synchronized folder properties can be accessed faster by clicking OsaSync - Synced folder - Properties.... In the Synced folder menu you can also directly add a computer by clicking the Add computer menu item or stopping the synchronization of the folder by clicking Stop synchronization.

The OsaSync peer-to-peer configuration wizard has been enhanced to make it easier to set the same OsaSync_Data folder on both configured computers.

It is now possible to configure OsaSync in client-server mode on a mapped drive instead of on a server. So instead of having to select a UNC path like \\computername\sharename\somefolder\OsaServer you can now configure the OsaServer folder on a mapped drive like X:\somefolder\OsaServer. A mapped drive can be required on a Novell server. The mapped drive also opens new syncing scenario's, for example a USB stick that acts as the 'server'.

Email syncing: the indication that an email is replied to or forwarded (the icon and time) is now also synced.

solved errors:

Tasks: if the due date of a synced task was moved to another date then the reminder on the synced pc was updated to a wrong date.

OsaSync's handling of birthdays and anniversaries has been updated to prevent the creation of duplicate appointments in the Calendar folder.

Error# 438 in proc: clsContact.CreateContactMsgData or in clsCntProc.SetPropsInNamedProps:. Object doesn't support this property or method (error in version 5.7 for outlook XP only)

Some other minor tweaks.

New in version 5.6.3 (January 7, 2006)

solved errors/problems:

When a task folder was prepared for synchronization duplicates could be created if this folder contained instances of recurrent tasks which were already complete. Completed recurrent tasks can’t be synced properly: Outlook keeps generating new tasks when OsaSync tries to sync one. This is why OsaSync deletes a complete tasks instance once the task is set complete. OsaSync has now been updated so that when the folder is prepared for syncing the complete recurrent instances are deleted as well. The remaining not completed recurrent task then syncs normally and there will only be one instance of this task on each computers.

FTP syncing: when OsaSync transfers files with the ftp server and file zipping and encryption is not enabled then it could happen that OsaSync stopped downloading files. Several items are synced by OsaSync by exchanging a .txt and a .msg file with the same file number. If OsaSync found a .msg file on the server while the .txt file was not there it would not continue the download assuming that the .txt file was not yet uploaded. OsaSync has now been changed so that it only waits for the corresponding .txt file three times and will continue downloading all files after thereafter.

Error# 91 in proc: clsDistList.ProcessMembersChanged. Could happen when a member was added to a distribution list.

Error# 13 in proc: clsFolderMonitor.CreateNewFldID. Type mismatch. Could happen when a folder was synced.

When a new task was created with priority low then the priority low status was not synced.

When a folder was prepared for syncing in advanced mode and the folder was set to be Read-Only on the target pc then this Read-Only indication was not set on the target PC. So the folder on the target PC not Read-Only.

When a contacts address field spans multiple lines then this could result in OsaSync continuously generating update files for the synced computer.

New in version 5.6.2 (November 22, 2005)

solved errors/problems:

If a new private recurrent appointment was created and private appointments were set on the OsaSync advanced options page to sync as 'Busy' then only the first instance of this appointment would sync.

The sharing menu item 'Share with computername' would remain greyed out so sharing was not possible if OsaSync was configured to share with only one other computer.

On certain configurations the notes field of a task could be lost when synced by OsaSync

New in version 5.6 (November 14, 2005)

new functions:

It was already possible to protect OsaSync options with a password by setting an option on the OsaSync advanced options page. The ability to run the OsaSync connection wizard and the possibility to prepare folders for synchronization are now also protected by this password. Setting the password will prevent inexperienced users by accidentally stopping a folder sync or by changing the configured computers.

If the reminder time for an appointments or tasks is changed then this changed time will now also be synced.

If a folder was deleted on a synced computer then OsaSync would always ask for confirmation before it deleted this folder on the other computers. This question is now optional: a checkbox 'Ask for confirmation before deleting folders' is added to the advanced options page, tab all items.

solved errors/problems:

Error# 438 in proc: clsCreateSyncData.InitCreateForFolder. Object doesn't support this property or method. This error happened when a folder that is already synced is resynced in advanced mode.

Recurrent appointments: when the subject or location of a recurrent appointment was changed this resulted in a partial loss of recurrence information of the appointment on the synced computers; visible as recurrent appointments being lost!

There were a few scenario's in which OsaSync could pop up a window asking you for a choice while these windows were lacking the option 'Apply the same choice to all other items'. That could result in the necessarily to click the the OK button for each item when OsaSync was processing several items. Now all windows have been updated with the 'Apply the same choice.. ' checkbox.

New in version 5.5.1 (October 30, 2005)

solved errors/problems:

Microsoft recently released Office 2003 Service Pack 2 (SP2) and this service pack accentuates some security related issues. Unfortunately this interfered with OsaSync's way of syncing recurrent appointments and tasks! If you are syncing appointments and/or tasks in folders other then the default appointment or task folder then the update to Outlook 2003 SP2 causes these recurrent items to be synced by OsaSync to the wrong folder: recurrent appointments and tasks end up in their default folder! 5.5.1 fixes this. If you have already noticed appointments or tasks having been synced to wrong folders then it's best to resynchronize your custom appointment and/or task folder after installing 5.5.1.

If a completed task was set again as not started by removing the completed check mark from the task then this would not sync correctly so the task would remain complete on the synced computers.

New in version 5.5 (October 25, 2005)

new functions:

Installation of OsaSync in peer-to-peer mode: it's NOT necessary anymore to install OsaSync on a shared folder or disk. OsaSync can now be installed in the Programs Files folders like any other program. The configuration wizard in peer-to-peer mode has been extended with a step in which the OsaSync_Data folder has to be specified. This OsaSync_Data folder has to exist on a share.

If the subject of an email was changed this change didn't sync. This version now also syncs changed email subjects.

The OsaSyncNew and OsaSyncChanged categories are now disabled by default. To have OsaSync assign these categories to new or changed items it's now necessary to explicitly enabled this on the OsaSync advanced options page, tab All items.

Syncing of the Read/Unread status of emails and posts. This status could not be synced in previous versions. Email was imported either read ór unread according to the setting on the OsaSync advanced options page. By default the Read/Unread status is not synced; syncing is enabled on the Email items tab on the OsaSync advanced options page.

The Compare process has been removed from the OsaSync menu and is now only accessible from the Exceptional produces tab on the OsaSync advanced options window. It is not possible anymore to run the compare process for all folders at once. Also the possibility to schedule the compare process has been removed.
The reason for these changes is that automatic syncing has become so reliable (thanks to the new syncing mechanism implemented in version 5.3) that it will be rarely necessary to compare folders. If for some reason a folder has become out of sync then resyncing the folder (by rerunning the Prepare folders for synchronization wizard) is the best the way to repair this. Only for email folders with a large number of emails running the compare process is a better way to get the folders back in sync (because the email folder compare process only creates compare data for the missing emails and not for all emails so it runs faster then resyncing the folder).
By relocating the compare process to the exceptional procedures OsaSync has become simpler for novice users. Quite a few people had the impression that running the compare process was necessary to have OsaSync synchronize.

solved errors/problems:

Error# 2076377093 (or another number) in proc: clsProtocolProc.pmsgRenameFolder. You don't have appropriate permission to perform this operation.

In some scenarios a folder move could be 'missed' by OsaSync so that this folder was not moved on the synced computers.

New in version 5.4.2 (September 6, 2005)

solved errors/problems:

error# 13 in clsfolderMonitor.CreatNewFldID. This error was introduced in version 5.4.1 and happens when a new folder is synchronized.

FTP file transfer: when ftp file zipping is enabled and the ftp transfer progress window was NOT shown then uploading files would fail.

New in version 5.4.1 (September 2, 2005)

solved errors/problems:

If the OsaSync installation mode was switched from peer-to-peer mode to client/server mode then it was necessary in OsaSync version 5.3 and higher to resynchronize all folders. This has now been repaired so resyncing is now not necessary.

Extra checks have been build in to make sure that whenever OsaSync assigns a new folder ID or a new item ID that these ID's are always the highest numbers thus preventing the creation of duplicate ID's. If there are two outlook folders with the same OsaSync ID then this would lead to data being synced to the wrong folder.

error# 424 in clsManager.InitOsaSyncByTimer: object required.

FTP file transfer: if file zipping was not enabled it could happen that an occasional appointment, task or email file was not synced but remained unprocessed in the osasync_local\computername\IN folder.

New in version 5.4 (August 18, 2005)

important:
When your current OsaSync version number is lower then version 5.3 then please also read New in version 5.3

new functions:

OsaSync top level folder management has been improved: if you work with many .pst files (= top level folders) then it's now possible to select a top level folder to INCLUDE for OsaSync. All other folders are then excluded. If folders from only one .pst file are synced then explicitly including this .pst file is more easy then excluding all others. OsaSync default is to exclude the selected folders and this can be changed by setting a checkmark on the advanced options page to include instead of to exclude folders.

solved errors/problems:

Error# 13 in proc: clsFolder.IsFldRenamed. Type mismatch

A change to a distribution list marked as private in a synced folder could get OsaSync in an endless loop. The CPU usage for Outlook would become high and the osasync logfile would become very large.

An email being resend could lead to the creation of an email with an identical osasync ID as the first email.

New in version 5.3.9 (August 2, 2005)

solved errors/problems:

Folder renaming was not always successfully synced. The last bug fix in version 5.3.8 was not sufficient.

FTP: some FTP servers don't allow navigation the the root folder. OsaSync's ftp transfer mechanism has now been updated to prevent OsaSync from navigating to the root folder.

Error# 91 in proc: clsFolder.SetHiddenMsgValue. Object variable or With block variable not set.

Distribution lists marked as private in a synced folder could cause OsaSync to go into an endless loop

New in version 5.3.8 (July 25, 2005)

solved errors/problems:

FTP transfer of un-zipped files: if on the ftp server there was only the file 000001.txt this file could become overwritten the next time when OsaSync transferred files with the ftp server. This could lead to lose of sync data.

Folder renaming was not always successfully synced.

Folder becoming unsynced: If more then 15 items were selected and moved to another folder then OsaSync could evaluate this event erroneously as the copying of the folder and OsaSync marks a copied folder always as being unsynced. This has been solved by implementing a more robust mechanism for detecting the moving and/or copying of outlook folders.

New in version 5.3.6 (July 13, 2005)

solved errors/problems:

Error# 91 in proc: clsFldMon.SetFldToBeMonitored.

Error# -196609 in proc: clsFldDelItmsWrap.GetChangedItmsAfterErr.

Error# 91 in proc: clsFoldermonitor.SyncFldInitOnThis. Could happen when all top level folders are excluded for osasync.

Error# 438 in proc: clsFoldermonitor.pmsgMoveItem. Happened when a contact item was moved from one folder to another.

Advanced mode syncing: folders were not marked for syncing on the target computers.

New in version 5.3.4 (June 29, 2005)

solved errors/problems:

Error# 91 in proc: clsFolderMonitor.CreateWrapperForFld. Could happen when an Outlook 2003 search folder was selected.

Error# 91 in proc: clsProtocolProc.MoveLocalMsgsToLANServer. Happened when there were no computers configured yet with the OsaSync connection wizard.

Error# 1245708559 in proc: clsFolderMonitor.CreateFldWrappersInit. The operation failed. If a .pst file could not be opened by Outlook.

clsAppProc.SetPropsInNamedProps: error# 28 Out of stack space. This error could happen if the subject of an appointment or task contains the character '['

New in version 5.3.3 (June 27, 2005)

solved errors/problems:

When syncing recurrent appointments it could happen that the recurrencetype was not always synced correctly. This resulted in monthly recurrent appointments showing as recurring weekly.

New in version 5.3.2 (June 23, 2005)

solved errors/problems:

Error# 281 in proc: clsFldDelItmsWrap.GetChangedItems. IMAPITable::Restrict() returned MAPI_E_EXTENDED_ERROR

Error# 91 in proc: clsExplorer.EnableFldButtons. Object variable or With block variable not set

Error# 483970100 in proc: clsFldDelItmsWrap.GetChangedItems. The requested resource was not found

A small bug in the conversion process could have resulted in an incomplete conversion of Calendar items when you previously synced the calendar with exclusion of past appointments. If so you can prevent problems by resyncing the calendar folder.

Syncing of recurrent appointments: if the start- and/or end time of the recurrence was not set this could result in a synced appointment with a different recurrence type

New in version 5.3 (June 18, 2005)

important:
When you start this new version for the first time then OsaSync will run a CONVERSION process . OsaSync now uses a new mechanism for detecting changes (see below) and in order to be able to work with this new mechanism OsaSync will copy all properties of contacts, appointments and tasks to hidden properties. This conversion can take some time depending on the number of synced folders and the speed of your computer.
If you have folders with many items (more then 1000) we recommend archiving your folders before you install version 5.3 (Outlook menu: File - Archive....) Especially the Calendar folder can contain very much items if you have never archived before.

OsaSync will also create a computers configuration file that lists all your configured computers. This file will be created on the server in the OsaServer folder and is called CnfComputers.txt (in Peer-to-Peer mode this file is created in the \OsaSync\Data folder). For each computer a computer ID is created and OsaSync will rename some OsaSync Windows registry keys and the OsaSync local folders (in Client/Server mode) from computer name to computer ID.

new functions:

Most work has been spent in changing an architectural aspect of OsaSync. OsaSync used to depend heavily on Outlook events in order to find out what was changed by the user. This event driven model has been abandoned and is now replaced by another mechanism: OsaSync now stores the existing state of each item in invisible properties and compares the old properties to the new properties in order to find out what has changed. This mechanism makes the change detection more robust then the previous event-driven mechanism. We expect this mechanism to be so robust that it will become very unlikely to detect changes during a folder compare process. If so, we intend to remove the compare mechanism altogether from OsaSync in a future version.

A Duplicate Items Remover (accessible via the exceptional procedures tab on the OsaSync advanced options window). If you have folders with duplicate items then you can have them removed by OsaSync to a subfolder called OsaSync_Duplicate_Items.

Syncing of the follow-up flag for contact items.

Syncing of the email follow-up flag and flag color.

Syncing of changed emails (an email can be edited and saved).

Contacts, Appointments and Tasks can be marked unread by OsaSync when they are imported or changed by OsaSync (setting on the OsaSync advanced options page; items tab). When changed items are marked unread it's possible to see at a glance with items have been changed by others. Use a table view to see the unread items.

Outlook will now start much faster then it did with the previous OsaSync version. OsaSync initialization used to block Outlook from being responsive. This has been changed so that the initialization will now take place in the background so that Outlook is responsive. During this initialization period the major OsaSync functions (like checking for changes on other computers) are not yet available and are greyed-out until initialization is ready.

You can now choose to synchronize private appointments as Busy. If so then an appointment set as private (checkbox in the lower right corner of the appointments window) will show on the synced computers only with the start- and end time and the subject Busy. Another user can only change the start- and or end time of such an appointment (so that your secretary can reschedule your private appointment).

OsaSync has become independent of computer names so it is now very easy to change a computer name: it's enough to set the new name in the CnfComputers.txt file. OsaSync (in Client Server mode) will then rename the folders on server. It is now also very easy to remove a computer from the OsaSync configuration: removing the corresponding line from the CnfComputer.txt file is enough. OsaSync will then delete all relevant folders.

solved errors/problems:

Error# 91 in proc: clsContactImp.AskIfCreateNewCnt. Object variable or With block variable not set

Error# 438 in proc: clsDLproc.RemoveMemberFromDL. Object doesn't support this property or method

Several other bug fixes and tweaks

New in version 5.2.3 (February 15, 2005)

solved errors/problems:

error# 52 in clsRemdataprocessor.CompDataEnd. This error is caused by a Windows security update KB885250.

New in version 5.2.2 (January 19, 2005)

In certain scenarios running a compare process with 3 or more computers could result in messages about items with OsaSync ID's already present.

The FTP wizard will now create the 'OsaServer' folder instead of the 'OsaSync' folder on the FTP server.

When the OsaSync connection wizard was run and canceled before ending then a few settings were saved.

New in version 5.2.1 (January 11, 2005)

solved errors/problems:

When updating multiple tasks in simple list view if was in certain scenarios possible that OsaSync didn't detect all changes thereby causing some tasks to become out-of-sync.

New in version 5.2 (December 30)

new functions:

OsaSync now also supports the French, German, Italian and Spanish languages. OsaSync adapts the Outlook language if it's one of these languages.

FTP errors can be ignored by clicking a checkbox on the FTP options window. FTP errors can sometimes occur but are in most cases temporary; the next time OsaSync connect to the FTP server this is likely to be without errors so these errors can often be ignored.

solved errors/problems:

Error# 6 in proc: clsFolder.moOlItems_ItemChange. Overflow

New in version 5.1.2 (December 6)

solved errors/problems:

If the 'prepare folders for synchronization' wizard was run in advanced mode and a computer was added to the list of synced computers (so the folder was already synced) this caused problems because OsaSync recreated the OsaSync ID's of all items in the folder. This caused the folder to become out-of-sync with the computers on which the folder was already synced.

Error# 517750789 in proc: clsAppImp.CheckAppExceptions. This error could occur during the compare process when OsaSync detected that an instance of a recurrent appointment was deleted on the other computer but not on this computer.

New in version 5.1.1 (November 26)

solved errors/problems:

Error# 91 in proc: ctlFTPfolders.SetCaptions. Could happen when the connection wizard was started from the OsaSync options page

Error# 91 in proc: clsExplorer.ToggleMenuButtons

Several customers expressed there confusion with regards to the OsaSync licence key and the subscription key. In order to make this subject more simple we stop working with a separate subscription key and add the subscription date to the regular OsaSync licence key. From now it doesn't matter if you buy your initial licence; if you extend your licence or if you renew your subscription. In all cases you receive the same licence key. If you reinstall OsaSync you now only need to paste the last licence key you received from us, so there's no need anymore to paste a separate subscription key.

New in version 5.1 (November 22)

new functions:

FTP file transfer can now be ZIPPED and encrypted. By zipping all files before sending them to the FTP server the transfer process becomes much faster. Zip files are encrypted with a strong encryption key in order to make the FTP file transfer very secure. Zipped files can only be unzipped when the same password has been set on all computers.
The FTP options window has been extended with a 'zipping and encryption' tab on which zipping can be enabled and a password can be set.
In order to use this new zipping and encryption feature you will need a licensed copy of Winzip 9.0 or higher. You also need to download and install a command line support add-on for Winzip. The OsaSync FTP options window will take you directly to the Winzip download pages.

During the connection wizard a prefix can be set to be used by all other computers during the import of appointments or tasks. A choice can be made on the appointments tab of the advanced options page whether you want OsaSync to use prefixes that are assigned by you or if you want to use the prefix as it has been set by the other computer.

The OsaSync registration window now has only one input box for licence keys. There was some confusion about which code (or key) had to be pasted in which input box. We start using the term 'licence key' for each encrypted code you receive from us regardless if the code is for a subscription renewal or for a new OsaSync licence.
We also dropped the term 'upgrade' because it was used ambiguous in OsaSync. 'Check for updates on other computers' has been changed to 'check for changes on other computers'. 'Upgrade licence' has been changed to 'Extend licence' and 'Upgrade OsaSync' is now only used to get a new OsaSync version.

solved errors/problems:

In a certain scenario a new contact could be created twice on the other computers.

Tasks in a table view: if a task item was marked complete without the task having been selected prior to clicking the complete box then this change could be missed by OsaSync.

Several other errors.

New in version 5.0 (October 25)

new functions:

Distribution lists are supported and can now be synced. Resynchronize your contacts folders that contain distribution lists to start the synchronization of the distribution lists (by running the prepare folders for synchronization wizard again).

When a folder is synchronized it is not necessary anymore to manually merge items from other computers into the 'source' folder. OsaSync will do merging. This was already the case for email folders and is now also working for contacts, appointments, tasks and notes folders.

A compare data expiration date can now be set on the OsaSync advanced options window. If compare data is created and the other computer comes back online when the expiration date has expired then the compare data will not be processed but will be deleted. Older compare data is not so useful anymore because several new changes can have been made since the compare data was created. This expiration date now defaults to 7 days.

Compare data can now be created for a selected range of computers. The OsaSync menu has been enhanced with the option Create compare data for this folder with selected computers.

It is now possible to sync a folder that is already synced with an extra computer from the OsaSync tab on the folder properties window (right-click on a folder and choosing properties).

The prepare folders for synchronization wizard has a new option to synchronize folders in enhanced mode. Using enhanced mode it is possible to sync several large folders much faster then when using normal mode. Enhanced mode however requires manual copying of the .pst file(s) so this mode can only be used when your Outlook and OsaSync setup enables the initial use of the same .pst file.

For appointments and tasks prefixes can now be used in order to see instantly who has created and/or updated the item. E.g. an appointment with the subject 'Coffee with Ron' will show as '[PvdG] Coffee with Ron'. Prefixes are set on the OsaSync advanced options page. When you (re-)sync an appointment or task folder, the wizard will ask if you want to use prefixes.

New layout of the OsaSync advanced options page: a tabbed dialog with three tabs is used in order to present options more structured.

Excluding top level folders for OsaSync can now be done by simply selecting folders from a list instead of having to type folder names.

An option has been added on the advanced options page to start OsaSync in Local Mode and not try to connect to the LAN server,

If you change the birthday or anniversary of a contact then Outlook does not update the corresponding appointment in the calendar. OsaSync will now take care of this.

solved errors/problems:

If the default contacts and calendar folder are synced and you added a birthday or anniversary to a contact then this could result in duplicate appointments in the calendar on the synced computers.

An email flagged complete can now by synced. In previous OsaSync versions syncing of flagged complete messages resulted in the error 'unsend messages cannot be flagged complete'

The progress windows shown by OsaSync used to get the focus. The active window would loose it's focus thereby interrupting your work. Progress windows don't get focus anymore in this version.

Appointments and tasks now sync there changes immediately when the item is saved; not when the item becomes unselected like OsaSync used to do before.

Dismissing or snoozing an appointment or task does not result in an update on the other computers anymore.

Working with meeting requests does not create duplicate appointments anymore like it used to do in previous versions.

Overall handling of appointments and tasks has improved, resulting in a more secure and robust syncing experience.

If a new contact is created and closed without saving OsaSync does not create update files anymore.

Several other tweaks

New in version 4.3.3 (July 22)

solved errors/problems:

FTP: it was not possible to increment the FTP timeout setting on the FTP options page before the connection wizard had run so the connection wizard could not connect to a FTP server that needed a timeout period longer then 10 seconds.

New in version 4.3.2 (June 22)

solved errors/problems:

OsaSync Client-Server mode: when OsaSync was running on a computer configured as the OsaSync server and a network connection was not possible this could result in OsaSync not correctly being aware of all configured computers. In this case the OsaSync options window did not list all previous configured computers. That in turn could result in folders getting out-of-sync because OsaSync didn't create update data for those computers not 'seen'.

FTP: when a computer configured for connecting via FTP only is unable to connect to the FTP server this could cause OsaSync to go into a loop for about 1 minute causing Outlook to appear to hang.

Read-Only folders: if while running the synchronization wizard a folder was configured Read-Only on some but not on all computers then it was possible that the configuration of Read-Only computers did not succeed completely.

Read-Only folders: if an item is added in a Read-Only folder OsaSync will show a message and delete the item.

OsaSync by default sets the OsaSyncNew or OsaSyncChanged category when an item is imported after being updated on another computer. Some users indicated there dislike of this feature so it is now optional: you can disable the use of these categories on the OsaSync advanced options page.

If Outlook is connected to an Exchange server OsaSync will by default ignore the top level folder 'Public Folders'. This makes it possible to sync folders from the users mailbox although these mailboxes (there top level folder names) are different on each users machine. Note: this is only possible when there are no other top level folders other then the public folders and the users mailbox.

New in version 4.3.1 (June 14)

solved errors/problems:

OsaSync Client-Server mode: when OsaSync was running on a computer configured as the OsaSync server and a network connection was not possible this could result in OsaSync not correctly being aware of all configured computers. In this case the OsaSync options window did not list all previous configured computers. That in turn could result in folders getting out-of-sync because OsaSync didn't create update data for those computers not 'seen'.

FTP: when a computer configured for connecting via FTP-only is unable to connect to the FTP server this could cause OsaSync to go into a loop for about 1 minute causing Outlook to appear to hang.

New in version 4.3 (June 7)

new functions:

Creation of compare data for mail folders runs much faster.

Compare: It's now also possible to create compare data for a selected folder and all it's subfolders. This process will also detect if there is a folder that's synced on this computer while it's not synced on the other computer or vice versa.

Moving, copying or deleting a selection of more then 15 items at once (a bulk) has become more solid. If two or more bulk operations were performed fast after one another OsaSync could 'miss' one of these bulk operations.

FTP: when Outlook starts OsaSync tries to connect to the FTP server for 10 seconds. If the connection has not been established within 10 seconds a time-out occurs in order to prevent Outlook from starting to slow. For some configurations this time-out period can be too short. You can now set the number of seconds on the FTP options window for this time-out.

FTP: if you connect to a computer that's been configured for connecting both via the LAN and via FTP it's now possible force OsaSync to change the connection on the FTP options window from LAN to FTP or vice versa. You might want to do this if you have reconnected your laptop to the LAN while OsaSync still wants to connect via FTP (in case something went wrong; normally OsaSync detects a reconnection to the LAN and switches back from FTP to LAN automatically).

FTP: It is now possible to configure FTP files transfer from behind a firewall by specifying several firewall settings on the ftp options window.

OsaSync will now mark an item when it imports its changes from another computer as being new or changed. OsaSync adds the category "OsaSyncNew" when it's a new item and "OsaSyncChanged" when it's a change to an existing item. This enables you to quickly see which items have been added or changed by OsaSync by applying a view with the category field. If an item marked with "OsaSyncNew" or "OsaSyncChanged" is changed by you the marker will disappear on your computer and appear on the other computers after this change has been imported on those computers.
When you remove the "OsaSyncNew" or "OsaSyncChanged" category when you are finished reviewing the updates, it will not be recognized as a change, so nothing will happen on the other computers.

OsaSync Options can be password protected. If you want to prevent an inexperienced user from changing OsaSync options you can check the box 'Enable password protection for OsaSync options' on the OsaSync advanced options window. You will have to specify a password which will be asked for whenever an option is changed (except for options concerning the display of progress windows and the enabling of extended logging).

Compare process options have been arranged more clearly on three tabbed dialogs on the compare options window.

solved errors/problems:

When comparing e-mail folders is was possible that e-mail became duplicated.

Error# 13 in clsProtocolProc.GetHighestTxTSeqNr or in clsProtocolProc.CreateFileName: type mismatch.

Error# 91 in proc: clsFldMon.SetItemsAddedAction. Object variable or With block variable not set. This could happen if an email was moved back into the inbox.

Error# 196695 in proc: clsFolderMonitor.FindItemInFolder. This error occured when comparing an empty email folder.

New in version 4.2 (May 7)

new functions:

When OsaSync is in local mode because the LAN server is unavailable it will now automatically try to connect again to the server and resume normal mode. Whether OsaSync automatically tries to reconnect or not is settable on the OsaSync advanced options page. Outlook can appear frozen for several seconds when OsaSync unsuccessfully tries to establish a connection to the server.

Peer-to-peer mode: when a computer is not available OsaSync shows a message. You can now indicate that you don't want to see these messages anymore.

You can set the default option to always have OsaSync delete duplicate e-mails. This is set on the OsaSync advanced options page or on the window which is shown after a duplicate e-mail has been detected by OsaSync.

In order to detect duplicate e-mails OsaSync now checks the internet message ID. This ID is unique for each e-mail.

The optional progress windows shown when OsaSync imports updates from other computers and when OsaSync transfers files with the FTP server can now be displayed minimized in the Windows taskbar so the popping up of the progress windows doesn't interrupt anymore.

solved errors/problems:

Error# 91 in clsFldMon.SetItemsAddedAction. Object variable or With block variable not set. Could happen when an email is moved to the Junk E-mail folder.

If an e-mail was moved back into the Inbox folder this was not recognized by OsaSync so this would not happen on the synced computers.

When a meeting request was created this would result in duplicate meeting request on synced computers.

Duplicate birthdays or anniversaries could be created in the Calendar when the Contacts folder was compared and contains contacts with the birthday or anniversary set.

If two identical e-mails arrived in the Inbox then OsaSync would prompt you with the 'duplicate e-mail detected' dialog twice and delete the e-mail twice if chosen. This has now been corrected; you will now be prompted once.

OsaSync also checked for duplicate items in non-synced folders.

OsaSync sometimes wrote temporary data into the OsaSync application installation folder. This resulted in errors when the user doesn't have write/modify access rights in this folder. Temporary data is now written in the system TEMP folder (Note: the user should still have create-, write-, modify access rights in the OsaSync\LOG folder).

New in version 4.1.4 (March 12)

solved errors/problems:

After installation of Office XP SP3 the Outlook security dialog was triggered when a contact item or an appointment was selected. This version doesn't trigger this warning anymore.

Error# 6 in proc: clsFolder.moOlItems_ItemChange. Overflow

The compare process can now be run when the folder is empty (in order to see if the other computers do have items in the folder)

error# 91 in clsFtpTransfer.SetReady. This error could occur if the FTP process had to reconnect to the FTP server during the files transfer.

New in version 4.1 (February 27 2004)

new functions:

Extensive checks have been added to make sure no DUPLICATE OsaSync ID's can exists in the same folder. Warnings have also been added in case an item is added to a folder and OsaSync sees that this item is already in the folder. You will have to explicitly allow the adding of duplicate items or choose to have them deleted by OsaSync. OsaSync recognizes an item as being the same if the following properties are the same:
- Contact: full name; company name and email address
- Appointment: start time; end time; location and subject
- Task: start date; due date; status and subject
- E-mail: sender name; date/time email was sent and subject

If OsaSync goes into Local mode because the server is not available it is now possible to check for changes and have OsaSync come out of local mode if the server is up again.

When OsaSync is importing updates from other computers it now shows a progress window. Whether you want to see this window or not every time OsaSync processes update files can be set on the OsaSync options page.
We recommend to keep this window visible and to limit your changes in synced folders during the time this window is visible. During the time OsaSync is processing updates it is possible OsaSync misses a manual change made by you (e.g. you move an email from or to a synced folder) so it's best to wait until OsaSync has finished processing the update files.

If it's necessary to remove OsaSync ID's from a folder you can now select this folder instead of having to remove ID's from all folders.

By default if you move an item from a synced folder to a non-synced folder, OsaSync will also move this item on the synced computers and create the non-synced folder if necessary. You can now change this behavior to items becoming deleted on the synced computers instead of being moved by a setting on the OsaSync advanced options page.

If an item is deleted on another computer from a synced folder it will also be deleted on your computer. This happens by default without notification. You can now have OsaSync ask you for confirmation before it deletes an item. You can do this for each item type on the OsaSync advanced options page.

It's now possible to specify an alternative port number for syncing via the FTP server.

solved errors/problems:

Several issues related to syncing via the FTP server

Error when deleting an appointment

When OsaSync was looking in a folder if an item (or item ID) is already present this could take some time especially in folders with a large number of items. The speed of this lookup process has now been increased dramatically.

Several other errors

New in version 4.0.2 (November 28)

solved errors/problems:

OsaSync connection wizard while trying to configure an FTP server:
Some FTP servers return there information in a slightly different way then other servers. This resulted in OsaSync not being able to 'see' the folders on the FTP server.

The compare process for Tasks and Calendar folders could 'miss' existing differences between items so these differences where not corrected.

The notes field of Tasks and Appointments could loose it's formatting.

An update to the Contacts notes field was sometimes not synced. This could happen if the notes update was the only update to the Contact.

Creation of synchronization data has been changed in order to prevent Outlook from freezing during the 'prepare folders for syncing' process.

If 3 or more computers are synced an extra check is added to make sure all computers are marked for syncing with each other correctly.

Small but nasty bug that could result in updates being 'missed' by OsaSync.

New in version 4.0 (November 21)

new functions:

Syncing computers over the internet via a FTP server is now possible.
- When you are traveling with your laptop you can stay synced whenever you can connect your laptop to the internet.
- When your company has more office locations you can now keep all your computers synced regardless of there location.
For more info see the FAQ page
- Can OsaSync sync files via a FTP server on the internet?
- How to configure OsaSync for syncing via the FTP server?

If you are running OsaSync in Client-Server mode it is now possible to use OsaSync with multiple users on the SAME computer. See My wife also works on my computer, can we both use OsaSync? on the OsaSync FAQ page for details

The default value for running the compare process has been set to NOT run automatically. The previous default setting was: run every 7 days.

solved errors/problems:

In some scenario's duplicates contacts or emails could be created. Before OsaSync imports an item it will now first check if the item is not yet there. For Contacts OsaSync will use the full name, company name and email address to see if the Contact is already present. Appointments are matched on start date, end date, location and subject. Emails on sender email address, subject and send-on date. If the folder already contains the item then OsaSync will not import the item again but only match the OsaSync ID (= the 'vaSCid' field)

Extra checks are also added to make sure no items can be imported with the same OsaSync ID

If a new Contact was created and it was marked Private while 'do not sync private items' was set on the OsaSync Advanced options page the contact was still synced.

In some scenario's not all User-Defined Fields on a custom Contacts form were synced correctly. Some fields could be missed.

Error# -271 in proc: clsFolder.moOlItems_ItemAdd. Automation error. This could happen when an anti-spam application like Norton Anti-Spam moved an email from the inbox to the spam folder.

When OsaSync was ready with comparing data received from other computers, the timer to automatically check for changes on other computers was not enabled again. No updates were processed until the next restart of Outlook or until 'check for changes' was clicked in the OsaSync menu.

When you run the 'prepare folder for syncing' process or create compare data the corresponding computers will postpone importing this data before all data has been received. This prevents the scenario that the importing computer could import data faster then the source computer could generate the data and therefore end up with incomplete data.

several other minor enhancements.

New in version 3.4.3 (August 28)

solved errors/problems:

OsaSync now also 'catches' updates to Contact categories made by moving a contact in a view by category. This was previously not recognized so this update wasn't synced to the other computers.

Error# 0 or 91 in proc: clsCreateCmpData.CreateNextFile. Could occur when compare data was created for a Calendar folder.

Error# 13 in proc: clsAppProcessor.pmsgImportMsgFile. Type mismatch. Occured when an appointment or task was imported during the compare folders process.

New in version 3.4.2 (August 15)

solved errors/problems:

error# 91, Object variable or With block variable not set. Procedure: clsFldMon.Process2FldsChanged. This error could occur when monitoring e-mail folders was not set.

New in version 3.4.1 (August 13)

solved errors/problems:

error# 91, Object variable not set or error# 424, Object required in proc: clsFoldermonitor.pmsgMoveOrCopyFolder

In some scenario's moving a folder could be 'missed' by OsaSync resulting in the folder not being moved on the synced computers. Improvements have been made to reduce this chance.

Error# 91 in proc: clsFldDelItmsWrap.moDeletedItems_ItemAdd. Object variable or With block variable not set. Happened when there were no synced folders yet.

This update includes a small utility called OsaMonitoring that checks every minute if OsaSync is still running and warns if this is not the case. See the FAQ What is OsaMonitoring for details.

The way OsaSync processes update files on other computer has been improved. It will now be possible to continue working when a large number of files is being processed. This improvement also strongly reduces the chance of Outlook freezing or running out of memory during the import of synchronization data for folders with many items.

New in version 3.4 (August 4)

new functions:

Enhancements to the folder comparing process:

The possibility to compare e-mail folders.
There are two major differences in the way OsaSync compares e-mail folders with the way other folders are compared:
1). OsaSync only checks if the same e-mails exist in the folder on both computers but it doesn't compare the properties of the individual e-mails (like sender name, subject and so on).
2). OsaSync doesn't receive all e-mails to be compared but only the e-mail headers. If an e-mail is not found on the current computer and you choose 'Update this computer' then OsaSync will ask the other computer for this e-mail. The other computer will see this request the next time it processes the 'check for changes on other computers' and will respond by copying the e-mail. This means that some time will elapse before the e-mail will be visible on the current computer.

All options related to folder comparing are moved to a separate window 'Compare folder options'. This window is accessible during the compare process.

New option for the compare process: 'update the property on this computer if it hasn't changed since the last compare run'. OsaSync will automatically apply the properties of the item on the OTHER computer by updating the item on THIS computer if:
a) the item has been changed on the OTHER computer on a later time then on the current computer AND
b) the item on the CURRENT computer hasn't been changed since the last time when the folder was compared.
In this case it is certain that the differences are caused by a change on the OTHER computer.

It is now REALLY possible to continue working while OsaSync is creating compare data or when it is processing compare data received from another computer. Comparing takes place in the background and doesn't block Outlook as it used to do in previous versions.

If the comparing process detects a difference and prompts you with a window to make a choice it is now still possible to access Outlook and continue working. Previously you had to close this window in order to be able to do anything else in Outlook.

solved errors/problems:

The FileAs field for contacts could be different on the destination computers as on the source computer after synchronization. This resulted in a different listing of the contact items when the contact view is sorted on the FileAs field.

error# 91: in proc: clsExplorer.moOLExpl_FolderSwitch, Object variable or With block variable not set. Happened when selecting the 'My Documents' or 'My Computer' icon in the Outlook bar.

Error# 91 in proc: clsFldDelItmsWrap.moDeletedItems_ItemAdd. Object variable or With block variable not set. Happened when deleting an e-mail while monitoring e-mail was not set on the OsaSync options page.

Problem during first time synchronization with more then one other computers:
When there are no folders already synced and the first time a folder is synced to more then one computer then this folder is not marked on the other computers as being synced with all other computers. So if you sync a folder on computer A with computer B and C then B doesn't mark this folder as being synced with C and C doesn't mark it as synced with B. This error doesn't occur when there is at least one folder already synced when the 'prepare folders for synchronization' is started.

New in version 3.3.1 (June 27)

solved errors/problems:

Error# 6 in proc: clsManager.GetRemoteData. Overflow.

Error# 424 in proc: AddinGlobals:CleanUpGlobals. Object required. Could occur if a contact inspector window remained open for some time.

Error#: 424: Procedure: AddinGlobals:CleanUpGlobals. Object Required. Occurred when Outlooks closes and there are no synchronized folders.

New in version 3.3 (June 26)

In this Upgrade OsaSync will run a one time only conversion process. Starting Outlook can take a few minutes because of this process.
=> July 31: Due to a small error in the conversion process OsaSync will create data files for all items in a PDA enabled folder after the first time OsaSync has checked for updates on other computers (manually from the menu or automatically). This results in the other computer appearing to freeze when it is processing all files generated on the other computer.
This happens only once, just wait till all files are processed. This small error is corrected in version 3.4

new functions:

Enhanced PDA/cell phone support:
OsaSync will now automatically recognize all changes made on your PDA while you sync with the PDA and copy them to all other computers. All items new, updated or deleted on your PDA will be added, updated or deleted on the computers synced with OsaSync. The manual procedure 'Copy PDA changes' has become obsolete.
Read more about this new PDA support and how to enable OsaSync for PDA support on the FAQ page.

When OsaSync is comparing contacts and finds a difference it is now possible to see all contact properties for both contacts in one window. This makes it more easy to see what has been changed and to choose which property has to be used.

solved errors/problems:

If Word has been selected as the default e-mail editor this will now also work when a reply or forward message is composed.

Imported e-mails were always imported as being read. The checkbox 'Do NOT mark imported e-mails as being read' on the advanced options page didn't work.

If an email in the Outbox was edited again the email wasn't sent on the next scheduled send/receive action but remained in the Outbox.

If an email was saved as a Draft and send on a later time then the email was not always deleted from the Drafts folder on the synced computers.

Working with custom forms could lead to creation of one-off items because OsaSync was using some user defined fields other then the 'vaSCid' field. These other user defined fields have been removed so if you are working with a custom form and you have added the 'vaSCid' field to this form then one-off items will not be created anymore.

New in version 3.2.1 (June 11)

solved errors/problems:

Error# 53 in proc: clsContactProcessor.ImportBody. File not found

New in version 3.2 (May 22)

new functions

OsaSync now supports the synchronization of appointment color labels. Note: Outlook 2000 doesn't support appointment color labeling.

If OsaSync runs in Local Mode it will display 'OsaSync - LM' in the Outlook menu. OsaSync runs in Local Mode when OsaSync has been configured in Client-Server mode and when the server is not available (e.g.: when you travel with your laptop). In Local Mode it is not possible to synchronize or compare folders.

You can now create a new contact by copying and pasting an existing contact into the same folder and then change only certain properties like the contacts name. OsaSync now recognizes this and assigns a new unique contact ID (= the 'vaSCid' field) to the copied contact.

The Advanced Options window now adds the possibility to specify the name of a top level folder to be excluded by OsaSync. When OsaSync starts it iterates all folders in all top level folders. Some top level folders like 'WinFax Fax Logs' produce errors when OsaSync reads it's contents. Other folders that can produce problems are HTTP mailboxes like hotmail. An excluded folder will not cause problems but its sub folders cannot be synced anymore.

While syncing contacts the contact notes field now retains formatting with bold. italic, colors etc. Formatting was lost in previous versions.

If the same contact notes field is updated on two disconnected computers OsaSync will now recognize this and prompt you to ask which update you want to use. You can also choose to append the update from the other computer to the existing notes field which enables you to merge the changes manually.

If OsaSync is setup in Client-Server mode then the 'check for changes on other computers' time can now be set to a minimum of 1 minute (this used to be 5 minutes).

When a calendar folder is synced OsaSync now by default does not sync appointments in the past. The 'prepare folders for synchronization wizard' however allows you to overrule this and sync the complete calendar. This is not recommended because importing the calendar data on the other computers can take a long time.

solved errors/problems:

If an appointment or task was opened from Outlook - Today and then deleted this appointment or task was not also deleted on the other computers.

If an new appointment was discarded (closing it without saving), an new empty appointment was created.

If two instances of Outlook were started this could result in an error when one instance was being closed.

In some scenario's copying or moving an item could be missed by OsaSync. Copying and moving items has been improved so items will also be copied or moved on the other computers.

When OsaSync imports sync data for a folder already synced, OsaSync asks if you want to delete the items in the folder before starting the import in order to prevent duplicates. If you answered yes then not all items were deleted due to a bug so this could result in the creation of duplicates.

New in version 3.1 (April 28)

new functions

New folder synchronization wizard. This wizard takes you step by step through the prepare folders for synchronization process. See the updated Getting Started page for details.

A folder can now be marked as Read-Only on a target computer during the synchronization process. In this way syncing works one-way only: from the source to the target computer. The user on the target computer can only view the contents of the folder but not make any changes.

The new synchronization wizard syncs one folder at a time but experienced users can change this to multiple folders at once by checking a box on the OsaSync advanced options page.
Note: this is not recommended.

solved errors/problems:

Error# 91 in procedure ClsApp.Appitem: Object variable or With block variable not set. Could happen on right-clicking the Calendar folder

Error# 234 in proc: clsComputer.ReadFromRegistry. Error calling API function. This error occurred when Outlook was started while there are very much contact folders synced.

Error# 438 in proc: clsContactProcessor.CompareCntProperties. Object doesn't support this property or method

When working with more then one top level folder (= more .pst files) the deletion of items and folders on the synced computers did ONLY WORK IN ONE TOP LEVEL FOLDER. Items or folders being deleted in one of the other .pst files did NOT get deleted on the synced computers. This has been solved so now all items and folders in all .pst files will be deleted on the other computers as well.

Syncing subfolders of a folder that had been assigned an alternative folder name on the other computers was not handled correctly.

New in version 3.0.3 (April 10)

new functions

The 'Prepare folders for synchronization' process can now be disabled by setting a checkmark on the advanced options page. Disabling this process can prevent a user from accidentally syncing a folder again if the folder syncing preparation process has already run.

solved errors/problems:

Error# -57335 in procedure: clsMail.CreateID. This happens with a Hotmail account (or other HTTP account) when selecting more than one message using either the "Shift" or "Ctrl" key.

The licence key for a 10 user licence did not work.

If the property 'Contact found on other computer' on the advanced options page was checked it was not checked anymore on the next startup.

New in version 3.0.2 (April 2)

solved errors/problems:

When comparing contacts OsaSync could prompt you saying that a contact had a business address on one computer and not on the other computer while this is not the true; the contact doesn't have a business address on both computers.

New in version 3.0.1 (March 26)

solved errors/problems

Error# 438 in proc: clsManager.moInspectors_NewInspector. Object doesn't support this property or method. This error occurred when opening a task with OsaSync extended logging enabled.

Error# 91 in proc: clsFolderMonitor.ProcessFldAdd. Object variable or With block variable not set. Could happen when a new folder is created in a synced folder

When OsaSync is installed in C/S mode while there is no connection to the server, OsaSync still tried to access the server causing Outlook to slow down or freeze.

Error# 424 in proc: clsExplorer.DisableMenu. Object required

If you are working with 2 top level folders (= 2 .pst files) and both folders have an inbox folder the syncing of emails in the inbox was not accurate; emails synced from the inbox on one machine did end up in the inbox in the wrong .pst file on the other machine.

If a new contact was created while the selected folder was not a contacts folder and the contact was moved into a synced folder from the inspector menu 'File - Move to folder', this new contact was not synced.

New in version 3.0 (March 7)

new functions

Possibility to configure OsaSync in Client-Server mode. Read here more on C/S and the advantages compared to the current Peer-to-Peer mode.

When resyncing a folder OsaSync now asks if it can delete all existing items in the folder prior to importing the new sync data so it is not necessary to do this manually anymore.

solved errors/problems:

Error# 438 in procedure: clsManager.moInspectors_NewInspector. This happened only when extended logging was enabled and an occurrence of a recurrent appointment was opened.

New in version 2.5.2 (March 2)

solved errors/problems:

Error# 76 in procedure: ctlSharingType.AllowNextStep. Path not found. Occurred when running the connection wizard.

New in version 2.5.1 (February 27)

solved errors/problems:

Error# 9 in proc: clsFldMon.CreateDataForFlds. Subscript out of range. This happened when there was no folder synced yet of an Outlook item type monitored by OsaSync.

Error# 234 in proc: clsComputer.ReadFromRegistry. Error calling API function. Could happen when a large number of folders were synced.

In some (exceptional) scenario's a deleted appointment was not deleted on the other computers.

New in version 2.5 (February 20)

new functions; solved problem

The 'prepare folders for synchronization' process as well as the 'Create compare data' process has been revised in order to speed up the creation of data files when syncing or comparing with two or more other computers. When a large folder was synced with several other computers this process could run a long time and sometimes cause Outlook to freeze up.

Importing synchronization data files runs faster especially for calendar folders.

New in version 2.4.3 (February 13)

solved errors/problems:

Run time error 429: activex component can't create object. Occurs when trying to run the connection wizard.

New in version 2.4.2 (February 12)

Some applications like ActiveSync (for the PocketPc) initialize Outlook 'behind the screens'. If the Outlook process is already running in the background and you start Outlook manually OsaSync would not start. This update adds a workaround for this.

Outlook becoming unstable and behaving strange on Windows XP. Examples of strange behavior:
The ESC or DEL key does not respond; the preview pane doesn't work; Outlook item edit windows cannot be closed; Run time error 91 when Outlook closes; Outlook doesn't want to restart; etc.

New in version 2.4 (February 7)

new functions

Copying calendar entries to another day (using drag & drop while holding CTRL) or another calendar folder is now possible.

solved errors/problems:

Error number 13 Procedure: clsInterface.AcceptOCXparams. This error could occur on clicking the 'synchronize this folder...' button on the OsaSync tab of a folder property page.

New in version 2.3.1 (February 4)

solved errors/problems:

Changes to a private contact, appointment or task were not updated on the other computers although 'Do NOT sync items marked as private' was not checked.

When a contacts address was cut and pasted into another address type (e.g. business address was deleted and home address created) the old address was not deleted on the other computers.

If more then one incoming e-mails were moved to another folder by an Outlook rule, OsaSync didn't move the same e-mails on the other computers accordingly.

In some cases a licence key related problem could occur resulting in error# 13 in clsManager.testlicence.

New in version 2.3 (January 31)

new functions

Syncing of contacts and appointments marked as 'private' has been made optional. In version 2.1 the feature has been added to NOT sync items marked as private. This has now been made optional depending on the setting 'Do NOT sync items marked as private' on the OsaSync advanced options window. By default private items ARE synced now.

The checkbox "Do NOT mark imported e-mails as being read" has been added to the OsaSync advanced options page. Checking this box imports all e-mails as unread. By default all e-mails are imported as being read.

solved errors/problems:

If Tasks were monitored by OsaSync while Appointments were not (checkboxes on the OsaSync options page); the compare process wrongly prompted for each task as not being found on the other computer.

Error nr: 9: GetAppItemAndFld: Subscript out of range. Occurred when syncing a contact without a location and subject.

Error nr: 234: Procedure: clsComputer.ReadFromRegistry. This error could occur on WinXP if a large number of e-mail folders was synced.

New in version 2.2 (January 23)

new functions

A new function has been added: 'Copy PDA changes for this folder' and 'Copy PDA changes for all folders'. You can use this function to quickly copy those items that have been changed by the PDA or cell phone syncing software to the other synced computers. The difference with the compare process is that copying the changes made by your PDA syncing software copies only those items that have been changed in the last x minutes while the compare process creates compare data for ALL items. Read more on the differences with comparing on the FAQ page.

solved errors/problems:

If an e-mail was saved in the Drafts folder using Word as an e-mail editor and sent later it remained in the Outbox.
Note: if you re-open the e-mail in the Drafts folder while you use Word as the email editor, Outlook changes the editor type to HTML editor so Word is not used.

When comparing e-mail folders OsaSync created compare data while this was not necessary, causing the compare process to run for a long time on large folders.

New in version 2.1.2 (January 18)

solved errors/problems:

Sent e-mails imported by OsaSync were not imported in the Sent Items folder but in the inbox.

error 131063 in clsMailproc.pmsgImportMsgfile: can't move the items.

New in version 2.1.1 (January 17)

solved errors/problems:

If in version 2.0 or 2.1 the option 'monitor e-mail folders' on the OsaSync options page was unchecked this could lead to several errors:
- A folder not being synced anymore.
- When comparing folders OsaSync prompted for the 'personal folders' folder as not found.

An e-mail imported by OsaSync was marked as unsent. All e-mails are now marked as having been sent unless it's a draft in the Drafts folder.

Imported e-mails were marked as unread. Now all e-mails imported by OsaSync are marked as having been read.

New in version 2.1 (January 13)

new functions

Contacts and appointments marked as 'private' (check box in the right corner of the contact edit window) are now NOT synced anymore. This makes it possible to exclude some items in a synchronized folder from being synced.

solved errors/problems:

If your regional settings have a dot as the date separator character OsaSync ran into trouble on updating the Birthday or Anniversary of a contact.

On changing a contacts email address the Outlook security warning was shown.

In some scenario's it was possible for deleted appointments not to be deleted also on the other synced computers.

If the synced email is in HTML format the email was not shown as a HTML message but showed the hyperlinks as text.

New in version 2.0 (January 9 2003)

new functions

E-mail syncing! Details: read the section on e-mail in the FAQ Does OsaSync PRO handle the other Outlook items in the same way as it does contacts?

The options window now has the setting 'Check when Outlook starts'. Selecting this will make OsaSync check for changes on other computers immediately when Outlook starts and not wait until the period set for checking has elapsed.

solved errors/problems:

A contact category could be duplicated on the other machine after assigning a new category to a group of selected contacts.

OsaSync did not reliably distinguish between the contact items Home and Business address fields.

For comments or suggestions about this site: techsupport@vaita.com