Outlook cannot open item (Calendar Invite)
Try adding the below reg key. I had a similar issue that this resolved.
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Options\Calendar\ DWORD: AllowHTMLCalendarContent Value:1
Related videos on Youtube
user5870571
Administer the following Operating Systems: Windows 2000, Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10, Windows NT 4.0 Server, Windows Server 2000, Windows Server 2003, Windows Server 2008, Windows Server 2012, Windows Server 2016, Windows Server 2019, Ubuntu, Debian, Fedora Program in the following languages: PHP, HTML, VB.NET, PowerShell, AutoIT
Updated on September 18, 2022Comments
-
user5870571 over 1 year
We are having a strange problem using calendar invites where if the client is using cached Exchange mode and they open a calendar invite sent from another user on the same Exchange server they can open the calendar invite, but if the client is not using cached Exchange mode and they try to open the calendar invite they get the message "Outlook cannot open item: Subject".
We have already tried deleting temporary files and that did not fix the problem.
We sent a calendar invite from another domain to someone in the domain with this issue and they were able to open the calendar invite with a client using cached Exchange mode and with a client not using cached Exchange mode.
We will take a closer look at the Exchange server to see if "Rooms" or other Resource Mailboxes are involved but wanted to see if anyone had some different ideas.
The Exchange server is Exchange Server 2010 (fully patched) and multiple employees have this problem with Outlook 2013 and Outlook 2016.
Update 1
We do not believe it is related to Resource Mailboxes because not every calendar invite that has this problem is related to a Resource Mailbox.
-
Admin about 7 years@yagmoth555 sorry for the delay. Yes, the problem still happens.
-
-
user407833 about 7 yearsI did not try HKLM just HKCU and deployed via GP once the solution was verified.
-
user5870571 about 7 yearsGood enough it took care of the problem. Thank you!