Outlook Connector Attempts To Set ACLs When Searching For Shared Calendars Causing Long Delays
(Doc ID 1303222.1)
Last updated on MAY 23, 2021
Applies to:Oracle Communications Connector for Microsoft Outlook - Version 7.0 and later
Information in this document applies to any platform.
With MS Outlook, there is a limitation where you must search by the calendar owner name when searching for calendars. You cannot search by calendar name or ID. Convergence allows searching by calendar name so it is much more user friendly.
Because of this limitation, performance is affected where the searches can take a long time to return results.
We created an account called resourcemaster which owns all of the resource calendars.
This was to ensure that all resource calendars have an owner who is not a regular user.
Now, every resource calendar that gets added makes it that much slower to search in Outlook. This is because you must search by owner name and therefore, potentially return EVERY resource calendar in the system (and we have hundreds now and growing).
Also, when searching for the calendar in Outlook, it looks like Outlook is trying to set some property for EVERY resource calendar as a test for whether or not you can subscribe to it, in order to determine if you should see it or not in the list (it doesn't show calendars to which you cannot subscribe). So, it appears as if the following is happening in Outlook:
- It issues a search_calprops.wcap command with a search-string=<the calender owner entered by the user>
- It then appears to take every calendar that was returned and attempts to set some property on it as the user. So, now it is iterating through potentially hundreds of calendars trying to set a property and, failing on most since most users can't subscribe to most calendars. Here is a log snippet showing these attempts:
- Note that these errors went on for a period of over 2 minutes as evidenced by the log, all the while Outlook was hanging.
- It finally returns the list of calendars to which the user is allowed to subscribe (we assume for which the step above was successful).
Due to the fact that all resource calendars are owned by one user and then Outlook seems to iterate over every single calendar, it can take over 5 minutes for the search to return during busy hours. This causes a lot of frustration to the end user and causes many users to just quit/kill the search.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document