Last updated: Fri, 04/30/2010
Major changes in this release are: adding synchronization of Lotus Notes event chairperson into Google invitees field; and also fixing the problem with all day events being marked as busy time in Lotus Notes when they're synchronized from additional subscription Google Calendars, like holidays, days of week, and so on. Now all events from read-only Google Calendars on which user is subscribed, including holidays, days of week, and calendars of your friends, will not mark your time in Lotus Notes as busy. See the complete list of changes and fixes in Release Notes for 2.0.1.7
Release notes - AweSync 2.0.1.7
- Now chairperson of Lotus Notes event will be synchronized to Google Invitees field on first position. Please note that you need to follow the same "spam" protection techniques as described for Invitees synchronization in this article. Also, disabling Invitees synchronization from Lotus Notes to Google will disable chairperson synchronization as well;
- Events from read-only Google Calendars are now not marked as busy time in Lotus Notes;
- Fixed the bug when meetings canceled in Lotus Notes were not removed from Google Calendar;
- Fixed the problem with yearly repeating events synchronized from Lotus Notes to Google causing additional schedule exceptions;
- Fixed minor bug with Activation not working if user selected another Notes ID file right before the activation.
Release notes - AweSync 2.0.1.5
- New Google API 1.5.0.0 is used in this release instead of current 1.4.0.2 for higher synchronization speed
- Distributed environment support is enhanced in AweSync, when synchronization is working in automatic mode simultaneously from several computers. The profile document, in which index is "locked" now when synchronization is started, so that process doesn't start at the same time on other computers (if working against the same replica of the database). If AweSync is terminated unexpectedly and "lock" is not removed upon synchronization completion, you will be alerted about locked profile, and it will be possible to unlock manually
- Fault tolerance is increased for the index. Now in addition to the profile document in mail database, index is additionally stored on the local file-system periodically during synchronization, so that it can be automatically recovered in case of unexpected fault such as power-off, or process kill
- Added the option to disable pop-up balloon if Lotus Notes database is unavailable - should be also useful for traveling users who synchronize against the server database, but don't maintain persistent connection to Lotus Domino server
- Fixed potential deletion of events from Lotus, when switching from 2-way to 1-way sync and back
- Fixed events from read-only Google calendars not synchronized back to Lotus, if they were removed manually in Lotus. Now they will be synchronized back to Lotus after the second synchronization (first sync will update them properly in index)
What we didn't include in this release, but possibly will add going further:
- Reliable solution for proxies with NTLM (Windows) authentication is not yet found
- Storing of index backup in Google Docs is also not yet implemented
Release notes - AweSync 2.0.1.4
- Fixed error "Google service did not accept participants" causing further errors "Google operation failed (409): Version conflict";
- Fixed error "Can't process: Notes error: Invalid or nonexistent document";
- Minor UI fixes.
Release notes - AweSync 2.0.1.2
- Fixed duplicate and missing calendar entries in Google Calendar after sync for specific Lotus Notes data;
- Fixed incorrect event schedule in Google Calendar for specific Lotus Notes data;
- Fixed "Error while SyncLotusDoc (#1#2#3#4#5#7#8#9): Index was outside the bounds of the array;
- Fixed "Can't process: The file exists" error;
- Fixed "Google operation failed (409): Version conflict" caused by operation time-out in Google;
- Changed behavior for users, who enable option "Don't prompt for a password from other Lotus Notes-based programs" in their Lotus Notes User Security settings or use Lotus Notes single logon. If no password is saved in AweSync Lotus Options, then on the first sync, users will be prompted to enter the password. Leaving password blank in this prompt together with enabling "save password in settings" will make AweSync save empty password in settings, and it won't be asked again if Lotus Notes is running in the background.
Release notes - AweSync 2.0.1.1
- New feature is implemented. If due to security reasons you canot store Lotus Notes or Google password in AweSync settings, you can leave password field(s) blank. In this case Awesync will prompt for password(s) and will use them until you exited AweSync;
- Fixed - ERROR - "Error during Google batch run: Value cannot be null. Parameter name: key" which caused event duplication;
- Fixed - WARN - BatchId of processed event is empty. EventId: xxxxxxxxxxxxxxxxxxxxxx. Status: 200. Reason: Success;
- Fixed - WARN - Value cannot be null. Parameter name: Document is null
Release notes - AweSync 2.0.1.0
- Increased synchronization reliability in case network faults during the process;
- Fixed the error with duplicate entries in index "An item with the same key has already been added";
- Index processing has been changed, so now if there is an error, which is not critical, synchronization will go through. But if index structure is critically damaged, sync will stop. In latter case you would need to submit an issue to our Support database to get further directions;
- Fixed the "Error in ProcessSophisticatedRules"
Release notes - AweSync 2.0.0.9
- Fixed "Network Unavailable" error for users who connect to the Internet via proxy server
Release notes - AweSync 2.0.0.8
- Added Privacy Options. Currently it can be used only to disable invitees synchronization, due to multiple requests from our users, who need it for privacy purposes, or who experienced Google Calendar sending reminders to their invitees email. Please note, that when Invitees are disabled for synchronization, this field will not be synchronized immediately, however it will not be cleared from those events, which were already synchronized. If sync for this field will be re-enabled again, synchronization of invitees for those events, for which it was previously prevented, will not be performed.
So, if you're using one way sync from Lotus Notes to Google, and need to make sure all your events coming from Lotus Notes to Google don't have invitees, you would need to remove and re-create a Google calendar for receiving events from Lotus Notes, and perform the sync in there. See the details below.
This is an instruction on how to push all events from Lotus Notes to Google without invitees for those, who are using one way synchronization to dedicated Google calendar. It is not recommended for those, who are using different synchronization directions and options.
As you're synchronizing one way, you can try to perform a "sync from scratch" sequence of actions:
1. Delete the calendar in Google, to which you're pushing Lotus Notes events - if possible, i.e. if you don't create events in it manually (otherwise, you would need to leave this calendar, but manually delete events coming from Lotus Notes, which is a bit painful).
2. Create new empty Google calendar for receipt of events from Lotus Notes.
3. Change your AweSync settings to synchronize with only this new Google calendar as default (don't forget to click Retrieve button, so that new calendar appears)
4. From tray icon select Debug -> Remove Index
5. Perform sync all - Added Network Options with a new option to show balloon pop-up, when the network is unavailable, and moved other network settings there.
- Added a progress indication, when verification is done whether any calendar events were removed from Lotus on the final phase of synchronization for better visual control, as user may think it is hanged
- Changed retrieving of primary documents from Google with smaller batches to prevent hanging
- Changed working with batches sent to Google during synchronization to increase reliability
- Fixed error happening when one instance of a repeating event created by a delegate was rescheduled "The batch operation for event (Event URI is not found) failed. Returned code: 403. Reason: You can't modify a cancelled event"
- Fixed few misspellings in the log
Release notes - AweSync 2.0.0.7
- Exception when the main AweSync form loads
- Fixed the error preventing synchronization to complete normally "The entry is already part of this collection"
- Fixed Notes Document cannot be parsed - DateTime field is empty: RepeatInstanceDates - now if field is missing or invalid AweSync collects information from the other fields
- Fixed similar problem - Invalid field "StartDateTimes" (dimension is X, but should be Y)
- Fixed the problems with synchronization of events originating from MS Outlook
- Fixed the problem with America/Argentina/Buenos_Aires time zone "No rules found for rule name Arg"
Release notes - AweSync 2.0.0.6
- Fixed exception "AweSync.MainForm ........", which occured on startup in some rear cases.
Release notes - AweSync 2.0.0.5
- Fixed "Error happened while Google batch ran";
- Fixed "System.NullReferenceException at Google.GData.Client.AtomBaseLink.get_AbsoluteUri()";
- Fixed "Can't process: Value cannot be null.";
- Fixed "Can't convert time zone from...";
- Fixed "Can't process: Exception... Domino8.NotesDocumentClass.get_Items()";
- Fixed "Unexpected error: {0}Systen.NullReferenceException: AweSync.MainForm_Load(object sender , EventArgs e)";
- Fixed "Upgrade Now box pop up every time a sync occurs" - now this message box will be shown only once;
- Fixed "Proxy password is lost, and also in auto-detect it doesn't ask for password".
Release notes - AweSync 2.0.0.4
- "Child domain removed" problem causing not all recurring events to be synchronized is fixed;
- New known instances of "Notes document cannot be parsed" fixed;
- Potentially slow or even hanging synchronization fixed;
- Fixed events created in Google calendar from iPhone not synchronizing into Lotus Notes;
- Fixed the problem with invitees and locations being removed during synchronization, which also caused conversion of Meetings into Appointments.
Release notes - AweSync 2.0.0.3
We fixed "Value cannot be null", "Object reference not set" and know instances of "Notes Document cannot be parsed" errors. Now the team is also actively working on "Child domain is removed" problem, and the fix should be available in the next 1-2 days.
Release notes - AweSync 2.0.0.1
- Fixed with time zone errors, please refer for details to the following comment
- Fixed the bug "Could not load file or assembly Interop.Domino8" on 64-bit operating systems
- Fixed some instances of the errors "Notes Document cannot be parsed"
What's new in AweSync 2.0.0.0
- Full support of repeated events with exceptions;
- Configuration Wizard, see details here;
- An option is added to change if the Google Calendar name should be stored in Lotus Notes Calendar entry Category field. Might be useful for those, who use categories in Lotus Notes Calendar intensively, and don’t want to mess it up with stuff coming from Google Calendar.
- Support of synchronization with Google Calendars to which there is no write access (for example, shared by other users).
- Google Apps Calendar support is added.
- Support of public and private flags synchronization.
- Configuration for double-clicking tray icon is added to either show/hide application window, or start/stop synchronization.
- A log of calendar entries changes is added, where more detailed information about synchronized entries can be found (View Changed Documents link below the Synchronization Log).
- Support of synchronization between Invitees Required field in Lotus Notes Meeting and Guests field in Google calendar event. Internet addresses of corresponding Lotus Notes user is placed in Google calendar event.
- Google Calendar event field Where is now synchronized with Lotus Notes Calendar entry Location field, including 2 way. Values of reservation fields from Lotus Notes Calendar entry are added to Google Calendar event Where field in format [Rooms: RoomName] [Resources: ResourceName].
- Google SMS notifications are now supported. You can enable AweSync option to map Lotus Notes Notify Me options into Google SMS notification, if it’s enabled in your Google Calendar.
- Now it’s possible to cancel the synchronization at any time.
- Made some improvements in handling Lotus Notes and Google data, which previously could cause some errors, as well as fixed a lot of other bugs.
- It is now possible to run few instances of different installations of AweSync which makes it possible to use them in terminal server environment.
Please see AweSync Settings section for more detailed explanations and screenshots.
