That happens to me all the friggin time; server gets updates, and then boom, Outlook can't connect.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Susan Bradley Sent: Friday, December 19, 2014 1:10 AM To: [email protected] Subject: Re: [Exchange] EX2013 rollup 7 install error Remind me to show you the number of Exchange 2010 servers that get rebooted after patching and the services don't start. I monitor a ton of patching lists/SBS 2008 and 2011 boxes if and you had an Exchange server that never had this problem, you were dang lucky. On a scale of .NET barfages, SharePoint blowups, it's lower down the list, but I can show you every Exchange update, someone hiccups right at the end and if it does, the services do not get reenabled. On 12/18/2014 10:03 PM, ccollins9 wrote: > Yes but since 2010, every Exchange update made has automatically > stopped the services, set them to disabled, updated everything, then > restarted the services during the very long update. Even once I fixed > the "MS Exchange Search Host Controller service" to where it could be > started, the updater actually did start the service during the > install, then it still bombed because the service was "set" to > disabled. This is the first time I had to go and set each service to > automatic during the install, just to get through the install. > > On Fri, Dec 19, 2014 at 12:56 AM, Susan Bradley <[email protected] > <mailto:[email protected]>> wrote: > > *Note* Update 2874216 is described in security update MS13-061 > <http://support.microsoft.com/kb/2876063> > (http://support.microsoft.com/kb/2876063) > . > > Given that's a 2013 update which as been rolled into later CUs, > I'm going to say yes you probably have that update. > > Because the patching process as noted stops the services if there > is any hiccup at the end of the process, you may find the services > not turned back on again. > > Rule of patching Exchange/ check for running services. > Rule of patching SharePoint /psconfig. > On 12/18/2014 9:48 PM, ccollins9 wrote: > > Ugh what a friggin PITA. I had two issues. The first was that > the MS Exchange Search Host Controller service got jacked up > and wouldn't start. I had to mod the registry by following > this KB, even though the offending update referenced in the KB > was never installed on the system (as far as i could tell). > The DataDirectory key was indeed missing on my system. Not > sure if it was missing before or after i began the UR7 install > http://support.microsoft.com/kb/2879739/sv > > > The second step was that I had to monitor the install and at > each "Step _ of 7" I would have to set all the MS Exchange > services to automatic. I used: > > gsv | where displayname -like "*exchange*" | Set-Service > -startuptype automatic > > > > https://social.technet.microsoft.com/Forums/en-US/73998790-5481-4dcb-b > 666-db1364cc57f2/exchange-2013-cu7-will-not-install?forum=exchangesvrd > eploy > > > Quoted from forum: > > "http://blogs.catapultsystems.com/cmatthews/archive/2013/04/17/exchang > e-2010-upgrade-sets-all-exchange-services-to-disabled.aspx > > you 扉e to do this after 3 or 4% of each step are processed > ... ;-(" > > > I'm no programmer, by any stretch, but why would their update > code throw errors about services being set to disabled after > the update itself purposefully sets all services to disabled > on each step? What the hell is going on over at MS where they > cannot consistently produce routine updates to one of their > multi-million dollar flagship products? At least it keeps > people like us employed. End rant! > > > On Thu, Dec 18, 2014 at 10:46 PM, ccollins9 > <[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > Already tried that. Same result. Thinking of running > powershell to set all disabled services back to auto, > rebooting, then running setup again. > > > > On Thu, Dec 18, 2014 at 10:16 PM, Michael B. Smith > <[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>> > wrote: > >> > >> Reboot. Restart setup from an elevated command prompt. > >> > >> > >> > >> From: [email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > [mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>] On Behalf Of > ccollins9 > > >> Sent: Thursday, December 18, 2014 9:42 PM > >> To: exchange > >> Subject: [Exchange] EX2013 rollup 7 install error > >> > >> > >> > >> I think ive seen this before on previous rollups, but I > can't recall the fix. Getting the following error when > updating a server with just MBX role. The CAS role server > updated fine. There are two other EX2013 servers in the > domain, one just a CAS and one just an MBX, so 4 total servers > >> > >> > >> > >> [12/19/2014 02:22:57.0626] [1] Processing component > 'Bridgehead Role Setter' (Configuring the Mailbox role: > Transport service.). > >> > >> [12/19/2014 02:22:57.0626] [1] Executing: > >> > >> if (get-service MSExchangeServiceHost* | where > {$_.name -eq "MSExchangeServiceHost"}) > >> > >> { > >> > >> restart-service MSExchangeServiceHost > >> > >> } > >> > >> > >> > >> [12/19/2014 02:22:57.0642] [1] The following 1 error(s) > occurred during task execution: > >> > >> [12/19/2014 02:22:57.0642] [1] 0. ErrorRecord: Service > 'Microsoft Exchange Service Host (MSExchangeServiceHost)' > cannot be started due to the following error: Cannot start > service MSExchangeServiceHost on computer '.'. > >> > >> [12/19/2014 02:22:57.0642] [1] 0. ErrorRecord: > Microsoft.PowerShell.Commands.ServiceCommandException: Service > 'Microsoft Exchange Service Host (MSExchangeServiceHost)' > cannot be started due to the following error: Cannot start > service MSExchangeServiceHost on computer '.'. ---> > System.InvalidOperationException: Cannot start service > MSExchangeServiceHost on computer '.'. ---> > System.ComponentModel.Win32Exception: The service cannot be > started, either because it is disabled or because it has no > enabled devices associated with it > >> > >> --- End of inner exception stack trace --- > >> > >> at > System.ServiceProcess.ServiceController.Start(String[] args) > >> > >> at > > Microsoft.PowerShell.Commands.ServiceOperationBaseCommand.DoStartService(ServiceController > serviceController) > >> > >> --- End of inner exception stack trace --- > >> > >> [12/19/2014 02:22:57.0642] [1] [ERROR] The following error > was generated when "$error.Clear(); > >> > >> if (get-service MSExchangeServiceHost* | where > {$_.name -eq "MSExchangeServiceHost"}) > >> > >> { > >> > >> restart-service MSExchangeServiceHost > >> > >> } > >> > >> " was run: > "Microsoft.PowerShell.Commands.ServiceCommandException: > Service 'Microsoft Exchange Service Host > (MSExchangeServiceHost)' cannot be started due to the > following error: Cannot start service MSExchangeServiceHost on > computer '.'. ---> System.InvalidOperationException: Cannot > start service MSExchangeServiceHost on computer '.'. ---> > System.ComponentModel.Win32Exception: The service cannot be > started, either because it is disabled or because it has no > enabled devices associated with it > >> > >> --- End of inner exception stack trace --- > >> > >> at > System.ServiceProcess.ServiceController.Start(String[] args) > >> > >> at > > Microsoft.PowerShell.Commands.ServiceOperationBaseCommand.DoStartService(ServiceController > serviceController) > >> > >> --- End of inner exception stack trace ---". > >> > >> [12/19/2014 02:22:57.0642] [1] [ERROR] Service 'Microsoft > Exchange Service Host (MSExchangeServiceHost)' cannot be > started due to the following error: Cannot start service > MSExchangeServiceHost on computer '.'. > >> > >> [12/19/2014 02:22:57.0642] [1] [ERROR] Cannot start service > MSExchangeServiceHost on computer '.'. > >> > >> [12/19/2014 02:22:57.0642] [1] [ERROR] The service cannot > be started, either because it is disabled or because it has no > enabled devices associated with it > >> > >> [12/19/2014 02:22:57.0642] [1] [ERROR-REFERENCE] > Id=BridgeheadRoleSetterComponent___115c1108e99e4560bd2c03c0fec99908 > Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup > >> > >> [12/19/2014 02:22:57.0642] [1] Setup is stopping now > because of one or more critical errors. > >> > >> [12/19/2014 02:22:57.0642] [1] Finished executing component > tasks. > >> > >> [12/19/2014 02:22:57.0657] [1] Ending processing > Install-BridgeheadRole > >> > >> [12/19/2014 02:30:46.0356] [0] CurrentResult > setupbase.maincore:396: 0 > >> > >> [12/19/2014 02:30:46.0356] [0] End of Setup > >> > >> [12/19/2014 02:30:46.0356] [0] ********************** > > > >
