|
|
Upgrade OsaSync PRO to version 7.0
This download will update your installation of OsaSync PRO to the latest version 7.0.
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.
-
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 7.0
| Outlook 2007 and 2010 |
Outlook 2000, 2002 (=Outlook XP) and 2003 |
|

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!
OsaSync PRO Upgrades
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:
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.
New in version 6.2 (October 31, 2008)
new functions:
- 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.
New in version 6.1.5 (October 3, 2008)
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.
New in version 6.1.3 (July 15, 2008)
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.
New in version 6.1.2 (July 9, 2008)
solved problems:
- error# 91 while Outlook is closing. This could happen if Outlook was
closed right after it was started.
- some minor tweaks
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 less 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)
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.
|