Exchange Server 2013 CU14 and Exchange Server 2016 CU3 Issues

Microsoft released Exchange Server 2013 CU14 in september and issues that are being addressed by Exchange 2013 CU14 are listed here. Along with Exchange server 2013 CU14, Microsoft also released CU3 of Exchange 2016. Implementation of these updates in production has caused issues with database content index failure. Both the updates were released in September of this year.

I have experienced this issue with Exchange 2016 CU3 implementation and a lot of customers has reported the same issue on Microsoft TechNet forum as well for Exchange Server 2013 CU14. Working with Microsoft support ticket, it has been reported back that a bug has already been acknowledged and for now, the solution is to deploy a new Exchange server 2013 CU13 or Exchange Server 2016 CU2 and move all user mailboxes to new server. Although, it’s the ugly workaround but for now we have to do this or I would say, we shouldn’t upgrade our Exchange implementation to current CU until a fix is being released by Microsoft.

Being a consultant, I will not recommend you to deploy Exchange Server 2013 CU14 or Exchange Server 2013 CU3 in your production environment until we have a fix for this bug.

If you are experiencing the same issue in your exchange organization, I would highly recommend to open a support ticket with Microsoft and let them know that you are also impacted with the issue. With content indexing failing on database, you’ll also see the following event ID on your server.

Watson report about to be sent for process id: 28160, with parameters: E12IIS, c-RTL-AMD64, 15.00.1236.003, M.E.Search.Service, M.E.Data.Directory, M.E.D.D.ScopeSet.GetOrgWideDefaultScopeSet, System.ArgumentNullException, 301, 15.00.1236.000.
ErrorReportingEnabled: False

This issue is widely reported by many organizations and I highly recommend to test Exchange updates in dev environment thoroughly before rolling out the changes to your production exchange server.