Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


Consider the following scenario:

  • You separately deploy Microsoft Exchange Server 2019 and Exchange Server 2016 on Windows Server 2019, Windows Server 2016 in the same organization.

  • You create a database availability group (DAG) and add one of the mailbox servers like Exchange 2016 mailbox server to the DAG first.

Unexpectedly, the Exchange 2019 mailbox server can also be added into the same DAG and vice versa. Two rules are violated here:

  • Exchange 2016 and Exchange 2019 should not be the member of same DAG.

  • Windows 2016 and Windows 2019 should not be the member of same DAG.

After you apply this update, the operation will fail and you will receive the following error message:

WARNING: The operation wasn't successful because an error was encountered.


This issue occurs because Exchange Server doesn't check to disallow Exchange Server 2019 and Exchange Server 2016 to exist in the same DAG.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


To fix this issue, install one of the following updates:For Exchange Server 2019, install the Cumulative Update 1 for Exchange Server 2019 or a later cumulative update for Exchange Server 2019.

For Exchange Server 2016, install the Cumulative Update 12 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.


Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!