Resolve mail flow issues with Exchange Server 2013 after failed Exchange SP1 upgrade

I received a request recently to upgrade a client Exchange 2013 Server, which is the RTM version [15.0 (Build 516.32)] to SP1 [ Build no – 15.00.0847.032].

The set up was downloaded to the local Exchange Server at first. The latest updates were installed on the server. Tried the installation from the setup.exe file. However, the installation got stuck at 90 % of the readiness checks. Hence, had to re-initiate the unattended installation from command prompt which too resulted in error during the pre-requisite checks. The error reported was as follows :


Tried rebooting the server once or twice but issue reoccurred. As per the Microsoft technet link “” checked on the following registry keys :

  1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile
  2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

However, I was unable to locate the keys in my server. Might be because I am using Windows Server 2012. Hence, had to manually create the registry keys and set the value as below:

  1. Navigated to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
  2. Created the key Updates with a string value UpdateExeVolatile 
  3. The value of the string value was set to 0 [ indicates that system restart is not required ]

But still after performing the above changes,issue persisted. Since the office hours was above to start, I stopped working on the upgrade and checked the mail flow on the server. Unfortunately, due to my bad luck the mail flow was not working. 😦

The emails kept pending on the drafts folder in the mailbox. Following troubleshooting steps were performed on the server :

  • Checked the email queue in the Exchange server, but no pending emails were found
  • Restarted Microsoft Exchange Services and rebooted the exchange server
  • Checked the event log errors
  • Executed the command “Get-ServerComponentState ServerName” and got the following result


All the Exchange components were found to be inactive in background even though the Exchange services were found to be started in the Services.

  • Navigated to the following registry location


\v15\SERVERCOMPONENTSTATES and confirmed that the status of the components were down.


In the above figure; HealthApi is the Requester; in the data field 1:0:, 0 indicates that the service is down

Some services also uses another Requester which is Functional


  • Tried executing the command in EMS “Set-ServerComponentState -ID SERVERNAME -Component ServerWideOffline -State Active -Requester HealthApi” & “Set-ServerComponentState -ID SERVERNAME -Component ServerWideOffline -State Active -Requester Functional
  • Checked the status again using the command : “Get-ServerComponentState ServerName
  • Checked and confirmed that the component status changed to Active
  • Restarted the Exchange services and confirmed the mail flow


Reference Links :

  1. Checked the link



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s