Solved

Exchange 2010 problems applying SP3

Posted on 2013-06-03
3
1,797 Views
Last Modified: 2013-06-10
SBS2011 box trying to apply SP3, has been rebooted before starting update, post problem same result - the MSExchangeProtectedServiceHost won't start so clients can't access email.

We have not disabled IPv6 and the service is set to local system

06/03/2013 15:38:07.0216] [1] Processing component 'Bridgehead Role Setter' (Configuring the Hub Transport role.).
[06/03/2013 15:38:07.0216] [1] Executing:
        if (get-service MSExchangeServiceHost* | where {$_.name -eq "MSExchangeServiceHost"})
        {
            restart-service MSExchangeServiceHost
        }
       
[06/03/2013 15:38:14.0059] [1] Executing:
        if (get-service MSExchangeProtectedServiceHost* | where {$_.name -eq "MSExchangeProtectedServiceHost"})
        {
            restart-service MSExchangeProtectedServiceHost
        }
       
[06/03/2013 15:40:14.0134] [1] The following 1 error(s) occurred during task execution:
[06/03/2013 15:40:14.0150] [1] 0.  ErrorRecord: Service 'Microsoft Exchange Protected Service Host (MSExchangeProtectedServiceHost)' cannot be started due to the following error: Cannot start service MSExchangeProtectedServiceHost on computer '.'.
[06/03/2013 15:40:14.0212] [1] 0.  ErrorRecord: Microsoft.PowerShell.Commands.ServiceCommandException: Service 'Microsoft Exchange Protected Service Host (MSExchangeProtectedServiceHost)' cannot be started due to the following error: Cannot start service MSExchangeProtectedServiceHost on computer '.'. ---> System.InvalidOperationException: Cannot start service MSExchangeProtectedServiceHost on computer '.'. ---> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion
   --- 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 ---
[06/03/2013 15:40:14.0228] [1] The following error was generated when "$error.Clear();
        if (get-service MSExchangeProtectedServiceHost* | where {$_.name -eq "MSExchangeProtectedServiceHost"})
        {
            restart-service MSExchangeProtectedServiceHost
        }
        " was run: "Service 'Microsoft Exchange Protected Service Host (MSExchangeProtectedServiceHost)' cannot be started due to the following error: Cannot start service MSExchangeProtectedServiceHost on computer '.'.".
[06/03/2013 15:40:14.0228] [1] Service 'Microsoft Exchange Protected Service Host (MSExchangeProtectedServiceHost)' cannot be started due to the following error: Cannot start service MSExchangeProtectedServiceHost on computer '.'.
[06/03/2013 15:40:14.0228] [1] Cannot start service MSExchangeProtectedServiceHost on computer '.'.
[06/03/2013 15:40:14.0228] [1] The service did not respond to the start or control request in a timely fashion
[06/03/2013 15:40:14.0243] [1] [ERROR-REFERENCE] Id=BridgeheadRoleSetterComponent___dd9c610618d44ff9bb1635b8b946ef42 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[06/03/2013 15:40:14.0243] [1] Setup is stopping now because of one or more critical errors.
[06/03/2013 15:40:14.0243] [1] Finished executing component tasks.
[06/03/2013 15:40:14.0290] [1] Ending processing Install-BridgeheadRole
0
Comment
Question by:ashdownsolutions
  • 2
3 Comments
 
LVL 18

Expert Comment

by:suriyaehnop
ID: 39217379
0
 

Accepted Solution

by:
ashdownsolutions earned 0 total points
ID: 39222986
After way to many hours with PSS we ended up rolling back to pre SP3 - any the protected service still wouldn't start.
Ultimately it was a clean boot from msconfig or the removal of Sophos AV (done together) that allowed the service to start.
Reinstalled Sophos all all is good.
Next thing is to schedule a slot where we might have to rollback and try SP3 again
0
 

Author Closing Comment

by:ashdownsolutions
ID: 39234101
Service now running without external assistance - very poor response so assume uncommon issue
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video discusses moving either the default database or any database to a new volume.

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question