Hi All,
Just asked this question over in the office forum but was told it would be best for me to post it here instead.
We have an issue in a clients environment with Outlook and Exchange playing up with calendar invites and corrupting reoccurring calendar appointments.
I will break down the scenario in detail below (sorry for the long post).
For the sake of discussion we have Jill who is the PA for Kate.
Jill has shared access to Kate's calendar and inbox so that she can accept and create meeting requests and move existing ones.
The issue comes about when Jill creates a reoccurring calendar appointment like a meeting. The meeting will display fine in Jill's outlook and you can open the meeting and read all the information from inside of it without any issues.
When Jill adds Kate in as a member of the meeting then Kate will receive the email to accept the meeting request, if she tries to accept the meeting request from Kate's inbox it will prompt with an error saying "Cannot open this item. The operation
failed. An object cannot be found."
Upon closing the error the appointment still appears in Kate's calendar with Kate accepting it as tentative.
The second part of this is that you can open the calendar appointments for the reoccurring meeting fine but should you move any of the reoccurring entries for the meeting (say if you had to move the meeting forward or backwards one week) then you
will no longer be able to open that calendar entry and it just displays an error message saying that the file can't be found.
The original setup when this initially happened was as follows:
* Outlook 2010 on physical computer
* Exchange 2010
Recently implemented setup that is now in use and the problem still occurs:
* Outlook 2016 via Citrix on thin client
* Exchange 2010
From the testing that I have done I believe it is either something with the OST/PST file that is created for the users profile or communication to the Exchange server not updating changes correctly. Happy to provide logs or additional details to
solve this issue!!
Thanks in advance for any assistance,
Ben