Answered by:
Error upgrading Exchange 2013 CU22 to CU23

Question
-
Hi all,
I encountered a long string of errors while trying to upgrade Exchange 2013 CU22 to CU23.
The Exchange server was already in maintence mode.
I have uploaded the errors in text document into my dropbox as it is too long to post here.
https://www.dropbox.com/s/k92d8qlpznsmxw6/Mailbox%20role%20mailbox%20service%20error.txt?dl=0
Will greatly appreciate it if anyone has any idea and can enlighten me where did it go wrong.
Stay safe and healthy guys. :)
Monday, June 1, 2020 9:42 AM
Answers
-
Hi porklegoguy,
According to the information your provided, I think this error is caused by your account not have permission to access the registry.
1. Please assign your account access to the registry.
There is a similar case you could refer to:Process execution failed with exit code 1 .
About how to change permissions in the registry :How to apply permissions to a Windows registry key.
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
2. In addition, please check the prerequisites .NET Framework, Visual C++ Redistributable Package and UCMA 4.0 correct.
Please note, some versions of .NET Framework support CU22 but not CU 23, please confirm the system requirements for installing Exchange 2013.
For more information: Exchange 2013 system requirements and Exchange 2013 prerequisites.
Regards,
Lucas Liu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
- Proposed as answer by Lucas_ LiuMicrosoft contingent staff Wednesday, June 3, 2020 8:35 AM
- Marked as answer by porklegoguy Friday, June 5, 2020 3:36 AM
Tuesday, June 2, 2020 7:26 AM
All replies
-
Hi porklegoguy,
According to the information your provided, I think this error is caused by your account not have permission to access the registry.
1. Please assign your account access to the registry.
There is a similar case you could refer to:Process execution failed with exit code 1 .
About how to change permissions in the registry :How to apply permissions to a Windows registry key.
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
2. In addition, please check the prerequisites .NET Framework, Visual C++ Redistributable Package and UCMA 4.0 correct.
Please note, some versions of .NET Framework support CU22 but not CU 23, please confirm the system requirements for installing Exchange 2013.
For more information: Exchange 2013 system requirements and Exchange 2013 prerequisites.
Regards,
Lucas Liu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
- Proposed as answer by Lucas_ LiuMicrosoft contingent staff Wednesday, June 3, 2020 8:35 AM
- Marked as answer by porklegoguy Friday, June 5, 2020 3:36 AM
Tuesday, June 2, 2020 7:26 AM -
Yes, checked and realized my ad account was wrongly shifted to a OU which contains a restricted registry access policy~
Thank you Lucas and the community!
Friday, June 5, 2020 3:39 AM -
Hi porklegoguy,
I’m pleased to know that the information is helpful to you.
Here I will provide a brief summary of this post so that other forum members could easily find useful information here:
1. Issue Symptom:
An error occurred during the Exchange upgrade, the error message is reported the "Process execution failed with exit code 1".
2. Cause:
This error is caused by user's account not have permission to access the registry
3. Solution:
Assign the user's account access to the registry
4. Reference Links:
How to apply permissions to a Windows registry key
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards,
Lucas Liu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Thursday, June 11, 2020 9:27 AM