This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 85%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERL%3C/text%3E%3C/svg%3E)
Exchange 2016 Build 15.1.225.42. Attempt to apply CU20 failed due to install asking for the "exchangeserver.msi" for the current build. Exchange was setup by previous IT and only performed monthly Windows updates. Unable to locate the .msi file and had to cancel the update. However, it caused Exchange to stop functioning even after restore all services and reboot. Last ditch effort to get Exchange back online, I restore Exchange from backup. Now, OWA and EAC are up and running, but unable to send/ receive. Outbound emails just stay in Outbox. Verified Send/ receive connectors are correct.
Thanks in advance.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 57.00000000000001%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESH%3C/text%3E%3C/svg%3E)
Had the same problem installing CU23 on a CU20 server - running from the CLI showed CU20 in the message - despite running setup from the Cu23 iso. The fact that it rejected the "_DiagnosticDataOFF" switch indicated that it was attempting to run CU20 setup*.* Turned out I had to run the update logged in as the same admin user that performed the previous upgrade
Correct, both internal and external mail flow stopped. I didn't have the time to wait for NDR from external user since the entire system was down and I had to get it back up and running ASAP.
I restore Exchange from Veeam backup. After restore, and roughly 30 minutes later, mail flow returned to normal.
So the only issue I'm facing now is the inability to patch Exchange to CU 20. Verified Exchange meet all required prerequisites including .NET 4.8. The install also passes
prerequisites analysis. Then it reaches Step 3 "Remove Exchange files" is when I ask for the "exchangeserver.msi". And if I point it to the "exchangeserver.msi" file from CU 20 ISO, it gives me the message that is not a valid installation package for the MS Exchange Server. At which point the only option is to cancel, then I get the following
Error:Couldn't remove product with code cd981244-e9b8-405a-9026-6aeb9dcef1f1. The installation source for this product is not available. Verify that the source exists and that you can access it. Error code is 1612.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
Hi @Roget Luo ,
Then it reaches Step 3 "Remove Exchange files" is when I ask for the "exchangeserver.msi". And if I point it to the "exchangeserver.msi" file from CU 20 ISO, it gives me the message that is not a valid installation package for the MS Exchange Server.
As it was in the Step 3 "Remove Exchange files" that you were asked for the "exchangeserver.msi", per my understand, here you would need to point it to the "exchangeserver.msi" file from the version you are currently running, that is the RTM(Build 15.1.225.42).
Please check if you still have the ISO file for the Exchange 2016 RTM, or you can see if it's possible to download it via VLSC, then mount it on the server, try it again to upgrade to CU 20, when prompted to choose the msi file in Step 3, point it to the "exchangeserver.msi" file located in the RTM's folder.
Well, this is the core of my issue. The previous IT didn't keep a copy of the ISO, and "exchangeserver.msi" is missing from the default install folder on the Exch server. And since this Build is so outdated, it's no longer available for download.
Hi @Roget Luo ,
Given this situation, then instead to trying to directly upgrade to CU 20 on this machine, you might need to consider building another Exchange server 2016 with CU 20, then move the mailboxes over there.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Roget Luo ,
Just checked in to follow up with this thread. Please post back at your convenience if we can assist further.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thanks for the suggestion, luckily I was able to locate a copy of the correct ISO from a contributor in another forum. Patched to the latest CU 20.
Happy to know that it has been resolved and thanks for your sharing :)
You can try to run the command from an elevated command prompt instead of a windows power shell. Also, in the command prompt, navigate to the network location of the Exchange 2016 installation files. You can take help from a similar thread -
Install with extracting the setup files to D:\Install\CU12, then ran the following command:
.\setup /mode:upgrade /iacceptexchangeserverlicenseterms
So copied the setup folder from the extracted folder: D:\Install\CU12 to C:\Program Files\Microsoft\Exchange Server\V15\bin** to make sure the setup folder with install files, then started the install again from the **D:\Install\CU12 folder, and then everything went fine and without a glitch.
I found the same forum post, however, changing the syntax of PS or CMD it didn't work for me. At the end, by luck, I discovered the missing "MSSpeech_SR_TELE.ca-ES.msi" was located in the c:\users\CurrentPatchInstaller\ directory. The CU install was looking for the .msi in the "OriginalExchangeInstaller" 's user profile.
Hopefully, this will help others who run into similar issue
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 30%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAC%3C/text%3E%3C/svg%3E)
This was my actual issue. I was still in PowerShell running the setup.exe / commands. This one that initiates the upgrade doesn't play well with PS. Command Prompt for the win!
Hi @Roget Luo ,
Now, OWA and EAC are up and running, but unable to send/ receive. Outbound emails just stay in Outbox.
Do you mean both the internal and external mail flow don't work now? If this is the case, is there any NDR message when an external user sends a mail to your organization?
By "restore Exchange from backup", do you mean you rebuilt the Exchange server from scratch?
Please have a check and ensure the Exchange related services are up and running. Also its' suggested to have a look at the Event Viewer and see if any relevant errors are recorded out there.
Regarding the missing "exchangeserver.msi" when you tried to upgrade to CU 20, would you please remove any personal information like domain name and then share the detailed error message so that we can help do further research on this?
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 98%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hi, for me this error came when trying to patch CU from PowerShell and not CommandPrompt. Once I did the command:
setup /m:upgrade /IAcceptExchangeServerLicenseTerms
from CMD (as admin) the error/warning went away.
(this was patching from CU19 to CU21 Exchange 2016)
Hope this helps, Sneaky_Pete