locked
kb3124557 broke Exchange 2016 ALL services disabled RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Anyone else found this issue this morning?

    Follows patch Tuesday

    Robbie

    Wednesday, January 13, 2016 9:35 AM

Answers

  • Question
    Sign in to vote
    4
    Sign in to vote

    Dear Robbie,

    I found this thread after experiencing the exact same problem.

    We were updating our Windows 2012 R2 server with Exchange 2013. When the security update KB3124557 started installing it disabled a lot of services on it's own! Because my colleagues could use Outlook anymore we cancelled the update but that didn't do anything. A restart didn't help either.

    We then installed the update once more via Windows Update. Luckily the installation was complete after about 30 minutes and we restarted the server once more. After the restart the services were still down so we checked the log to see which services were affected. We enabled all the services and now the Exchange server is working again.

    First we enabled these services:

    Windows Management Instrumentation
    World Wide Web Publishing Service
    Tracing Service for Search in Exchange
    Remote Registry
    Performance Logs & Alerts
    IIS Admin Service
    Application Identity
    Microsoft Filtering Management Service

    After that we enabled these services:

    Microsoft Exchange Unified Messaging
    Microsoft Exchange Transport Log Search
    Microsoft Exchange Transport
    Microsoft Exchange Throttling
    Microsoft Exchange Service Host
    Microsoft Exchange Search Host Controller
    Microsoft Exchange RPC Client Access
    Microsoft Exchange Replication
    Microsoft Exchange POP3
    Microsoft Exchange Mailbox Transport Submission
    Microsoft Exchange Mailbox Replication
    Microsoft Exchange Mailbox Assistants
    Microsoft Exchange Information Store
    Microsoft Exchange IMAP4
    Microsoft Exchange Health Manager
    Microsoft Exchange Frontend Transport
    Microsoft Exchange Search
    Microsoft Exchange EdgeSync
    Microsoft Exchange Diagnostics
    Microsoft Exchange Mailbox Transport Delivery
    Microsoft Exchange DAG Management
    Microsoft Exchange Anti-spam Update
    Microsoft Exchange Active Directory Topology

    Some services need other services to work, so if a service doesn't want to start, check which other services it needs and start them first.

    Good luck everybody

    • Proposed as answer by Johan Petri Wednesday, January 20, 2016 11:54 AM
    • Marked as answer by GPP Tech Wednesday, January 20, 2016 1:21 PM
    Wednesday, January 20, 2016 11:53 AM
  • Question
    Sign in to vote
    2
    Sign in to vote

    No need to remove the update. Re-apply it won't fix the service issue

    THEN re-enable all exchange services to automatic(make a note of pop3 and imap they need to be manual if you don't use them)

    Also automatic for worldwide web publishing service, iis admin service and application identity

    Reboot then all will be good

    Robbie

    • Marked as answer by GPP Tech Wednesday, January 20, 2016 1:21 PM
    Thursday, January 14, 2016 2:26 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi!

    You had bad install.It is normal that services are disabled during install and then re-enabled after install complete.

    I would reinstall msp patch.

    BR,

    G

    • Proposed as answer by Cedric Ch Monday, January 18, 2016 3:22 PM
    Wednesday, January 13, 2016 11:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Reinstall also didn't work. We reset the services manually. We did miss IIS and W3C first time round as they were also disabled

    [05:25:00] [Warning] 'AppIDSvc' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'FMS'.
    [05:25:00] [Warning] 'FMS' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'hostcontrollerservice'.
    [05:25:00] [Warning] 'hostcontrollerservice' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'IISAdmin'.
    [05:25:00] [Warning] 'IISAdmin' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeADTopology'.
    [05:25:00] [Warning] 'MSExchangeADTopology' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeAntispamUpdate'.
    [05:25:00] [Warning] 'MSExchangeAntispamUpdate' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeDagMgmt'.
    [05:25:00] [Warning] 'MSExchangeDagMgmt' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeDelivery'.
    [05:25:00] [Warning] 'MSExchangeDelivery' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeDiagnostics'.
    [05:25:00] [Warning] 'MSExchangeDiagnostics' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeEdgeSync'.
    [05:25:00] [Warning] 'MSExchangeEdgeSync' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeFastSearch'.
    [05:25:00] [Warning] 'MSExchangeFastSearch' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeFrontendTransport'.
    [05:25:00] [Warning] 'MSExchangeFrontendTransport' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeHM'.
    [05:25:00] [Warning] 'MSExchangeHM' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeIMAP4'.
    [05:25:00] [Warning] 'MSExchangeIMAP4' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeIS'.
    [05:25:00] [Warning] 'MSExchangeIS' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeMailboxAssistants'.
    [05:25:00] [Warning] 'MSExchangeMailboxAssistants' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeMailboxReplication'.
    [05:25:00] [Warning] 'MSExchangeMailboxReplication' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangePOP3'.
    [05:25:00] [Warning] 'MSExchangePOP3' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeRepl'.
    [05:25:00] [Warning] 'MSExchangeRepl' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeRPC'.
    [05:25:00] [Warning] 'MSExchangeRPC' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeServiceHost'.
    [05:25:00] [Warning] 'MSExchangeServiceHost' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeSubmission'.
    [05:25:00] [Warning] 'MSExchangeSubmission' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeThrottling'.
    [05:25:00] [Warning] 'MSExchangeThrottling' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeTransport'.
    [05:25:00] [Warning] 'MSExchangeTransport' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeTransportLogSearch'.
    [05:25:00] [Warning] 'MSExchangeTransportLogSearch' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'MSExchangeUM'.
    [05:25:00] [Warning] 'MSExchangeUM' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'pla'.
    [05:25:00] [Warning] 'pla' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'RemoteRegistry'.
    [05:25:00] [Warning] 'RemoteRegistry' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'SearchExchangeTracing'.
    [05:25:00] [Warning] 'SearchExchangeTracing' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'W3Svc'.
    [05:25:00] [Warning] 'W3Svc' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'WinMgmt'.
    [05:25:00] [Warning] 'WinMgmt' did not exist, this is not an error as the sevice might have just been installed
    [05:25:00] Enabling service 'wsbexchange'.
    [05:25:00] [Warning] 'wsbexchange' did not exist, this is not an error as the sevice might have just been installed

    Wednesday, January 13, 2016 11:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    What if you uninstall update, reboot and then reinstall it?
    Wednesday, January 13, 2016 12:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I installed this security update for exchange 2016 and went well.

    This update will stop and disable all necessary services during setup, after setup, it will re-enable and start services automatically. Your update file could be corrupted, I suggest to re-download this update file from here to take a test, uninstall update and reboot system first.

    Meanwhile, please check C:\ExchangeSetupLogs\ServiceControl.log for service events

    Best Regards.

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Lynn-Li
    TechNet Community Support

    • Proposed as answer by TonyLeef Thursday, December 14, 2017 2:07 AM
    Thursday, January 14, 2016 8:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We redownloaded and reinstalled same problem. The first update was an automatic one

    In the end we manually enabled and started the services

    Thursday, January 14, 2016 10:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Same problem here. All services disabled after a succesfull install. When enabling all services ECP is still not available. Inbound mailflow also not working. Outbound mailflow works. Currently removing the update.
    Thursday, January 14, 2016 12:17 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    No need to remove the update. Re-apply it won't fix the service issue

    THEN re-enable all exchange services to automatic(make a note of pop3 and imap they need to be manual if you don't use them)

    Also automatic for worldwide web publishing service, iis admin service and application identity

    Reboot then all will be good

    Robbie

    • Marked as answer by GPP Tech Wednesday, January 20, 2016 1:21 PM
    Thursday, January 14, 2016 2:26 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Its hosed my exchange. I have mine virtualised and had to go back to the backup prior to the update. Thank goodness I have it both virtulaised and a backup because despite comparing the list of services to another backup I have here and making them identical, it still failed to function correctly.

    Seems to be alot of poor updates coming from MS in the last 3 months KB3114409 has kept me busy since Dec.

    Terry

    Saturday, January 16, 2016 1:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Similar issues here.  KB3124557 failed, then was successful but services were still down.  After the manual StartupType change--still nothing.  Restored from a replica.  We were on 2013 CU10 at the time.
    Saturday, January 16, 2016 1:15 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi, I had the same problem yesterday. After the update they were set up and launched services including disabled IIS. Then as ECP began re configure the path in the IIS ASP.NET binaries. Its value is changed based on environment variables“%ExchangeInstallDir%bin;%ExchangeInstallDir%bin\CmdletExtensionAgents;%ExchangeInstallDir%ClientAccess\Owa\bin” by "C: \ Program Files \ Microsoft \ Exchange Server \ V15 \ bin; C: \ Program Files \ Microsoft \ Exchange Server \ V15 \ bin \ CmdletExtensionAgents; C: \ Program Files \ Microsoft \ Exchange Server \ V15 \ ClientAccess \ Owa \ bin ".
    Tuesday, January 19, 2016 12:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a 2012 R2 server running Exchange 2013 SP1 with Symantec Mail Security installed.  The update failed and disabled all of the Exchange services and a few others.  I was able to set the services back to how they were by looking through the event log to see what was changed.  I set everything back and started services to confirm Exchange was working again.

    I tried to download the patch from Microsoft instead of through Windows Update, and it got to the point where it said it was stopping services and then bombed out with an error.  The weird thing is that it did not seem mark services as disabled as it did the first time.  I could not find any logs to show me anything specific to what was happening.  I did see in the Windows Update log the error 0x80070643

    A 3rd attempt did the same thing as the second.  I don't know what else to do but assume to mark this update as hidden and move on.

    Tuesday, January 19, 2016 9:48 PM
  • Question
    Sign in to vote
    4
    Sign in to vote

    Dear Robbie,

    I found this thread after experiencing the exact same problem.

    We were updating our Windows 2012 R2 server with Exchange 2013. When the security update KB3124557 started installing it disabled a lot of services on it's own! Because my colleagues could use Outlook anymore we cancelled the update but that didn't do anything. A restart didn't help either.

    We then installed the update once more via Windows Update. Luckily the installation was complete after about 30 minutes and we restarted the server once more. After the restart the services were still down so we checked the log to see which services were affected. We enabled all the services and now the Exchange server is working again.

    First we enabled these services:

    Windows Management Instrumentation
    World Wide Web Publishing Service
    Tracing Service for Search in Exchange
    Remote Registry
    Performance Logs & Alerts
    IIS Admin Service
    Application Identity
    Microsoft Filtering Management Service

    After that we enabled these services:

    Microsoft Exchange Unified Messaging
    Microsoft Exchange Transport Log Search
    Microsoft Exchange Transport
    Microsoft Exchange Throttling
    Microsoft Exchange Service Host
    Microsoft Exchange Search Host Controller
    Microsoft Exchange RPC Client Access
    Microsoft Exchange Replication
    Microsoft Exchange POP3
    Microsoft Exchange Mailbox Transport Submission
    Microsoft Exchange Mailbox Replication
    Microsoft Exchange Mailbox Assistants
    Microsoft Exchange Information Store
    Microsoft Exchange IMAP4
    Microsoft Exchange Health Manager
    Microsoft Exchange Frontend Transport
    Microsoft Exchange Search
    Microsoft Exchange EdgeSync
    Microsoft Exchange Diagnostics
    Microsoft Exchange Mailbox Transport Delivery
    Microsoft Exchange DAG Management
    Microsoft Exchange Anti-spam Update
    Microsoft Exchange Active Directory Topology

    Some services need other services to work, so if a service doesn't want to start, check which other services it needs and start them first.

    Good luck everybody

    • Proposed as answer by Johan Petri Wednesday, January 20, 2016 11:54 AM
    • Marked as answer by GPP Tech Wednesday, January 20, 2016 1:21 PM
    Wednesday, January 20, 2016 11:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Same to us ! This failed Update killed our single Hyper-V-virtualized Exchange 2013 CU11 ! We were not able to bring back the services up again, especially the Transport-Service.

    I'm not sure but it think corrupted the Microsoft Filtering-Management-service, which is needed for the transport-service.

    So we used our ntbackup to restore the complete server.


    Wednesday, February 3, 2016 12:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Looks similar to problems with similar update for CU9 a few months ago.. Security updates for CU required a path to setup files for some reason. And when it can't find the setup, update fails, and services are not re-enabled/started. http://evotec.pl/exchange-2013-cu9-kb3087126-installation-goes-bad/

    Wish MS would fix their updating mechanism so security updates won't require setup files and won't bring down Exchange every month..

    Friday, February 5, 2016 7:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have had the services go down twice, found the customer had automatic updates configured. Is it recomended to remove this update if it appears to of installed eventually?

    Monday, March 7, 2016 11:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    MS hasn't retracted this or the older cumulative update so i think it is still recommended to update (actually it fixes various security issues with OWA and other stuff). My service provider was able to install this update. So it is doable, but one has to take some precautions while doing it. At least to have Exchange installation files at hand to point to them if update asks for it (for some unthinkable reasons only MS engineers can program..).
    Tuesday, March 8, 2016 7:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    That is strategy. Microsoft wants you to go to office365. But otherwise, their services are offline often enough.

    It's just everything to laugh about. So much money, so little quality...

    This said, you should always have a double-checked backup from your vm you can recover if one of the updates fails. And if you listen to MS, you have at least a DAG and so you won't have to worry about anything ;-)

    Friday, March 18, 2016 12:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I add the same problem and your solution works for me.

    Thank you

    Wednesday, June 15, 2016 9:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Issue occurred again today with the latest patch KB3150501

    I think servicecontrol.ps1 has an issue

    05:39:30] * ServiceControl.ps1: 15/06/2016 05:39:30
    [05:39:30] Performing service control with options:
    [05:39:33] Adding to installed roles list: AdminTools
    [05:39:33] Adding to installed roles list: ClientAccessMailboxRole
    [05:39:33] Adding to installed roles list: Gateway
    [05:39:33] Adding to installed roles list: Mailbox
    [05:39:33] Adding to installed roles list: Bridgehead
    [05:39:33] Adding to installed roles list: Mailbox
    [05:39:33] Adding to installed roles list: UnifiedMessaging
    [05:39:33] Enabling services for the following roles: AdminTools ClientAccess Gateway FrontendTransport Bridgehead Mailbox UnifiedMessaging
    [05:39:33] Enabling services for 'AdminTools ClientAccess Gateway FrontendTransport Bridgehead Mailbox UnifiedMessaging'...
    [05:39:33] Reading service registry data from 'C:\ExchangeSetupLogs\ServiceStartupMode.xml'
    [05:39:33] Loaded state for 0 services registry
    [05:39:33] Enabling service 'AppIDSvc'.
    [05:39:33] [Warning] 'AppIDSvc' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'FMS'.
    [05:39:33] [Warning] 'FMS' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'hostcontrollerservice'.
    [05:39:33] [Warning] 'hostcontrollerservice' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'IISAdmin'.
    [05:39:33] [Warning] 'IISAdmin' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeADTopology'.
    [05:39:33] [Warning] 'MSExchangeADTopology' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeAntispamUpdate'.
    [05:39:33] [Warning] 'MSExchangeAntispamUpdate' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeDagMgmt'.
    [05:39:33] [Warning] 'MSExchangeDagMgmt' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeDelivery'.
    [05:39:33] [Warning] 'MSExchangeDelivery' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeDiagnostics'.
    [05:39:33] [Warning] 'MSExchangeDiagnostics' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeEdgeSync'.
    [05:39:33] [Warning] 'MSExchangeEdgeSync' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeFastSearch'.
    [05:39:33] [Warning] 'MSExchangeFastSearch' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeFrontendTransport'.
    [05:39:33] [Warning] 'MSExchangeFrontendTransport' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeHM'.
    [05:39:33] [Warning] 'MSExchangeHM' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeIMAP4'.
    [05:39:33] [Warning] 'MSExchangeIMAP4' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeIS'.
    [05:39:33] [Warning] 'MSExchangeIS' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeMailboxAssistants'.
    [05:39:33] [Warning] 'MSExchangeMailboxAssistants' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeMailboxReplication'.
    [05:39:33] [Warning] 'MSExchangeMailboxReplication' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangePOP3'.
    [05:39:33] [Warning] 'MSExchangePOP3' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeRepl'.
    [05:39:33] [Warning] 'MSExchangeRepl' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeRPC'.
    [05:39:33] [Warning] 'MSExchangeRPC' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeServiceHost'.
    [05:39:33] [Warning] 'MSExchangeServiceHost' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeSubmission'.
    [05:39:33] [Warning] 'MSExchangeSubmission' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeThrottling'.
    [05:39:33] [Warning] 'MSExchangeThrottling' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeTransport'.
    [05:39:33] [Warning] 'MSExchangeTransport' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeTransportLogSearch'.
    [05:39:33] [Warning] 'MSExchangeTransportLogSearch' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'MSExchangeUM'.
    [05:39:33] [Warning] 'MSExchangeUM' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'pla'.
    [05:39:33] [Warning] 'pla' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'RemoteRegistry'.
    [05:39:33] [Warning] 'RemoteRegistry' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'SearchExchangeTracing'.
    [05:39:33] [Warning] 'SearchExchangeTracing' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'W3Svc'.
    [05:39:33] [Warning] 'W3Svc' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'WinMgmt'.
    [05:39:33] [Warning] 'WinMgmt' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Enabling service 'wsbexchange'.
    [05:39:33] [Warning] 'wsbexchange' did not exist, this is not an error as the sevice might have just been installed
    [05:39:33] Starting services for AdminTools ClientAccess Gateway FrontendTransport Bridgehead Mailbox UnifiedMessaging...
    [05:39:33] Reading service state from 'C:\ExchangeSetupLogs\ServiceState.xml'...
    [05:39:34] Loaded state for 195 services
    [05:39:34] Starting services and their dependents.
    [05:39:34] (0) Enter: RestoreServiceAndDependents 'AppIDSvc'.
    [05:39:34] 'AppIDSvc' was not running.
    [05:39:34] (0) AppIDSvc was not previously running.
    [05:39:34] (0) Exit: RestoreServiceAndDependents 'AppIDSvc'
    [05:39:34] (0) Enter: RestoreServiceAndDependents 'FMS'.
    [05:39:34] 'FMS' was running.
    [05:39:34] (0) Starting FMS...
    [05:39:41] 0: Service 'FMS' is disabled on this server.
    [05:39:41] Unable to restore service 'FMS'.
    [05:39:41] (0) Enter: RestoreServiceAndDependents 'hostcontrollerservice'.
    [05:39:41] 'hostcontrollerservice' was running.
    [05:39:41] (0) Starting hostcontrollerservice...
    [05:39:41] 0: Service 'hostcontrollerservice' is disabled on this server.
    [05:39:41] Unable to restore service 'hostcontrollerservice'.
    [05:39:41] (0) Enter: RestoreServiceAndDependents 'IISAdmin'.
    [05:39:41] 'IISAdmin' was running.
    [05:39:41] (0) Starting IISAdmin...
    [05:39:41] 0: Service 'IISAdmin' is disabled on this server.
    [05:39:41] Unable to restore service 'IISAdmin'.
    [05:39:41] (0) Enter: RestoreServiceAndDependents 'MSExchangeADTopology'.
    [05:39:41] 'MSExchangeADTopology' was running.
    [05:39:41] (0) Starting MSExchangeADTopology...
    [05:39:41] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:41] Unable to restore service 'MSExchangeADTopology'.
    [05:39:41] (0) Enter: RestoreServiceAndDependents 'MSExchangeAntispamUpdate'.
    [05:39:41] 'MSExchangeAntispamUpdate' was running.
    [05:39:41] (0) Starting MSExchangeAntispamUpdate...
    [05:39:41] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:41] Unable to restore service 'MSExchangeAntispamUpdate'.
    [05:39:41] (0) Enter: RestoreServiceAndDependents 'MSExchangeDagMgmt'.
    [05:39:41] 'MSExchangeDagMgmt' was running.
    [05:39:41] (0) Starting MSExchangeDagMgmt...
    [05:39:41] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:41] Unable to restore service 'MSExchangeDagMgmt'.
    [05:39:41] (0) Enter: RestoreServiceAndDependents 'MSExchangeDelivery'.
    [05:39:41] 'MSExchangeDelivery' was running.
    [05:39:41] (0) Starting MSExchangeDelivery...
    [05:39:41] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:41] Unable to restore service 'MSExchangeDelivery'.
    [05:39:41] (0) Enter: RestoreServiceAndDependents 'MSExchangeDiagnostics'.
    [05:39:41] 'MSExchangeDiagnostics' was running.
    [05:39:41] (0) Starting MSExchangeDiagnostics...
    [05:39:41] 0: Service 'MSExchangeDiagnostics' is disabled on this server.
    [05:39:41] Unable to restore service 'MSExchangeDiagnostics'.
    [05:39:41] (0) Enter: RestoreServiceAndDependents 'MSExchangeEdgeSync'.
    [05:39:41] 'MSExchangeEdgeSync' was running.
    [05:39:41] (0) Starting MSExchangeEdgeSync...
    [05:39:42] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:42] Unable to restore service 'MSExchangeEdgeSync'.
    [05:39:42] (0) Enter: RestoreServiceAndDependents 'MSExchangeFastSearch'.
    [05:39:42] 'MSExchangeFastSearch' was running.
    [05:39:42] (0) Starting MSExchangeFastSearch...
    [05:39:42] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:42] Unable to restore service 'MSExchangeFastSearch'.
    [05:39:42] (0) Enter: RestoreServiceAndDependents 'MSExchangeFrontendTransport'.
    [05:39:42] 'MSExchangeFrontendTransport' was running.
    [05:39:42] (0) Starting MSExchangeFrontendTransport...
    [05:39:42] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:42] Unable to restore service 'MSExchangeFrontendTransport'.
    [05:39:42] (0) Enter: RestoreServiceAndDependents 'MSExchangeHM'.
    [05:39:42] 'MSExchangeHM' was running.
    [05:39:42] (0) Starting MSExchangeHM...
    [05:39:42] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:42] Unable to restore service 'MSExchangeHM'.
    [05:39:42] (0) Enter: RestoreServiceAndDependents 'MSExchangeIMAP4'.
    [05:39:42] 'MSExchangeIMAP4' was running.
    [05:39:42] (0) Starting MSExchangeIMAP4...
    [05:39:42] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:42] Unable to restore service 'MSExchangeIMAP4'.
    [05:39:42] (0) Enter: RestoreServiceAndDependents 'MSExchangeIS'.
    [05:39:42] 'MSExchangeIS' was running.
    [05:39:42] (0) Starting MSExchangeIS...
    [05:39:42] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:42] Unable to restore service 'MSExchangeIS'.
    [05:39:42] (0) Enter: RestoreServiceAndDependents 'MSExchangeMailboxAssistants'.
    [05:39:42] 'MSExchangeMailboxAssistants' was running.
    [05:39:42] (0) Starting MSExchangeMailboxAssistants...
    [05:39:42] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:42] Unable to restore service 'MSExchangeMailboxAssistants'.
    [05:39:42] (0) Enter: RestoreServiceAndDependents 'MSExchangeMailboxReplication'.
    [05:39:42] 'MSExchangeMailboxReplication' was running.
    [05:39:42] (0) Starting MSExchangeMailboxReplication...
    [05:39:42] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:42] Unable to restore service 'MSExchangeMailboxReplication'.
    [05:39:42] (0) Enter: RestoreServiceAndDependents 'MSExchangePOP3'.
    [05:39:42] 'MSExchangePOP3' was not running.
    [05:39:42] (0) MSExchangePOP3 was not previously running.
    [05:39:42] (0) Exit: RestoreServiceAndDependents 'MSExchangePOP3'
    [05:39:42] (0) Enter: RestoreServiceAndDependents 'MSExchangeRepl'.
    [05:39:43] 'MSExchangeRepl' was running.
    [05:39:43] (0) Starting MSExchangeRepl...
    [05:39:43] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:43] Unable to restore service 'MSExchangeRepl'.
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'MSExchangeRPC'.
    [05:39:43] 'MSExchangeRPC' was running.
    [05:39:43] (0) Starting MSExchangeRPC...
    [05:39:43] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:43] Unable to restore service 'MSExchangeRPC'.
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'MSExchangeServiceHost'.
    [05:39:43] 'MSExchangeServiceHost' was running.
    [05:39:43] (0) Starting MSExchangeServiceHost...
    [05:39:43] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:43] Unable to restore service 'MSExchangeServiceHost'.
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'MSExchangeSubmission'.
    [05:39:43] 'MSExchangeSubmission' was running.
    [05:39:43] (0) Starting MSExchangeSubmission...
    [05:39:43] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:43] Unable to restore service 'MSExchangeSubmission'.
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'MSExchangeThrottling'.
    [05:39:43] 'MSExchangeThrottling' was running.
    [05:39:43] (0) Starting MSExchangeThrottling...
    [05:39:43] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:43] Unable to restore service 'MSExchangeThrottling'.
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'MSExchangeTransport'.
    [05:39:43] 'MSExchangeTransport' was running.
    [05:39:43] (0) Starting MSExchangeTransport...
    [05:39:43] 0: Service 'FMS' is disabled on this server.
    [05:39:43] Unable to restore service 'MSExchangeTransport'.
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'MSExchangeTransportLogSearch'.
    [05:39:43] 'MSExchangeTransportLogSearch' was running.
    [05:39:43] (0) Starting MSExchangeTransportLogSearch...
    [05:39:43] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:43] Unable to restore service 'MSExchangeTransportLogSearch'.
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'MSExchangeUM'.
    [05:39:43] 'MSExchangeUM' was running.
    [05:39:43] (0) Starting MSExchangeUM...
    [05:39:43] 0: Service 'MSExchangeADTopology' is disabled on this server.
    [05:39:43] Unable to restore service 'MSExchangeUM'.
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'pla'.
    [05:39:43] 'pla' was not running.
    [05:39:43] (0) pla was not previously running.
    [05:39:43] (0) Exit: RestoreServiceAndDependents 'pla'
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'RemoteRegistry'.
    [05:39:43] 'RemoteRegistry' was not running.
    [05:39:43] (0) RemoteRegistry was not previously running.
    [05:39:43] (0) Exit: RestoreServiceAndDependents 'RemoteRegistry'
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'SearchExchangeTracing'.
    [05:39:43] 'SearchExchangeTracing' was not running.
    [05:39:43] (0) SearchExchangeTracing was not previously running.
    [05:39:43] (0) Exit: RestoreServiceAndDependents 'SearchExchangeTracing'
    [05:39:43] (0) Enter: RestoreServiceAndDependents 'W3Svc'.
    [05:39:43] 'W3Svc' was running.
    [05:39:43] (0) Starting W3Svc...
    [05:39:44] 0: Service 'W3Svc' is disabled on this server.
    [05:39:44] Unable to restore service 'W3Svc'.
    [05:39:44] (0) Enter: RestoreServiceAndDependents 'WinMgmt'.
    [05:39:44] 'WinMgmt' was running.
    [05:39:44] (0) Starting WinMgmt...
    [05:39:44] (0) WinMgmt has 4 dependents.
    [05:39:44] (1) Enter: RestoreServiceAndDependents 'UALSVC'.
    [05:39:44] 'UALSVC' was running.
    [05:39:44] (1) Starting UALSVC...
    [05:39:47] (1) UALSVC has 0 dependents.
    [05:39:47] (1) Exit: RestoreServiceAndDependents 'UALSVC'
    [05:39:47] (1) Enter: RestoreServiceAndDependents 'SharedAccess'.
    [05:39:47] 'SharedAccess' was not running.
    [05:39:47] (1) SharedAccess was not previously running.
    [05:39:47] (1) Exit: RestoreServiceAndDependents 'SharedAccess'
    [05:39:47] (1) Enter: RestoreServiceAndDependents 'NcaSvc'.
    [05:39:47] 'NcaSvc' was not running.
    [05:39:47] (1) NcaSvc was not previously running.
    [05:39:47] (1) Exit: RestoreServiceAndDependents 'NcaSvc'
    [05:39:47] (1) Enter: RestoreServiceAndDependents 'iphlpsvc'.
    [05:39:47] 'iphlpsvc' was running.
    [05:39:47] (1) Starting iphlpsvc...
    [05:39:47] (1) iphlpsvc has 1 dependents.
    [05:39:47] (2) Enter: RestoreServiceAndDependents 'NcaSvc'.
    [05:39:47] 'NcaSvc' was not running.
    [05:39:47] (2) NcaSvc was not previously running.
    [05:39:47] (2) Exit: RestoreServiceAndDependents 'NcaSvc'
    [05:39:47] (1) Exit: RestoreServiceAndDependents 'iphlpsvc'
    [05:39:47] (0) Exit: RestoreServiceAndDependents 'WinMgmt'
    [05:39:47] (0) Enter: RestoreServiceAndDependents 'wsbexchange'.
    [05:39:47] 'wsbexchange' was not running.
    [05:39:47] (0) wsbexchange was not previously running.
    [05:39:47] (0) Exit: RestoreServiceAndDependents 'wsbexchange'
    [05:39:47] Unable to restore all services for AdminTools ClientAccess Gateway FrontendTransport Bridgehead Mailbox UnifiedMessaging.
    [05:39:47] Removing service state from 'C:\ExchangeSetupLogs\ServiceState.xml'...
    [05:39:47] Removing service registry data from 'C:\ExchangeSetupLogs\ServiceStartupMode.xml'...
    [05:39:47] Script completed with one or more errors.

    Wednesday, June 15, 2016 9:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Every Exchange update stops services when it installs the update.  At the end it goes back and reenables the services. If there is *any* hiccup at the end it will leave the services in a stopped state.

    So the stopping of the services is entirely normal and expected.

    It's the hiccup at the end that everyone needs to be focusing on.

    Saturday, June 18, 2016 12:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    When the hiccup is that it searches for the Exchange setup files and obviously not finding them (why would anyone leave the setup laying around on the working server or iso attached) it is not the best design to do updates. Also, when hiccup happens, it is expectable for it to do a revert (which includes starting back everything that was stopped).
    Saturday, June 18, 2016 9:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Just an added note, you can search the System Event Log for event ID 7040 to identify which services were disabled and in what order.
    Saturday, January 7, 2017 3:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Gracias, funcionó para mi. thanks , it worked for me
    Thursday, October 19, 2017 3:14 PM
  • Question
    Sign in to vote
    5
    Sign in to vote

    This is the closest thing I found to my problem which occured today.

    kb4092041 was available in WSUS for Exchange 2016 CU9. Stupidly, I approved the updated and allowed it to install on one of my servers.

    It shut down all the services and set them to disabled, then promptly crashed with 80070643.

    Several hours in trying to get things to work, the Filtering service still goes into permanent "starting" and at this point I can't even launch the setup from the CU9 ISO, it reports some obscure message about the NET framework.

    This is the last straw for me. Any time there is an update for Exchange, there is a greater than 80% chance that I will be restoring a backup if I am lucky, or spending the next two days rebuilding the server if I am not lucky. And as the guys on Hee Haw said, if it weren't for bad luck I'd have no luck at all.

    From now on, I will be ignoring ALL updates for Exchange with the exception of the quarterly CUs. Cleaning up a security breach can't be as difficult as rebuilding the server every time there's a security update, can it? Only after seeing massive amounts of people saying that an update did NOT hose their servers will I even consider it.

    I've built my career supporting Microsoft products, time for a new career path it seems. My blood pressure can't take Patch Tuesdays anymore.




    Wednesday, May 9, 2018 9:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Guys, what you can do is to make Exchange UPGRADE. Not update, but upgrade. I just upgraded MS Exchange from CU8 to CU9 and after that Exchange start working. Remember always to make backup or VM snapshot before making any changes. If you already have latest version of Exchange I do not know what you can do. Perhaps you can try to reinstall it.
    Monday, May 14, 2018 6:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    /me2

    -=Chris

    Thursday, May 17, 2018 8:29 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi.

    pls check you firewall-settings.

    we had the same problems. After switching all firewalls on the server to enabled, the update installs well but we had to start the services manually after reboot.

    • Proposed as answer by Progent.CT Friday, May 18, 2018 10:30 PM
    Friday, May 18, 2018 5:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    That may be the common thread.  The machine I was working on had the firewall disabled via gpo.

    -=Chris

    Friday, May 18, 2018 10:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No firewall issues with mine, everything enabled at the defaults.

    What could firewall possibly have to do with it anyway? Just seems like grasping at straws to me.

    Saturday, May 19, 2018 12:51 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    We ran into this issue with KB4459266 applied to our Windows 2016 Server with Exchange 2016 CU10. The update applied automatically Thursday morning (10/11/2018). The update failed the installation, left all the Exchange services stopped and disabled (including IIS/IISAdmin, etc...) and when enabling the services and attempting to start them they crashed. Trying to run the exchange setup from Control Panel -> Programs and Features or from the Exchange 2016 CU10 media, the setup crashed. Basically, the Exchange install was corrupted.

    I am posting this in hopes that I can save some people some trouble in the future. Someone recommended upgrading Exchange to a newer CU. This may in fact work, but you'll be out of luck if there is no newer CU, as was the case for us.

    Our resolution was to perform the following steps.

    1) Ensure all of the Exchange services and supporting services (IIS, IISAdmin, etc.) are stopped and disabled.
    2) From the current version media (Exchange 2016 CU10, in our case) run the EXCHANGESERVER.msi with the /fa flags (msiexec.exe /i  EXCHANGESERVER.msi /fa). This will force the installation to replace all the binaries with the version from the install media without updating the registry.
    3) Apply all the necessary patches in order (KB4340731 and then KB4459266, in our case).
    4) Re-enable the Exchange services and additional dependent services and reboot the server
    5) Fix-up and start any services that did not start. Probably some services won't start due to dependent services being disabled
    6) All the IIS sits will be broke at this point, ECP, ActiveSync, OWA and Outlook won't work and the Exchange PowerShell will report errors. To resolve this run the UpdateCas.ps1 script from the Exchange install.
    7) Finally find all the web.config and SharedWebConfig.config files in the ..\Exchange Server\V15\ClientAccess\ folder and ..\Exchange Server\V15\FrontEnd\HttpProxy\ folder. These files will need to be updated to replace %ExchangeInstallDir% with the actual install location (C:\Program Files\Microsoft\Exchange Server\V15\ in our case). These files were not updated by the CustomAction that is executed by the Setup.exe. This step is skipped when the MSI is run manually.
    8) Re-apply any custom changes to the IIS sites (i.e. http to https redirection for OWA, if you're doing that)

    Additionally, you'll want to go through the web.config and all the config files to make sure nothing was missed. We compared with a backup from a couple days prior to ensure we didn't miss anything.

    Hope this helps someone.


    ETA: Even though this got us back up and running, we don't feel confident enough with the rebuild that it will be stable for the rest of it's life. Rebooting causes Exchange to generate enough errors that we can't find info on we have opted to build a new system and do a like for like migration.

    • Proposed as answer by Progent.CT Monday, October 15, 2018 2:33 PM
    • Edited by Joe Bandura Wednesday, October 17, 2018 3:53 PM Updated Information
    Monday, October 15, 2018 2:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    That is really good info on the recovery process. 

    -=Chris

    Monday, October 15, 2018 2:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Maybe that's what Exchange Online admins have to do every month :)..
    Monday, October 15, 2018 5:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks man, you saved my life. I was able to repair our Exchange 2016 CU11 installation with your procedure.

    A few things:

    • The command line that worked for me was "msiexec.exe /fa c:\temp\EXCHANGESERVER.msi"
    • Do not try to run the above command from the mounted ISO, you should extract the files to a temporary folder
    • You have to run UpdateCas.ps1 from an Administrative Powershell (elevated privileges)

    - ThePro

    Friday, January 11, 2019 4:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Great info, saved my life today
    Wednesday, July 24, 2019 12:37 AM