Upgrade OsaSync PRO to version 7.0.8
This download will update your installation of OsaSync PRO to the latest version 7.0.8.
Installation instructions
Installing the upgrade is very easy, it won't take more more than 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. -
- 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 7.0.8
| Outlook 2007 and 2010 | Outlook 2000, 2002 (=Outlook XP) and 2003 |
|---|---|
|
|
This latest version contains all previous upgrades so it is not necessary to install previous upgrades first!
OsaSync PRO Upgrades
New in version 7.0.8 (April 18, 2011)
solved problems:
- A changed folder name was not synced correctly and could result in an empty folder name
New in version 7.0.7 (January 11, 2011)
solved problems:
- Error 13 in proc: clsAppointment.CreateAppMsgData. Type mismatch
New in version 7.0.6 (December 29, 2010)
solved problems:
- Emails didn't sync if the email subject was longer then 150 characters
- Errors resulting from the use of a dot as seperator in the international date/time settings like in '2010.12.25'
New in version 7.0.5 (November 26, 2010) (for Outlook 2007/2010 only)
solved problems:
- Outlook 2010: the OsaSync tab in the Outlook ribbon was not displayed when a computer friendly name contained a singel quote like in "Ron's PC".
New in version 7.0.4 (September 20, 2010)
solved problems:
- Outlook 2010 Italian language version:
The OsaSync tab did not show in the Ribbon - Outlook 2000/2002/2003 version:
Error 'osasync languages could not be initialized, quitting' while trying to run the osasync connection wizard.
New in version 7.0.3 (May 25, 2010) (for Outlook 2007/2010 only)
solved problems:
- Outlook 2010:
The OsaSync tab still did not show in the Ribbon in the Dutch language version.
New in version 7.0.2 (May 21, 2010) (for Outlook 2007/2010 only)
Version 7.0.2 is released only for the Outlook 2007/2010 version of OsaSync.
solved problems:
- Outlook 2010:
If OsaSync was configured for syncing with only one other computer the OsaSync tab in the Outlook ribbon in Outlook 2010 would not be visible. Instead the following error during startup occurred: error# 91 in proc: clsMenuWrap.ResetBtnCaptions. Here is how the OsaSync tab in Outlook 2010 should look like:
If no other computer was configured yet a similar error would occur and the OsaSync tab was also invisible.
New in version 7.0.1 (February 22, 2010)
solved problems:
- If you have set the OsaSync option for private appointments to sync with the indication 'bussy' then sometimes appointment changes were not synced.
- Archiving: when a folder was archived osasync would 'see' all archived items as having been deleted and would create DELETE messages for all synced computers. Now osasync detects that archiving has happenend and does not create the DEL messages anymore.
New in version 7.0 (January 22, 2010)
Outlook 2003 users: please make sure to download the correct OsaSync version. Contrary to previous releases this is now the version that is suitable for Outlook 2000, 2002 and 2003.
new functions:
- Outlook 2010:
OsaSync 7.0 supports the new Ribbon interface in Outlook 2010. New in Outlook 2010 is that the Outlook main menu has been replaced by a Ribbon, similar to the Ribbon in Word 2007. The OsaSync menu now has also been replaced by an OsaSync tab in this new Ribbon. All OsaSync functions are now accessible through buttons on this OsaSync Ribbon tab. - Outlook 2007:
In Outlook 2007 the new Ribbon interface is used when a Contact, Appointment or other outlook item is opened in an inspector window. If sharing has been enabled in OsaSync then the inspector window now also has an OsaSync tab on the inspector Ribbon.
solved problems:
- OsaSync uses an extra mechanism to detect changes. Each hour all folders are processed in order to find out if anything has changed that was not previously 'seen'. An update to this detection mechanism ensures much faster processing of non-synced calendar, contacts or tasks folders.
- When a new outlook item was created and this item was assigned a NEW category then this new category would not be synced with the master category list on other computers. Because of this the category color of the synced item would not be correct
New in version 6.5.2 (October 30, 2009)
solved problems:
- Appointment syncing marked as busy. The bug fix in version 6.5.1. was not accurate. Sometimes the appointment set to private was deleted on the synced computers but not synced again with the 'busy' indication.
New in version 6.5.1 (October 20, 2009)
solved problems:
- Appointment syncing marked as busy. An existing synced appointment changed to private was not correctly synced if private appointments have to be synced with the 'busy' indicator (as set on the appointments tab in OsaSync advanced options). A private appointment changed to public was also not correctly synced if it was previously synced as 'busy'.
- Deleting a task in the Outlook To-Do Bar always
triggers the following message:
OsaSync sees that a meeting has been deleted on this computer. Do you want OsaSync to delete this meeting on all synced computers? - error# -196609 in proc: clsFldDelItmsWrap.DelItemsPermanent. Error in IMAPIFolder.DeleteMessages: MAPI_W_PARTIAL_COMPLETION
- error# 91 in proc: clsFoldermonitor.pmsgSyncFldBegin. Object variable or With block variable not set. Could happen when the other computer has synced multiple folders in advanced mode.
New in version 6.5 (August 7, 2009)
new functions:
- OsaSync in Client-Server mode: The prefix for appointments or
tasks that is shown on other computers can now be changed more
easy. In previous versions this prefix could only be changed by
manually editing the CnfComputers.txt file on the LAN server ánd on
the FTP server if the computer also syncs via FTP.
The Edit Prefix window (Options - Advanced Options - Outlook items - Appointments or Tasks tab) has been improved. It has two tabs:
- How I see others: offers a choice if you want to see the prefixes that have been specified on other computers or if you want to set your own prefixes. The prefixes from th other computers are now shown
- How others see me: shows the prefix as configured with the OsaSync connection wizard and offers a button to change this prefix.
solved problems:
- Prefixes for appointments or tasks were not used after a fresh OsaSync install if prefixes were filled out in the connection wizard. The option to use prefixes is now by default enabled.
- OsaSync will now show a message when a new appointment, task or
contact cannot be saved by OsaSync. When OsaSync sees that a new item
it assigns a unique ID to the item and saves the item with this new
ID. If, in previous versions, this save failed OsaSync would silently
recover from the error and continue. The item however was not synced
because OsaSync can't sync items without ID and folders could go
silently out-of-sync.
This failure to save new items is most often caused by some other program or Add-in that is somehow interfering with OsaSync's operation. When this happens again in version 6.5 or higher a message will be shown with a link to the technical support page about how to tackle this problem.
New in version 6.4.1 (July 20, 2009)
solved problems:
- Rejected meeting requests. Imagine the following scenario:
3 users have synced their calendar and receive a meeting request. This
meeting is relevant for 2 people so they accept the meeting request.
Outlook automatically creates the meeting in the calendar and OsaSync
makes sure this meeting is correctly synced. However, the third person
does not want to attend the meeting and rejects the meeting request.
The meeting is now automatically deleted by Outlook (if it was already
created by OsaSync in this persons calendar). OsaSync now sees this
deletion and deletes the meeting also on the synced computers! This is
technically correct but functionally not what we want because the
meeting should still remain in the synced calendar because both other
users do want to attend this meeting.
In order to handle this scenario OsaSync will now:
* when a meeting is deleted OsaSync will show a popup window asking if you want the meeting to be deleted on the synced computers or not.
* this popup window is shown for 5 minutes waiting for an answer. If no answer is given within these 5 minutes, the meeting is not deleted. OsaSync then shows a message that this meeting has not been deleted and continues its work. -
error# 5 in proc: clsAppointment.CreateAppMsgData. FindAppOnLogicalID: Invalid procedure call or argument LineNumber: 2. This error could occur when appointments that are birthdays or anniversaries are synced in OsaSync running in a non-English language.
New in version 6.4 (July 8, 2009)
new functions:
- Further improvements to the reliability of the synchronization of meetings. Starting with version 6.4 OsaSync in client-server mode keeps track of all IDs of appointments in a central file on the server called OsaSync.mdb. This further reduces the chances of the creation of duplicate meetings.
- OsaSync installed in client-server mode now saves a copy of the previous_osasync.log file on the server in the \OsaServer\logs folder. For each computer copies are saved until 7 days in the past. Older copies are deleted. This makes the retrieval of relevant log files much easier.
solved problems:
- Advanced mode syncing: if a contacts or calendar folder was prepared for synchronization using the sync wizards Advanced mode this would result in many errors 91. Those errors would again result in many osasync messages that contacts or appointments are already present in the folder.
New in version 6.3.1 (May 13, 2009)
solved problems:
- Tasks: CheckIfRightAppIsFound: FindTaskOnLogicalID: IMAPITable::FindRow() returned MAPI_E_INVALID_PARAMETER. Due to this error tasks don't sync anymore.
New in version 6.3 (May 6, 2009)
Please note:
Starting with version 6.3 OsaSync has
been released in two versions:
- A version for Outlook 2000 and 2002
- A version for all higher versions: Outlook 2003 and 2007
new functions:
- Folder Compare process improvements:
It is now possible to compare a Calendar folder. The way a folder compare process works has changed. Now the computer that initiates the folder compare is the only computer that will be prompted if changes are found that need attention. To read more about the new folder compare process please check out this faq. - Items deleted with SHIFT-DEL were not 'seen' by OsaSync because items deleted with SHIFT-DEL do not go to the deleted items folder. Now those deletions are seen and synced accordingly. This same change also sees all items deleted by a PDA or Cell phone or by any application.
- Because of the improved deletion detection it is not necessary
anymore to explicitly mark a folder as being synced by a PDA or Cell
phone. This means that the option to enable OsaSync for syncing with a
PDA has become obsolete and has been removed.
ALL changes made on a PDA or Cell phone will be seen by OsaSync and synced to the other computers!
solved problems:
- FTP files transfer:
The option Check when Outlook starts on the OsaSync options window did not work if the computer was configured to sync only via FTP. - Synchronization of appointments has been improved, especially the handling of meetings. This reduces chances on duplicate appointments creation.
- Termination of OsaSync upon closing of Outlook has been improved. Together with the latest Outlook 2007 service pack 2 this greatly reduces the chances of incomplete termination and subsequent failure-to-start problems. Both service pack 2 and OsaSync 6.3 also solves the issue 'The data file file name was not closed properly. This file is being checked for problems'.
- Appointment reminders firing repeatedly during OsaSync checking
for changes or during the import of files resulting from a prepare
folders for synchronization process.
note: this is only solved in OsaSync 6.3 for Outlook 2003 and 2007! - When Outlook is connected to Microsoft Exchange server it is possible that Outlook performance drops. This happens because Outlook/Exchange marks each item that has been inspected by OsaSync as being modified. That in turn triggers a new inspection by OsaSync. Then again Outlook/Exchange marks the item as changed, and so on. OsaSync can now detect and terminate this looping behavior.
New in version 6.2.1 (November 27, 2008)
solved problems:
- Read-Only folders: In an exceptional situation the unsetting of a Read-Only folder back to a normal folder does not work because the button Undo Read-Only is not visible on the OsaSync folder property windows. It is now possible to force OsaSync to show this button thereby enabling the possibilty to restore a Read-Only folder to normal. If necessary see the technical support page for details on how to do this.
- FTP files transfer:
OsaSync transfers FTP files when Outlook is closed. This behavior is now optional and can be disabled by clicking the setting Do not transfer files when Outlook closes on the OsaSync FTP option windows. Note that if ftp files are not transferred other computers miss the corresponding updates until Outlook is restarted. - OsaSync checks all folders for changes every hour (as a double check
to make sure no changes area missed). This check also runs when e-mails
are received during OsaSync initialization process. During this folders
checking it was not possible to have OsaSync check other computers for
changes, transfer ftp files or start the folder sync wizard. The
corresponding menu items were grayed out and appended with 'processing...'.
It is now possible to check for changes, transfer ftp files or start the wizard also if the folders checking is running. The checking is postponed and continues when the other process has finished.
solved problems:
- Marking a Read-Only folder again as being fully accessible would sometimes fail.
- In one (exceptional) scenario the OsaSync computer ID could be different from the computer ID listed in the CnfComputers.txt file in the OsaServer folder. This could result in some OsaSync messages not being processed correctly.
New in version 6.1.4 (July 28, 2008)
solved problems:
- OsaSync is unable to connect to the server (or to a
peer computer) and goes into Local Mode. This can happen after the
installation of Windows XP service pack 3. When you previously ran the
OsaSync connection wizard, the wizard didn't prompt you for a username and
password if it was possible to make a connection without a username and
password.
Solution: install 6.1.4 and rerun the OsaSync connection wizard. In the step connection click the checkbox Always ask for a username and password before you have the wizard connect to your network computer. The wizard will now prompt you the username and password for the computer you are connecting to.
solved problems:
- Custom form syncing: in some cases not all custom fields were synced. Initial syncing was fine but some updates were not recognized by OsaSync.
solved problems:
- error# 91 while Outlook is closing. This could happen if Outlook was closed right after it was started.
- some minor tweaks
solved problems:
- error# 424 in proc: clsManager.Timerfired. Object Required. This error could occur when Outlook was closed.
new functions:
- Read-Only folder syncing has been improved. If a folder is
-
- FTP syncing: when Outlook shuts down OsaSync will upload any pending files to the FTP server before terminating.
- 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.
- 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.
- 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
- 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.
- 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.
- 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.
- 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)
- 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:
-
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
For comments or suggestions about this site: techsupport@vaita.com
© 2012 Vaita