ARCHIVED: Known issues for Exchange 2013 at IU
| Issue | Description | Status | Last updated |
|---|---|---|---|
| Shared calendars cannot be viewed in Outlook Mobile. | Microsoft does not support the ability to view shared calendars in Outlook Mobile for Exchange 2013. However, you can view shared calendars in Exchange Online. For more, see How to have a shared calendar with on premise Exchange viewable with Outlook mobile app? | Known issue | December 7, 2020 |
| When sharing files from Microsoft OneDrive at IU, email notifications about the share will not be sent to the recipient of the invitation if the sender is on Exchange 2013. | If the person sharing files has an Exchange account on Exchange 2013, an email notification will not be sent to the recipient of the sharing invitation. The permissions to the file or folder will still be added for the recipient. This was resolved by resolving an issue that was causing notifications to be flagged as spam. | Resolved | September 7, 2020 |
| Certain methods of accessing Exchange have attachment size limits lower than 50 MB |
In OWA, attaching a file greater than 25 MB will result in the error, "The following files couldn't be attached: [filename]. Please try again later." However, any file greater than 25 MB will always fail to attach in OWA. For ActiveSync, the method most mobile devices use to connect to Exchange, the size is limited to 10 MB. Some devices and programs have their own built-in limits that may reduce this further. |
Known issue | November 29, 2018 |
| If an Exchange account is configured in an IMAP client or certain ActiveSync clients, or if a message is read with OWA, read receipts may be sent regardless of settings. | If a message is read in an IMAP client and a read receipt was requested by the sender, the read receipt will be sent regardless of the read receipt preferences set in the client and on the Exchange account. This can also occur with some ActiveSync connections. A workaround that allows reading the message without sending a receipt in some IMAP clients is to read the message in plain text mode only. | Known issue | November 19, 2018 |
| Unable to add Internet calendars using a URL in OWA |
In OWA, if you go to the tab, right-click , select , and then try to add a calendar using the URL to a calendar feed, you will get this error: "Couldn't open calendar. The Internet calendar address isn't formatted correctly". As workaround, you can add the calendar using an Outlook client instead, but the calendar will appear only in Outlook clients that have the account added, not in OWA. |
Known issue | July 26, 2018 |
| Some browsers do not handle credentials in a way that allows login |
When logging into OWA, you may get a message that an error occurred. This is known to affect Firefox in private mode, Brave in any mode, and Chrome in any mode. |
Expected behavior | September 15, 2020 |
| Unable to access options page from OWA |
When you follow a link to OWA from another page and select , you may get an error that requires you to close the tab/window to get out of OWA.
To resolve this issue, type |
Expected behavior | November 2, 2017 |
| Some users cannot access their Exchange mailboxes via desktop or mobile clients; OWA displays the error "HTTP 400 - Bad Request (Request Header too long)". | This can occur if you are a member of many Active Directory user groups (approximately 120 primary groups, or 1,015 primary and nested groups). To resolve the issue, reduce the number of AD groups in which you are a member. For more, see Problems with Kerberos authentication when a user belongs to many groups in Microsoft's online support documentation. | Expected behavior | June 16, 2017 |
| Some file attachments cause email delivery to fail. | Certain file attachments will cause email delivery to fail and you'll receive a bounced email message with the error "Remote Server returned '554 5.6.0 Invalid message content'". Certain file attachments have embedded objects that are incompatible with the Exchange 2013 email security file scanning mechanism. Types of files that may cause this issue include, but are not limited to, some PDFs and Excel spreadsheets. Workarounds include zipping and password protecting the file before attaching it, or using an alternative service like Slashtmp or one of the services listed in Options for storing files at IU. | Known issue | October 16, 2015 |
| In Conversations view, Outlook on the web does not provide preview text or a Reading Pane view for any digitally signed (S/MIME) email message. | If you use Conversations view in Outlook on the web, preview text and Reading Pane view are not available for digitally signed (S/MIME) email. To read a digitally signed message, you must open it in a new window. Turning off Conversations view enables normal preview and Reading Pane functionality for S/MIME messages. You can enable preview text in Conversations view by installing the Microsoft S/MIME Active X Control plug-in and restarting your browser; however, Reading Pane functionality for encrypted messages cannot be enabled in Conversations view. | Resolved | May 20, 2022 |
| Some mail-enabled groups cannot be managed from OWA. |
Managers may find some older mail-enabled groups can no longer be edited from Outlook. To request help with this problem, contact your IT Pro. |
Known issue | August 5, 2015 |
| Manually configured Exchange profiles do not work. They configure without problems, but display an error and refuse to open when you launch Outlook. |
If you manually configure your profile in
Outlook after the migration to Exchange 2013 and then launch
Outlook, you will get an error due to the way Exchange now handles server names. In
Outlook 2013 the error message is:
"Cannot start Microsoft Outlook. Cannot open the Outlook Window. The set of folders cannot be opened. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)." In older versions the error message is: "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your offline folder file." Exchange 2013 no longer lets a profile use an FQDN as the server name. Instead, a "connection point" is created that consists of your mailbox GUID and email domain. That connection resembles: a53e98e4-0197-4513-be6d-49836e406aaa@iu.edu
Thus, you can no longer use Profiles configured manually before the Exchange 2013 migration are not affected by this. For more, see Manual Outlook configuration with Exchange 2013. |
Expected behavior | July 23, 2015 |
| The OWA URL changed to https://mail.iu.edu/. | This is a deliberate change to simplify the URL. | Expected behavior | June 9, 2015 |
| The OWA login page looks very different. | The OWA login page has been redesigned to bring it more in line with standard IU branding. | Expected behavior | April 28, 2015 |
|
For some users after the upgrade is complete,
Skype for Business 2015 will display an error: "The Exchange server won't let us connect. We're working on fixing the connection. Your history, voice mail and
Outlook features might be unavailable or out-of-date until things are fixed."
There is no pattern for whom this affects. |
Delete your SIP profile folder in
sip_dvader@iu.edu After that, restart Skype for Business. |
Resolved | July 22, 2015 |
| Duplicate Contacts and Junk E-Mail folders | After migrating to Exchange 2013, a duplicate Contacts folder and an additional folder called Junk E-mail were visible. This has been fixed with a cumulative update issued by Microsoft. | Resolved | July 7, 2015 |
This is document bfnk in the Knowledge Base.
Last modified on 2021-09-07 17:08:11.