Learn how to fix the error that occurs when uninstalling Exchange Server 2013 after upgrading to Exchange Server 2019. This article provides a simple solution and some FAQs.
Table of Contents
Problem
If you have recently upgraded your Exchange Server from 2013 to 2019, you might encounter an error when trying to uninstall the old version. This error can be frustrating and confusing, especially if you have already removed the old Exchange Server from the control panel, the Exchange Admin, and the Active Directory.
Detail error message as below:
The following error was generated when “$error.Clear();
if (Test-Path $RoleBinPath\ServiceControl.ps1)
{
& $RoleBinPath\ServiceControl.ps1 Start $RoleRoles.Replace(‘Role’,”).Split(‘,’);
& $RoleBinPath\ServiceControl.ps1 Remove;
}
” was run: “Microsoft.Exchange.Configuration.Tasks.ServiceNotInstalledException: Service ” isn’t installed on this server.
at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
at Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)”.
In this article, we will explain why this error happens and how to fix it in a few easy steps.
Why Does the Error Occur?
The error that occurs when uninstalling Exchange Server 2013 after upgrading to Exchange Server 2019 is caused by a mismatch between the registry and the actual state of the system. The uninstallation process tries to remove some components that are no longer present, and fails to complete the final step. This error does not affect the functionality of the new Exchange Server, but it can prevent you from freeing up some disk space and cleaning up the system.
How to Fix the Error?
The solution to this error is very simple: just click on “Exit” on the Exchange uninstaller and ignore the error message. This will close the uninstallation process and leave the system as it is. You do not need to worry about any leftover files or registry entries, as they will not interfere with the new Exchange Server or cause any performance issues. You can also delete the old Exchange Server’s VM if you do not need it anymore.
Frequently Asked Questions (FAQs)
Question: Is it safe to ignore the error message?
Answer: Yes, it is safe to ignore the error message, as it does not indicate any serious problem with the system. The error message is just a result of the uninstallation process trying to remove something that is not there.
Question: Will the error message affect the new Exchange Server?
Answer: No, the error message will not affect the new Exchange Server, as it is related to the old version only. The new Exchange Server will work normally and independently from the old one.
Question: How can I prevent the error message from happening again?
Answer: The error message will not happen again, as it is a one-time issue that occurs when uninstalling Exchange Server 2013 after upgrading to Exchange Server 2019. Once you exit the uninstallation process, you will not see the error message again.
Summary
In this article, we have discussed how to fix the error that occurs when uninstalling Exchange Server 2013 after upgrading to Exchange Server 2019. We have explained the cause of the error, the solution, and some FAQs. We hope this article has been helpful and informative for you. If you have any questions or feedback, please feel free to leave a comment below.
Disclaimer: This article is for informational purposes only and does not constitute professional advice. We are not responsible for any damages or losses that may result from following the instructions or suggestions in this article. Please consult a qualified IT expert before making any changes to your system.