Outlook Mapi Was Unable To Load Gsync.dll
Vallie Brzenk
FIX: Addressed "The specified sequence number is below the current sequence number of the resource. Re-fetch the resource and use its sequence number on the following request" error preventing recurring event exceptions from syncing.
NEW: Added new Field Maps feature to the Google contact sync mapping allowing for overriding field mappings performed by the sync work flow. This advanced feature allows for addressing customer specific sync work flow edge cases. In general, and in most cases, customization of the contact field mappings is not needed. The feature should only be used/configured with the assistance of product support or support documentation.
NEW: Updated all gSyncit .Net, Windows SDK, and VC++ runtime dependencies with the latest available updates and recompile the sotware using Visual Studio 2019 toolsets. These changes are being done in preparation to migrate gSyncit build tools to Visual Studio 2022.
NEW: gSyncit v5.6 will only support Windows 8 and higher, Microsot .Net Framework 4.8 and higher, and Outlook 2013 and higher. All *prior* versions of Windows, .Net Framework, and Microsoft Office are considered end-of-life meaning Microsoft is no longer supporting or maintainaing these versions.
FIX: Resolves CalDav sync issue where the sync was incorrectly expecting all calendar events to have .ics extension. This issue could result in UID conflicts and/or preconditioned failed errors.
FIX: Revision to handling of PreconditionFailed and Conflicts when syncing CalDav events. The default work-flow will force the event to push to the CalDav server regardless of the ETag value in the case where the CalDav server is the primary source (default).
FIX: Corrects reported issue where events assigned the time zone "[(UTC+01:00) Brussels, Copenhagen, Madrid, Paris" were incorrectly synced to the wrong Google event time zone causing the time of the event to shift by 1 hour.
UPDATE: Addresses issue where enabling sync on send/receive or folder change may cause Outlook to run in the background unexpectedly after the gSyncit system tray app is loaded.
- NEW: Added the ability to assign a Outlook category to new events imported from the Google calendar. This option is found on the categories tab for the Google calendar sync mapping.
FIX: Corrects issue where Google event with a weekly recurrence rule that occurs on the nth weekday fails to sync to Outlook. This recurrence rule is not allowed/supported by Outlook.
Due to this change gSyncit will no longer allow selecting these deprecated labels on the sync mappings. Existing unedited sync mappings will continue to reference to deprecated groups but you may encounter issues syncing changes from Outlook to Google until the sync mapping is updated to point to non-system groups.
If you are syncing with specific Google contacts system groups (e.g. Friends, Coworkers, Family, Chat Contacts, ...) then you need to update your Google Contacts to move your contacts to equivalent labels that you create. Then update the gSyncit Contact sync mapping to point to the new group. This ensure contacts synced from Outlook to Google Contacts can be assigned to the expected groups. For example, if you are currently syncing your Outlook contacts with a label/group called "Friends" you will need to explicitly create a groups/label in Google contacts called "Friends" and update the gSyncit Contacts Mappings to sync with this new "Friends" group.
If you are currently using the option to auto sync Outlook categories with Google groups then no changes are required. The new groups will be created automatically during the sync process.
PATCH: Workaround for rate limiting issue syncing Google People / Contact photos that may result in some contacts not syncing. Google limits contact photos to 60/minute/user. The sync process has been updated to reflect this rate limit. At the same time we've made a request to Google to increase our quota to improve sync performance.
UPDATE: Updates the Todoist sync to use the description field for syncing the task description. This update also removes the *legacy* option to sync the Todoist comment with the Outlook task description field.
FIX: Adds configuration to CalDav sync to control syncing the CATEGORIES field which is not supported by many CalDav servers. This option is enabled by default. If your CalDav server does not support the CATEGORIES properties then you should disable this option to avoid the loss of categories assigned to Outlook events.
FIX: Corrects "Response status code does not indicate success: 400 (Bad Request)." caused by a change made by Google on September 23rd that requires sending a "Content-ID" header with each batch task request entry. This change conflicts with Google's own API BatchRequest implementation which does not set this now expected header.
This was not a planned or communicated change from Google. They updates the Google Calendar service without warning that also was compatible with their own Microsoft .Net Client Libraries used by gSyncit.
FIX: Corrects "Response status code does not indicate success: 400 (Bad Request)." caused by a change made by Google on September 13th that requires sending a "Content-ID" header with each batch task request entry. This change conflicts with Google's own API BatchRequest implementation which does not set this now expected header.
UPDATE: Updated the Google Contacts/People sync batch operations from 25 to 500 contacts per request to address potential quota limits. This also improves the contact sync performance slightly when updating large batches of changes.
REVISION: Updates the authentication browser windows to no longer use incognito mode. Using incognito mode was confusing and concerning to customers despite the deliberate choice to use incognito mode in gSyncit to offer increased security by avoiding any credentials being cached.
FIX: Corrects "Insufficient permissions to modify a field on the resource" error when updating recurring Google event occurrences related to a meeting owned by someone else. This issue surfaces when the sequence property on the event, organized by someone else, is updated. This issue caused some changes to recurring Outlook event exceptions to fail to sync/update to the Google calendar.
FIX: Correctly maps Outlook time zone "Atlantic Standard Time" to "America/Halifax"
- FIX: Correctly error syncing the Outlook "Starred" contact distribution group with Google groups.
- FIX: Corrects contact duplication issue in the gSyncit v5.5 update in cases where a contact contains only a first name that is a email address, does not contain a last name or the company name contains a " character. After installing this update use the duplicate removal wizard on the gSyncit tool bar in Outlook to clean up any duplicate Outlook contacts.
NEW: Updated the Google Contact sync to use the recently released Google People API batch operations ( -people-api-now-supports-batch.html) providing faster contact syncing when adding, updating and/or deleting contacts.
NEW: Updates CalDav sync to support the iCalendar COLOR property specification allowing the color of a Outlook category to sync with a color assigned to a iCalendar event. See specification for additional details. Please check that your iCalendar implementation supports this property.
To enable this work-flow select the "Other" tab on the gSyncit CalDav sync mapping and select the option (see below) to sync CalDav event color with the Outlook event category. This option maps the first Outlook category color with a matching/assigned/supported iCalendar event color and vice versa.
UPDATE: Updates the Outlook category listings on the gSyncit settings to show the categories available within the mailbox for the selected Outlook folder. In prior versions of gSyncit the list if categories was based only on the primary mailbox.
NEW: Revised Google calendar sync work-flow to include video conference link in the Outlook event location and updated the original logic to sync the Google Hangout link to now include any video conference link associated with the Google event along with the meeting passcode, password, pin, and/or meeting id.
FIX: Corrects error syncing contacts from Google to Outlook that have a year set to 1601 or 1604. This is possibly caused by a defect in a prior version of gSyncit but the issue has not been confirmed/replicated.
FIX: Corrects "r" character appearing after the street address when syncing Google Contacts with iOS contacts. To fully correct this issue you should set Outlook as the primary source on the gSyncit Google contacts sync mapping and re-sync all contacts to your Google account. This will remove the "\r" return control character that iOS does not render correctly.
Note: if you experience this issue after installing gSyncit v5.5 then you will need to edit the gSyncit Google Contact sync mapping, select the repair tab and reset BOTH the sync history and cache to ensure the updated contact information is requested from your Google domain contacts list.
FIX: Updated the "Restore Settings" button on the gSyncit settings to open dialog to the current gSyncit settings folder. We'be seen a few reports of users upgrading to gSyncit v5.5 where the settings failed to migrate. To work around this use the "Restore Settings" button on the gSyncit settings and select and open the file settings5.dat.
FIX: Corrects "r" character appearing after each line on the Contact notes when syncing Google Contacts with iOS contacts. To fully correct this issue you should set Outlook as the primary source on the gSyncit Google contacts sync mapping and re-sync all contacts to your Google account. This will remove the "\r" return control character that iOS does not render correctly.
7fc3f7cf58