SynQ Release Notes

These release notes describe enhancements/fixed problems (see below) and known problems in the SynQ add-in for Microsoft Outlook. They also provide troubleshooting information.

The SynQ add-in (build 2.4.1.77) for Microsoft Outlook synchronizes calendar events, to-do/task items, and address-book contacts between your calendar server and Outlook. You must have a valid user account on your calendar server. Additionally, Outlook must be installed, configured, and run at least once for each user prior to running SynQ.

Important: In order for you to install and use SynQ 2.4.1, your system must run Mirapoint Operating System (MOS) 3.8.1 and have the D3_8_1_webcal_2 patch installed. Also, if your enviroment has multiple servers, all the servers must be upgraded to MOS 3.8.1. Mirapoint does not support environments in which some servers are running MOS 3.8.1 or higher while other servers are running MOS 3.8.0 or lower. The D3_8_1_webcal_2 patch must be installed on each server.

For details on using the add-in, see the Outlook SynQ User's Guide.

Fixed In This Release

Release 2.4.1 fixes the following customer-reported issues:

  • If your calendar server login ID and the user name in your email address were not the same, you could have encountered event-ownership problems following synchronization. For example, an event owner might have been mistakenly regarded as an attendee and Accept and Decline buttons would have incorrectly displayed in the person's Outlook Meeting window for that event. (36884, 38354, 35117)
  • When you attempted to setup a meeting in Outlook, free-busy information was not fetched for some email addresses when you entered attendees on the Scheduling tab. (38259)
  • (This problem existed with the WebCal server and was independent of SynQ.) A deleted exception to a recurring event would not be restored in an attendee's WebCal calendar even if the event owner updated the event. This problem had been observed in the following scenario: 1) User A (using WebCal) created a recurring event and invited User B (using Outlook); 2) User A created an exception (for example, he changed the time for one of the meetings in the series; 3) User B synchronized, declined the exception, and synchronized again; 4) User A saw that the exception had been declined and changed the meeting time; 5) In User A's calendar, User B's status was "Not yet confirmed"; but, the exception was not restored in User B's WebCal calendar. (37497)

Enhancements In The Previous Release

Release 2.4 (build 2.4.0.72) introduced the following enhancements:

  • In previous releases, the calendar server maintained strict ownership of calendar events and had restrictions on who could modify/update events. For example, a user who was an attendee to a meeting could not make a change to a meeting event and synchronize that event back to the calendar server because the server refused to let a user change a meeting that the user didn't own. Similarly, the SynQ add-in could not sync meeting invitations that came from users that were not known to the Mirapoint operating system.

    These issues have been addressed in such a way that a Microsoft Outlook user can make changes to an event that the user does not own. Similarly, now a user can synchronize an event even if that event is owned by a user that is not known to the Mirapoint calendar server.

  • Multiple Microsoft Outlook user profiles are now supported. (25242)

Fixed In The Previous Release

