Emerging Issues for Exchange On-Premises
This page lists emerging issues for Exchange On-Premises deployments, possible root cause and solution/workaround to fix the issues. The page will be consistently updated with new issues found and reflect current status of the issues mentioned.
| Updated on | Update causing the issue | Issue | Workaround/Solution |
|---|---|---|---|
| 2/24/2025 | Exchange Server 2019 CU14 OR Exchange Server 2019 Cumulative Update 15 | Environments that are using SSL offloading configuration may face issues with Outlook connectivity issues after upgrading to Exchange Server 2019 CU14 OR Exchange Server 2019 Cumulative Update 15 |
As announced in August 2023 , by default, starting with Exchange Server 2019 CU14, setup enables the Windows Extended Protection (EP) feature on the Exchange server being installed. Extended Protection isn't supported in environments that use SSL Offloading. SSL termination during SSL Offloading causes Extended Protection to fail. To enable Extended Protection in your Exchange environment, you must not be using SSL offloading with your Load Balancers. Please check this link for more details |
| 2/6/2025 | HCW | You may see following error when creating Migration Endpoint using HCW "The last connection attempt happened too recently" |
Please create the Migration Endpoint manually by following steps in this article while the issue is being fixed in HCW |
| 1/29/2025 | November Exchange Security Update for Exchange 2016 & Exchange 2019 V2 | You may see following error when installing November 2024 V2 Exchange Security Update: Error 1935. An error occurred during the installation of assembly 'Microsoft.Exchange.Data.Common,version="15.1.2503.00" ,fileVersion="15.1.2507.44",culture="neutral", publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL"'. For more information, refer to Microsoft Help and Support. HRESULT: 0x800700B7. assembly interface: IAssemblyCacheItem, function: Commit, component: {B79F9EB4-6D81-48F3-BC2D-3A0A83C30742} |
Please follow the workaround provided on this KB article |
| 11/29/2024 | November Exchange Security Update for Exchange 2016 & Exchange 2019 V2 | Time zone exception may be reported in event viewer , after installing the November Exchange Security Update for Exchange 2016 & Exchange 2019 V2 Event log entries are generated if Exchange Server fails to process calendar information, such as: w3wp#MSExchangeOWAAppPool, M.Exchange.Net , M.E.E.ExIanaTimeZoneProvider+Cache.AddTimeZone , M.E.ExchangeSystem.InvalidTimeZoneException OR Microsoft.Exchange.ExchangeSystem.InvalidTimeZoneException: Time zone id already exists |
Please follow the workaround provided on this KB article |
| 11/27/2024 | November Exchange Security Update for Exchange 2016 & Exchange 2019 | Exchange Transport Rules may stop working after applying the November Exchange Security Update for Exchange 2016 & Exchange 2019 | Please install the re-released November 2024 Exchange security update |
| 9/11/2024 | August 2024 update for Windows | After installing the August 2024 update for Windows 1) Microsoft Exchange Transport service may start crashing 2) Microsoft Filtering Management Service may not start or start with long delay |
Update on 9/11/2024 Install Windows Update for September 2024 or later Old information Please follow steps in this KB |
Old issues
| Updated on | Update causing the issue | Issue | Workaround/Solution |
|---|---|---|---|
| 4/23/2024 | March 2024 Security Update for Exchange 2019,2016 | After installing the March 2024 Security Update, Search in Outlook (cached mode) may show "We're having trouble fetching results from the server...". The search works fine in OWA or Outlook online mode. |
Please install April 2024 Hotfix Update |
| 4/23/2024 | March 2024 Security Update for Exchange 2019,2016 | After installing the Security Update, add-ins may stop working with following error "Add-in Error Something went wrong and we couldn't start this add-in. Please try again later or contact your system administrator |
Please install April 2024 Hotfix Update |
| 4/23/2024 | March 2024 Security Update for Exchange 2019,2016 | After installing the March 2024 Security Update, Unread envelope icon is not getting updated |
Please install April 2024 Hotfix Update |
| 4/23/2024 | March 2024 Security Update for Exchange 2019,2016 | After installing the March 2024 Security Update, preview of Office documents in OWA may fail with error "Sorry, there was a problem and we can't open this document." |
Please install April 2024 Hotfix Update |
| 2/19/2024 | CU 14 for Exchange 2019 | Exchange 2019 CU14 RecoverServer fails while creating "New-PushNotificationsVirtualDirectory" with following error: Exception setting "ExtendedProtectionTokenChecking": "Cannot convert null to type "Microsoft.Exchange.Data.Directory. SystemConfiguration.ExtendedProtectionTokenCheckingMode" due to enumeration values that are not valid. |
Please follow the steps from this KB to resolve the issue |
| 11/23/2023 | November 2023 Security Update for Exchange 2016, Exchange 2019 | Some customers may find queue viewer crashing with error "Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints" |
The error can occur if the Exchange server auth certificate has expired. Solution is to renew the Exchange server auth certificate manually or by using this script |
| 10/12/2023 | All versions of August 2023 Security Update for Exchange 2016, Exchange 2019 | Users in account forest can't change expired password in OWA in multi-forest Exchange deployments after installing any version of August 2023 Security Update for Exchange servers Note The account forest user will be able to change the password after they sign in to Outlook on the web if their password is not yet expired. The issue affects only account forest users who have passwords that are already expired. This change does not affect users in organizations that don't use multiple forests. |
** Update on 10/12/2023 ** Follow steps on this article |
| 8/15/2023 | Non-English August 2023 Security Update for Exchange 2016, Exchange 2019 | When you install the Microsoft Exchange Server 2019 or 2016 August 2023 Security Update (SU) on a Windows Server-based device that is running a non-English operating system (OS) version, Setup suddenly stops and rolls back the changes. However, the Exchange Server services remain in a disabled state. |
The latest SUs have been released that do not require a workaround to install. If you used a workaround to install KB5029388, it is highly recommend to uninstall the KB5029388 to avoid issues down the line. For more information please check out this KB. |
| 6/15/2023 | January 2023 Security Update for Exchange 2016, Exchange 2019 | When you try to uninstall Microsoft Exchange Server 2019 or 2016 on servers , that had January 2023 Security Update for Exchange Server installed at any point, the Setup fails with following error message: [ERROR] The operation couldn't be performed because object ' be found on ' |
Install Exchange Security Update June 2023 or higher to resolve the issue. Check this KB for more details |
| 6/15/2023 | Extended protection enabled on Exchange server | Changing the permissions for Public Folders by using an Outlook client will fail with the following error, if Extended Protection is enabled: The modified Permissions cannot be changed. |
Install Exchange Security Update June 2023 or higher Security Update and create the setting override mentioned in this KB |
| 3/16/2023 | Outlook client update for CVE-2023-23397 released | These vulnerabilities affect Exchange Server. Exchange Online customers are already protected from the vulnerabilities addressed in these SUs and do not need to take any action other than updating Exchange servers in their environment, and if applicable, installing the security update for Outlook on Windows described on the link on the right. More details about specific CVEs can be found in the Security Update Guide (filter on Exchange Server under Product Family). Awareness: Outlook client update for CVE-2023-23397 released There is a critical security update for Microsoft Outlook for Windows that is required to address CVE-2023-23397. To address this CVE, you must install the Outlook security update, regardless of where your mail is hosted (e.g., Exchange Online, Exchange Server, some other platform). |
Please check this page for FAQs about the Outlook CVE-2023-23397 |