Exchange Server 2013 Update from to CU3 to CU8 stuck, Exchange completely down

Hello,

We tried to update a Exchange 2013 server to CU8 because we needed support from Microsoft (certificate revoked, so OWA not working anymore) and they could only help us after updating to CU8 first. The problem is that the update got stuck and now Exchange is not working at all anymore. Since it is a production enviroment and there is mail in all outboxes we do not want to turn back to a snapshot but solve the problem and continue the update. Any help is welcome because all mail is down now :-(

The error we received at the Exchange Server is:

C:\Users\administrator.DOMAINNAME\Downloads\Exchange-cu8>setup.exe /m:upgrade /In stallWindowsComponents /IAcceptExchangeServerLicenseTerms Welcome to Microsoft Exchange Server 2013 Cumulative Update 8 Unattended Setup Copying Files... File copy complete. Setup will now collect additional information needed for installation. Languages Mailbox role: Transport service Client Access role: Front End Transport service Mailbox role: Client Access service Mailbox role: Unified Messaging service Mailbox role: Mailbox service Management tools Client Access role: Client Access Front End service Performing Microsoft Exchange Server Prerequisite Check     Configuring Prerequisites                                 COMPLETED     Prerequisite Analysis                                     COMPLETED Configuring Microsoft Exchange Server     Preparing Setup                                           COMPLETED     Stopping Services                                         COMPLETED     Language Files                                            COMPLETED     Removing Exchange Files                                   COMPLETED     Preparing Files                                           COMPLETED     Copying Exchange Files                                    COMPLETED     Language Files                                            COMPLETED     Restoring Services                                        COMPLETED     Language Configuration                                    COMPLETED     Mailbox role: Transport service                           FAILED      The following error was generated when "$error.Clear();           $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;           foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };         " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei veConnectorRoleConflictException: The values that you specified for the Bindings  and RemoteIPRanges parameters conflict with the settings on Receive connector " SERVER-EXCHANGE\Externe POP3 mailboxen". Receive connectors assigned to differen t Transport roles on a single server must listen on unique local IP address & po rt bindings.    bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio n, ErrorCategory errorCategory, Object target, String helpUrl)    bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio n, ErrorCategory category, Object target)    bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto r.InternalValidate()    bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()    bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu ncName, Action func, Boolean terminatePipelineIfFailed)".      The following error was generated when "$error.Clear();           $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;           foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };         " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei veConnectorRoleConflictException: The values that you specified for the Bindings  and RemoteIPRanges parameters conflict with the settings on Receive connector " SERVER-EXCHANGE\Default Frontend SERVER-EXCHANGE". Receive connectors assigned t o different Transport roles on a single server must listen on unique local IP ad dress & port bindings.    bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio n, ErrorCategory errorCategory, Object target, String helpUrl)    bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio n, ErrorCategory category, Object target)    bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto r.InternalValidate()    bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()    bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu ncName, Action func, Boolean terminatePipelineIfFailed)". The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.


April 20th, 2015 6:55am

Hello Gadget,

Please find the solution as follows

This error is concern about WMSVC certificate which was deleted, we could refer to the following steps:

1- Go to IIS Manager and select server certificate,

2- Select Create Self-Signed Certificate,

3- For Server 2012 in the Friendly Name Field type: WMSVC and select the personal (certificate Store),

4- Now go to Management Service,

5- From SSL Certificate choose the newly create WMSVC Self-Signed Certificate,

6- Apply,

7- Now  start service of Web Management service.

https://social.technet.microsoft.com/Forums/office/en-US/eac00dc2-6e43-45ae-939c-aad82a144908/cu8-install-fails?forum=exchangesvrgeneral

Free Windows Admin Tool Kit Click here and download it now
April 20th, 2015 10:20am

Look like there a problem with receive connector binding, each receive connector need to have unique IP:Port:RemoteIPRange binding.

Usually you can't enable 2 Receive Conenctors that overlap on those parameters, but there seem to be a problem with disabled receive connector being analyzed during CU8 setup.

Did you have disabled receive connectors prior to the upgrade?


April 20th, 2015 10:45am

Look like there a problem with receive connector binding, each receive connector need to have unique IP:Port:RemoteIPRange binding.

Usually you can't enable 2 Receive Conenctors that overlap on those parameters, but there seem to be a problem with disabled receive connector being analyzed during CU8 setup.

Did you have disabled receive connectors prior to the upgrade?

Free Windows Admin Tool Kit Click here and download it now
April 20th, 2015 10:54am

Hello Bruce, the engineer from Microsoft has indeed removed connectors so after that the update to CU8 worked. The problem now is that the engineer is done working and we only have internal mail and outgoing email. The external mail is not coming in yet. We cannot check or change the connector yet since the owa/ecp is not working yet. Do you have any idea how to test or make the incoming mailconnector working?
April 20th, 2015 12:28pm

Hello Andy, the engineer from Microsoft has indeed removed connectors so after that the update to CU8 worked. The problem now is that the engineer is done working and we only have internal mail and outgoing email. The external mail is not coming in yet. We cannot check or change the connector yet since the owa/ecp is not working yet. Do you have any idea how to test or make the incoming mailconnector working?
Free Windows Admin Tool Kit Click here and download it now
April 20th, 2015 12:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics