I went to install the CU5 update today and it fails on the step Mailbox role: transport service.

Error:
The following error was generated when "$error.Clear(); 
          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
        " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\MFP". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Error:
The following error was generated when "$error.Clear(); 
          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
        " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Client Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

When I try to re-run the setup, it fails at the same spot. I can't use the ECP nor the Shell to remove the Receive Connector (it is just a receive connector for the MFP).

Is there any way to remove this receive connector with Powershell not working?

(It looks like this is the problem: http://exchangemaster.wordpress.com/2014/01/24/incorrectly-adding-new-receive-connector-breaks-exchange-2013-transport/ but since I can't get a shell to run in this failed upgrade state I can't take the recommended fix nor just remove the connector.)

• Edited by Sean P T Monday, June 02, 2014 7:45 PM More information

If I am sure that it is the cause then I would use ADSIEdit.msc or ADExploer.exe to modify the msExchangeReceiveBindings at Receive Connector Object in AD carefully... ;)

Might be around, CN=Protocols,CN=ServerName,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExOrgName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=Com

I was able to find it -- I had to go one step deeper, specifically

CN=Configuration\CN=Services\CN=Microsoft Exchange\CN=<Organization>\CN=Administrative Groups\CN=Exchange Administrative Group (FYDIBOHF23SPDLT)\CN=Servers\CN=<Server Name>\CN=Protocols\CN=SMTP Receive Connectors

But you set me on the right track.

My first instinct was to delete it but I thought that might cause more problems. So I simply edited the bad receive connector and changed the listening port to something else entirely. I then re-started the update and was able to run through.Everything is good to go now!

So thank you for this.

• Proposed as answer by IT Hero Tuesday, October 21, 2014 9:59 PM

Awesome, you're welcome...!

Very helpful.  I had this problem just now and was able to solve it with this Answer.

You guys just saved my azz thanks.

I'm glad y'all are finding this and getting fixed up.

I am having the same issue - and I've dived into Adsiedit to change the port - but I am not sure what part to change. I can't find one that is referred too as a listening port. Any ideas?

Error:

The following error was generated when "$error.Clear();

          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;

          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };

        " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "LVS301GBR\Inbound from Office 365". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)

   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Error:

The following error was generated when "$error.Clear();

          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;

          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };

        " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "LVS301GBR\Default Frontend LVS301GBR". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)

   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Just to also say this post helped us out with the same issue today! Thanks!

TrevCA - your error looks basically the same as ours. Follow the ADSI path posted above by Sean P T and then edit (I would assume your 365 connector) Locate the attribute msExchSmtpReceiveBindings and double click it. It should contain an IPaddress followed by a port number like 1.2.3.4:25

I just added a new one with a random port number so 1.2.3.4:777 and removed the original one. Then re-run the setup and it will kick off from where it failed. Our setup is running now so hopefully when it's all done I can modify the receive connecter via ECP and set it back.

Hope this helps.

PT

Just documented detail procedure/instructions to modify this via ADSIEdit.msc on a Wiki page...

http://social.technet.microsoft.com/wiki/contents/articles/25372.exchange-2013-setup-error-a-receive-connector-must-have-a-unique-combination-of-a-local-ip-address-port-bindings-and-remote-ip-address-ranges.aspx

I saw that in my RSS feed and I thought "Hey, that sounds like the problem I had a few weeks ago!"

Amit you saved the day. You are a star!

Amit you saved the day. You are a star!

Glad it helped you Jon! :)

Many thanks :)

Thank you for the post. I was having the same issue and with this I was able to get this working.

Thanks for the post, it was very helpful. 

Awesome save!