Release 2.4 fixed the following problems:

  • It had been observed that a COM error occurred upon synchronization involving a recurring event that had been declined via Outlook. (36410)
  • The Conflict Detected - SynQ dialog box, which displays when SynQ detects a synchronization conflict, did not have a scroll bar. (36159)
  • If you had not configured an IMAP account in Microsoft Outlook, the SynQ installer would crash. (36817)
  • When a meeting was changed, the attendee status - as shown on the Tracking tab within Outlook's Meeting window - was incorrectly carried over from the response to the original invitation. This problem occurred with a delegate user in the following scenario: 1) Delegate scheduled a meeting a delegator's calendar and invited himself; 2) Delegate synchronized; 3) Delegate accepted the meeting invitation and then synchronized; 4) The delegator modified the meeting time and then synchronized; 5) SynQ displayed the conflict resolution dialog box and the delegator specified Outlook as the winner of the conflict. At that point, the Tracking tab for the event in the delegator's Outlook calendar showed that the attendee accepted the meeting at the new time. (36632)
  • If you scheduled a meeting in WebMail/WebCal Corporate Edition and invited an external attendee, the email address of the external attendee would be converted incorrectly once you clicked Add on the Schedules tab. (36270)
  • SynQ did not allow attendees to modify events that they did not own. Other event-ownership issues also existed. (24746, 33527, 30397, 33636, 34212)
  • Shared calendar items to which you had read-only access would be restored to their original state if you modified them with Outlook and synchronized. Essentially, events which you accepted or declined would be restored to their original states during synchronization. (33762, 33612)
  • In some cases, recurring meetings which were accepted by an attendee were not synchronized to the calendar server if the meeting owner edited the meeting request prior to the attendee accepting. (35401)
  • Due to an incompatibility between SynQ and Microsoft Outlook, a delegate user could no longer access certain buttons in the Outlook appointment/meeting window when setting up and responding to meeting requests on behalf of another user. Specifically, the Invite Attendees, Send, Cancel Invitation, Send Update, Accept, and Decline buttons in the Outlook appointment/meeting window were disabled. Now these buttons are available to delegate users, but not during the creation of new meetings. See the Known Problems section in this document for workarounds when a delegate user creates sets up a new meeting on behalf of someone else. (33906, 35402)
  • If you were a delegate user and you edited an event in another person's calendar (the delegator's calendar), you could have encountered a dialog box with the following text during synchronization: "The reminder for "event" will not appear because the item is not in your calendar or tasks folder. Is this OK?" (33885)
  • If you—as a delegate user—created an event in one shared calendar and then used the drag-and-drop technique to move the item into other shared calendars, the event would fail to write to the other calendars during synchronization. (33941)
  • If you changed an all-day recurring Outlook event so that it was no longer an all-day event, the change would not be reflected in WebCal. (34999)
  • In release 2.0.6, a fix was implemented to prevent synchronization from failing if Outlook was configured to display appointments in the Preview pane and modifications were made to an event's attendee list. As part of the fix, SynQ automatically closed the Preview pane upon synchronization. Until this release, however, there was no dialog box informing you that the Preview pane was being closed. (28338)
  • Possible database corruption could have occurred if you did not safely shut down your computer or exit Outlook while SynQ was running. (28333)
  • The data entered on the Personal Account dialog box was specific to the user who was logged into Windows, rather than the current Outlook profile.(25242)
  • If a user who was using a Mirapoint calendar server received a meeting invitation from an Outlook user who was not using a Mirapoint calendar server, and the invitee used Outlook to accept the invitation, SynQ did not synchronize the meeting to the invitee's calendar because he did not own the event. (28275, 34040)
  • If you were a delegate user who scheduled a meeting on behalf of another person and you included yourself as an attendee, you had to perform a manual sync twice so the event would display in your Outlook calendar. (24910)
  • There were known problems regarding attendees modifying events where the events would return to their original states or cause duplications during synchronizations. (33793, 34212)
  • A duplicate event would be created in a delegator's calendar if the following scenario occurred: 1) Using Outlook, a delegate user created a meeting on behalf of someone else and included himself as an attendee; 2) The delegate user edited the meeting request and sent an update; 3) The delegate user read the update email and synchronized. (34114)
  • As a meeting attendee, you could not accept or decline a single occurrence of a repeating event.(34176)
  • If the version numbers of your database and SynQ connector were different and you encountered a warning informing you of the mismatch, the warning dialog box would persist even after you exited Outlook. (34204)
  • If you encountered a database error/warning and then restarted Outlook without dismissing the dialog box, Outlook would crash once you dismissed the dialog box. (34205)
  • It had been observed that changes to a shared user's recurring event created in Outlook were not saved to the calendar server in the following scenario: 1) You created a recurring event in a shared user's calendar using Outlook and then synchronized; 2) In WebCal, you modified the event (such as changing the first and third occurrences in some way) and then synchronized; 3) In WebCal, you deleted the event series; 4) In Outlook, you changed the description of the event series; 5) Set SynQ's conflict resolution feature to favor Outlook and synchronized.
    In this scenario, the changes made via Outlook were not saved to the server. (34191)
  • You could have received occasional decline notifications from attendees for meetings that had already occurred and for which the attendees did not originally decline. (32223, 35355)
  • If you were a delegate user attempting to add a shared user (that is, a user whose information you want to synchronize), you would encounter problems if you entered a partial name in the User Settings - SynQ dialog box and then clicked Verify. (For example, users "test1" and "test2" were valid users and you only entered a partial name such as "test".) If you selected a user in the resulting Outlook Check Names dialog box, your selection would not display correctly in the Users to Synchronize section on the SynQ tab. Additionally, the user status would incorrectly state "Need to verify user," and an error would occur upon synchronization. (35399)
  • If you uninstalled the beta version of SynQ 2.4, you could not install SynQ 2.3 on the same PC. (35537)
  • In some cases, WebCal incorrectly incremented the duration of all-day events by one day. (34175)
  • If you deleted an occurrence of a repeating event and synchronized, the change might not have been reflected in your Outlook calendar. (34178)
  • If you received a meeting request created in Outlook and proposed a new time, the resulting email sent to the event owner would not show the event's current and proposed times. (35713)
  • You could have encountered a COM error upon synching if you deleted a meeting in which you were the event owner and the event had already accepted by an external attendee. (35662)
  • If you entered a valid user name on the Scheduling tab within Outlook's Appointment window, you could have encountered an error message stating that Microsoft Outlook did not recognize that particular user. This problem occurred because SynQ did not parse email addresses correctly. (35592)
  • As a delegate scheduling a meeting on behalf of another person (a delegator), you could have encountered an error message stating that Microsoft Outlook did not recognize the user you entered on the Scheduling tab within Outlook's Appointment window--even though you entered a valid user name. Further, if you saved the event, the meeting would appear in the delegator's calendar, but the owner's name would be listed twice on the Scheduling tab. This problem occurred because SynQ did not parse email addresses correctly. (35594)
  • An event opened in Outlook would inexplicably display Accept and Decline buttons and its attendee list would be read-only in the following scenario: 1) In Outlook, you scheduled a meeting on behalf of another person and synched; 2) You used WebCal to edit the event's title and then synched. This problem occurred because SynQ did not parse email addresses correctly. (35604)
  • It has been observed in a case involving a delegate scheduling a meeting on behalf of another person, the event owner would receive an update notification with the Propose New Time button enabled when the owner - rather than an attendee - would edit the event. (35657)
  • If a delegate scheduled a meeting in Outlook on behalf of another person (a delegator), the delegator would receive a WebCal message from herself, stating that she was invited to a meeting owned by her. (35659)
  • If an Outlook user edited a meeting originally setup in WebMail/WebCal Corporate Edition, the update email received in Corporate Edition would state that the event was missing or had been deleted. A similar problem could also have occurred if a meeting setup in Outlook was viewed in Corporate Edition. These problems won't occur if Outlook is not configured to send meeting requests in iCalendar format.
    To configure Outlook accordingly, do the following:
    1. In Outlook, click Tools > Options.
    2. Click Calendar Options.
    3. In the "Advanced options" section in the Calendar Options dialog box, uncheck (deselect) the When sending meeting requests over the Internet, use iCalendar format option.
    4. Click OK.
    (36160)
  • You would encounter an error if you synchronized calendar events and contacts in Microsoft Outlook 2000. (36155)
  • It had been observed that when a meeting was scheduled by a delegate on behalf of another person (the delegator) using Outlook and an attendee used WebCal to accept the invitation, the meeting organizer information would display incorrectly when that attendee viewed the event following synchronization. The event incorrectly listed the delegator as the event organizer (instead of the delegate). (36190)

Copyright © 2003-2006 Mirapoint, Inc. All rights reserved.