As so many times, you may have tried to upgrade Exchange to a new Cumulative Update (CU), find the newest here : Exchange Server build numbers and release dates
You download, you install, it completes etc. and you’re good!
Great!
But with Exchange 2013 CU22 and CU23, things go otherwise, you download, you install, it comp….FAIL! :
[02-17-2019 09:32:58.0051] [1] [ERROR] Fatal error during installation
[02-17-2019 09:32:58.0051] [1] [ERROR] Installing product C:\Exchange Install\Exchange2013Cu22\exchangeserver.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘Error reading from file: C:\Exchange Install\Exchange2013Cu22\Setup\Perf\ApaAgentPerfCounters.h. Verify that the file exists and that you can access it.’.
[02-17-2019 09:32:58.0051] [1] [ERROR] Fatal error during installation
[02-17-2019 09:32:58.0066] [1] [ERROR] Installing product C:\Exchange Install\Exchange2013Cu22\exchangeserver.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘Error reading from file: C:\Exchange Install\Exchange2013Cu22\Setup\Perf\ApaAgentPerfCounters.h. Verify that the file exists and that you can access it.’.
[02-17-2019 09:32:58.0066] [1] [ERROR] Fatal error during installation
[02-17-2019 09:32:58.0098] [1] Ending processing install-msipackage
[02-17-2019 09:33:12.0306] [0] CurrentResult setupbase.maincore:396: 0
[02-17-2019 09:33:12.0306] [0] End of Setup
Now what is that all about?
You have been left with a broken Exchange server, a sunken ship 🙁
Some people have tested and written about all this, and the solution is actually simple!:
Map a network share on another server, copy the CU22 or CU23 files into there, and just run it, from the command prompt:
\\<servername>\c$\temp\ex2013cu22\setup.exe /Mode:Upgrade /IAcceptExchangeServerLicenseTerms
And it completes, or at least should do 🙂
If you want to read more about this issue, you may check the following links:
In Danish:
Related Posts
Office 365: Users in a hybrid deployment can’t access a shared mailbox that was created in Exchange Online
Exchange 2013/2016 Server Component State Inactive (IMAP)- Enable-RemoteMailbox –ExchangeGuid is mandatory on UserMailbox
Exchange: Add the Exchange PowerShell module into a standard PowerShell session- Exchange Server 2019 on Windows Server 2019 Core
- Exchange powershell: Add transport rule to add [EXT] word to all external mails
Will this work for error code 5 as well. Was at the finalization step when it failed. Out of 5 servers updated this server is only one that failed.
Totally annoyed why this started happening – it was always a next-click-next installation :-O
OMG…. So so happy I found your blog. Had the same error with Cu23. The fix solved it for me. The weekend with the family is savede.
Thanks – So glad to hear that 😉