Solved

Exchange 2010 problems applying SP3

Posted on 2013-06-03
3
1,841 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 19

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

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

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

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

733 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