Exchange 2013 update fails from SP1 to CU5

Hi,
Trying to upgrade my exchange server 2013 SP1 to CU5 but not able to do it successfully it is giving below error while analyzing prerequisites .
Server is in test environment and it has 2 network interfaces.
Error:
There was a problem accessing the registry on this computer. This may happen if the Remote Registry service isn't running. It may also indicate a network problem or that the TCP/IP Netbios Helper service isn't running.
#kkalas

Hi
Are those services running?
Have you tried doing a restart and then apply the update again?

Similar Messages

SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The virtual directory 'ecp' already exists under 'server/name'.
Parameter name: VirtualDirectoryName".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
!! And now transport service won't start and mail is unavailable !!
Any help would be appreciated.
I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

Hi,
Thanks for your response.
From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Office 2013 updates fail on computers with Access 2013 installed

I have about 10 workstations with the combination of Windows 7 enterprise 32 bit, Access 2013 and Office 2007 installed.
SCCM offers up both Office 2007 and Office 2013 updates to these machines, but the Office 2013 updates, fail to install.
The same thing happens when I go to Microsoft updates and manually install the required Office 2013 updates.
I read that one of the updates required Office 2013 sp1.
But when I downloaded it, it won't install: KB2817430 "The expected version of this product was not found on the system."
This is the second month I've had the failures. I removed KB2878316 and KB2889927 from my deployments and packages to stop repeated install attempts.
But this month I've got a new on failing, KB2899493.
Is there a way around this problem?

Thanks, I couldn't really find anything but it looks as though this could be just the way it is.
from http://support.microsoft.com/kb/2784668
When you start a version of Access on a computer that has multiple versions of Access installed, the Windows Installer may start, and
a message that states that the Windows Installer is preparing to install Access may be displayed before Access starts.
Every time that you start Access 2003, Access 2007, or Access 2010 after you use Access 2013, the Windows Installer repair operation registers
that version of Access. Similarly, the Windows Installer repair operation registers Access 2010 every time that you start it after you use an earlier version of Access. This does not occur when you start Access 2002, nor does it occur when you start the same
version of Access again.
Is this likely to also apply even when running App-V?

Error when updating Client Access Front End Service to Exchange 2013 Update 6

When updating to Exchange 2013 Update 6 we received the following error at the Step 11 of 13: Client Access role: Client Access Front End service step:
Error:
The following error was generated when "$error.Clear();
$fe = get-ActiveSyncVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
if ($fe -eq $null)
new-ActiveSyncVirtualDirectory -DomainController $RoleDomainController -Role ClientAccess;
else
update-ActiveSyncVirtualDirectory $fe -DomainController $RoleDomainController -InstallIsapiFilter $true
" was run: "System.Management.Automation.ParameterBindingException: Cannot convert 'System.Object[]' to the type 'Microsoft.Exchange.Configuration.Tasks.VirtualDirectoryIdParameter' required by parameter 'Identity'. Specified method is not supported. ---> System.NotSupportedException: Specified method is not supported.
at System.Management.Automation.ParameterBinderBase.CoerceTypeAsNeeded(CommandParameterInternal argument, String parameterName, Type toType, ParameterCollectionTypeInformation collectionTypeInfo, Object currentValue)
--- End of inner exception stack trace ---
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".
Problem was that if you have more than one ActiveSyncVirtualDirectory, the installer for Update 6 fails because it's not expecting an array of virtual directories to be returned. Solution is to remove the "extra" virtual directory, perform the
installation, and then re-add the virtual directory.
None of the other types of virtual directories are susceptible to this, only ActiveSync.

Hi,
Please try to reset registrar state:
http://tsoorad.blogspot.in/2013/04/lync-2013-ee-pool-wont-start.html
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Kent Huang
TechNet Community Support

Exchange 2013 - Import-TransportRuleCollection from Exchange 2007 failing

I am in the middle of a Exchange 2007 SP3 to Exchange 2013 Sp1/CU4 migration and am importing transport rules and it's failing.
[PS] C:\Windows\system32>Import-TransportRuleCollection -FileData C:\2007TransportRules.xml -Verbose
Cannot process argument transformation on parameter 'FileData'. Cannot convert value "C:\2007TransportRules.xml" to type "System.Byte[]". Error: "Cannot convert value "C:\2007TransportRules.xml" to type "System.Byte".
Error: "Input string was not in a correct format.""
    + CategoryInfo          : InvalidData: (:) [Import-TransportRuleCollection], ParameterBindin...mationException
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,Import-TransportRuleCollection
    + PSComputerName        : ex2013-mb1.MYDOMAIN.local
Before you ask, I am still on SP1/CU4 because CU5 and CU6 are so buggy I refuse to install them. And that's probably not the fix anyway... WHEN IS CU7 coming out?

I've seen an official list but, rules that were Edge transport rules are the first ones that come to mind. After the import you can look in the EAC and it should show you any rules that have errors or you can stare and compare the rules to your 2007 environment
to determine if any weren't imported.
DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

Outlook can't connect with Exchange 2013 after migration from Exchange 2007

<style type="text/css">P { margin-bottom: 0.21cm; }</style>
Hello,
recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
To try to resolve it we've done:
- Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
- Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
- In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
- Check Outlook Anywhere block: we've cheked.
Currently server state:
- Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
unless the mailbox. After a restart it can't start.
-The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
We continue to try to resolve the problem.
Thanks to all in advance!
Testing RPC / HTTP connectivity.
Error in testing RPC / HTTP.
additional Details
Elapsed time: 24295 ms.
Test steps
Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
Error in automatic detection test .
additional Details
Elapsed time: 24294 ms.
Test steps
Attempting each method of contacting the Autodiscover service .
Failed to properly contact the Autodiscover service using all methods.
additional Details
Elapsed time: 24294 ms.
Test steps
Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
Error in testing this potential Autodiscover URL .
additional Details
Elapsed time: 1509 ms.
Test steps
Attempting to resolve the host name in DNS empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 80.36.252.194
Elapsed time: 507 ms.
Testing TCP port 443 on the host to ensure empresa.com listening or is open.
The port was opened successfully.
additional Details
Elapsed time: 464 ms.
Testing the SSL certificate to make sure it is valid.
The SSL certificate is not exceeded one or more certificate validation checks .
additional Details
Elapsed time: 537 ms.
Test steps
Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
additional Details
Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
Elapsed time: 454 ms.
Validating the certificate name .
The certificate name was validated successfully .
additional Details
Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
Elapsed time: 1 ms.
Is validating the trusted certificate .
Validation Error trusted certificate.
Test steps
Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = mail.empresa.com .
Could not build a certificate chain for the certificate.
Tell me more about this issue and how to resolve
additional Details
The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
Elapsed time: 31 ms.
Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
Error in testing this potential Autodiscover URL .
additional Details
Elapsed time: 21723 ms.
Test steps
Attempting to resolve the host name in DNS autodiscover.empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 46.16.56.40
Elapsed time: 498 ms.
Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
The specified port is blocked , not listening or does not generate the expected response .
Tell me more about this issue and how to resolve
additional Details
Network Error communicating with the remote host.
Elapsed time: 21224 ms.
Attempting to contact the Autodiscover service with the HTTP redirect method .
Error when trying to contact the Autodiscover HTTP redirect method .
additional Details
Elapsed time: 606 ms.
Test steps
Attempting to resolve the host name in DNS autodiscover.empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 46.16.56.40
Elapsed time: 14 ms .
Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
The port was opened successfully.
additional Details
Elapsed time: 202 ms.
Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
additional Details
Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
Elapsed time: 388 ms.
Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
additional Details
Elapsed time: 186 ms.
Test steps
Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
Not the Autodiscover SRV record in DNS found .
Tell me more about this issue and how to resolve
additional Details
Elapsed time: 186 ms.
Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
Tell me more about this issue and how to resolve
additional Details
No Autodiscover CNAME record for your domain ' empresa.com ' .
Elapsed time: 268 ms.
jspt

Hello,
We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
$AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
Name                                 : EXCHANGE13
Fqdn                                 : EXCHANGE13.domain.local
ClientAccessArray                    :
OutlookAnywhereEnabled               : True
AutoDiscoverServiceCN                : EXCHANGE13
AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
AlternateServiceAccountConfiguration :
IsOutOfService                       : False
WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
Identity                             : EXCHANGE13
IsValid                              : True
ExchangeVersion                      : 0.1 (8.0.535.0)
DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                       (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=First Organization,CN=Microsoft
                                       Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass                          : {top, server, msExchExchangeServer}
WhenChanged                          : 09/03/2014 12:46:07
WhenCreated                          : 08/03/2014 19:15:54
WhenChangedUTC                       : 09/03/2014 11:46:07
WhenCreatedUTC                       : 08/03/2014 18:15:54
OrganizationId                       :
OriginatingServer                    : severdc.domain.local
ObjectState                          : Unchanged
I hope this stuff can help you.
Thanks!!
jspt

Exchange 2013 CU3 Fails "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception."

I can't get Exchange 2013 to install in our Server 2008 R2 infrastructure. Setup fails with the following error when preparing AD. This is running on Server 2008 R2 SP1 VM's.
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
    Organization Preparation
FAILED
     The following error was generated when "$error.Clear();
        install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
ainController $RoleDomainController
" was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the

I have set the PowerShell Execution Policy to unrestricted. After running setup /PS I get the following output
PS C:\Windows\system32> cd c:\temp\ex2013cu3
PS C:\temp\ex2013cu3> ./setup /ps /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
    Extending Active Directory schema
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation completed successfully.
PS C:\temp\ex2013cu3>
The installation was started at 10:13am and hung for sometime at 94% of the prereq stage. Installation finally completed at 10:47am. The errors seem to indicate that setup will continue. However upon running setup /prepareAD the installation hangs for sometime
at 21% of Organization Preparation before finally failing with the following output....
PS C:\temp\ex2013cu3> ./setup /prepareAD /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
    Organization Preparation
FAILED
     The following error was generated when "$error.Clear();
        install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
ainController $RoleDomainController
" was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
PS C:\temp\ex2013cu3>

2012 r2 Essentials on premises Exchange 2013 integration failing

I have a new server in my development environment that I have installed Essentials and Exchange 2013 on with all of the latest updates. After getting Exchange 2013 installed I am unable to successfully run the Exchange Integration wizard. It fails saying
that it can't contact the exchange server.
I am able to access the Exchange Powershell, Exchange Admin center and OWA.
The Essentials Anywere Access has been setup and Is working as well.
any suggestions on where to go from here?

Hi,
-->It fails saying that it can't contact the exchange server.
Can you ping the exchange server via server name and IP address? In addition, did you apply
Cumulative Update 5 for Exchange Server 2013 and reboot the Exchange server, then monitor the result? Just a confirmation, thanks for your understanding.
Please also refer to following article and check if can help you.
Integrate an On-Premises Exchange Server with Windows Server Essentials
In addition, if this issue still exists, please follow the path:
%programdata%\Microsoft\Windows Server\Logs and check log files if find more clues.
Windows Server Essentials 2012/2012 R2 Log Files
If any update, please feel free to let me know,
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Exchange 2013 schemaprep failing

Trying to setup Exchange 2013 on a test domain with no prior Exchange.
All prereq's done, tried doing the schemaprep from one of the CAS servers, and it failed, also tried from one of the DC's. DC's are 2008R2. Domain and forest are at 2003 level. Running as the domain's "administrator" account, which is a domain admin, schema
admin and enterprise admin. Single forest, single domain.
Logs below:
Z:\>setup /prepareschema /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/04/2012 23:30:28.0234] [0] **********************************************
[12/04/2012 23:30:28.0234] [0] Starting Microsoft Exchange Server 2013 Setup
[12/04/2012 23:30:28.0234] [0] **********************************************
[12/04/2012 23:30:28.0234] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[12/04/2012 23:30:28.0234] [0] Operating system version: Microsoft Windows NT 6.1.7601 Service Pack 1.
[12/04/2012 23:30:28.0234] [0] Setup version: 15.0.516.32.
[12/04/2012 23:30:28.0250] [0] Logged on user: HILLZ\Administrator.
[12/04/2012 23:30:28.0250] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/04/2012 23:30:28.0281] [0] Command Line Parameter Name='prepareschema', Value=''.
[12/04/2012 23:30:28.0281] [0] Command Line Parameter Name='iacceptexchangeserverlicenseterms', Value=''.
[12/04/2012 23:30:28.0296] [0] Command Line Parameter Name='sourcedir', Value='Z:\'.
[12/04/2012 23:30:28.0375] [0] RuntimeAssembly was started with the following command: '/prepareschema /iacceptexchangeserverlicenseterms /sourcedir:Z:"'.
[12/04/2012 23:30:28.0375] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[12/04/2012 23:30:28.0375] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[12/04/2012 23:30:28.0375] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/04/2012 23:30:28.0375] [0] Copying Files...
[12/04/2012 23:30:28.0390] [0] Starting copy from Z:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[12/04/2012 23:30:45.0968] [0] Finished copy from Z:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[12/04/2012 23:30:45.0968] [0] File copy complete. Setup will now collect additional information needed for installation.
[12/04/2012 23:30:45.0984] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[12/04/2012 23:30:46.0156] [0] [ERROR] The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
[12/04/2012 23:30:46.0156] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/04/2012 23:30:46.0171] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/04/2012 23:30:46.0171] [0] End of Setup
[12/04/2012 23:30:46.0171] [0] **********************************************
[12/05/2012 13:28:21.0046] [0] **********************************************
[12/05/2012 13:28:21.0062] [0] Starting Microsoft Exchange Server 2013 Setup
[12/05/2012 13:28:21.0062] [0] **********************************************
[12/05/2012 13:28:21.0062] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[12/05/2012 13:28:21.0062] [0] Operating system version: Microsoft Windows NT 6.1.7601 Service Pack 1.
[12/05/2012 13:28:21.0062] [0] Setup version: 15.0.516.32.
[12/05/2012 13:28:21.0062] [0] Logged on user: HILLZ\Administrator.
[12/05/2012 13:28:21.0062] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/05/2012 13:28:21.0093] [0] Command Line Parameter Name='prepareschema', Value=''.
[12/05/2012 13:28:21.0093] [0] Command Line Parameter Name='iacceptexchangeserverlicenseterms', Value=''.
[12/05/2012 13:28:21.0093] [0] Command Line Parameter Name='sourcedir', Value='Z:\'.
[12/05/2012 13:28:21.0140] [0] RuntimeAssembly was started with the following command: '/prepareschema /iacceptexchangeserverlicenseterms /sourcedir:Z:"'.
[12/05/2012 13:28:21.0140] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[12/05/2012 13:28:21.0140] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[12/05/2012 13:28:21.0156] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/05/2012 13:28:21.0156] [0] Copying Files...
[12/05/2012 13:28:21.0156] [0] Starting copy from Z:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[12/05/2012 13:29:06.0468] [0] Finished copy from Z:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[12/05/2012 13:29:06.0468] [0] File copy complete. Setup will now collect additional information needed for installation.
[12/05/2012 13:29:06.0484] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[12/05/2012 13:29:06.0500] [0] [ERROR] The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
[12/05/2012 13:29:06.0515] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/05/2012 13:29:06.0515] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/05/2012 13:29:06.0515] [0] End of Setup
[12/05/2012 13:29:06.0515] [0] **********************************************

Hi Troy12n,
Please make sure you install Exchange 2013 Prerequisites first:
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354.aspx
And if you didn't download Exchange 2013 from Microsoft download, please download it from there as well.
I prefer to create a dedicated account for Exchange management, e.g.
exadmin, and assign permission to it, then install & manage Exchange 2013.
If you have any feedback on our support, please click
here
Frank Wang
TechNet Community Support

Exchange 2013 installation fails

We're in the process of migrating from Exchange 2007 to Exchange 2013. I've followed the prerequisites, and have the necessary account permissions, but when I start the installation it fails at step 1 of 5 (mailbox role:mailbox service).
This warning shows up in the application log:
Event ID 2397
Process ExSetupUI.exe (PID=9844). Object [CN=Mailbox Database 1783948598,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<domain>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>,DC=local]. Property [Server] is set to value [<Exchange 2013 server name>
DEL:492ae292-f89f-4a29-b009-22a60973a4bf], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
This error shows up in the Exchange install console, as well as the application log:
Event ID 1002
Exchange Server component Mailbox role: Mailbox service failed.
Error: Error:
The following error was generated when "$error.Clear();
if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
# upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
$name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
$dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
$mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
$dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if($dbs.Length -ne 0)
$mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($mbxUser.Length -ne 0)
enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
else
write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
" was run: "The Exchange server for the database object "Mailbox Database 1783948598" wasn't found in Active Directory Domain Services. The object may be corrupted.".
I should also mention that this installation was attempted once before by an ex-coworker, and it failed. I've spent hours searching Google but haven't come up with a solution. Does anyone have any ideas?

Check it at Exchange 2007 side, Get-MailboxDatabase -Server E2007ServerName or via EMC to confirm but if msExchOwningServer/msExchMasterServer
points to the server which is stale 2013 server then it shouldn't be connected to E2007 by any way and you are good to remove those...
But I wouldn't touch another DB which has just server name and not servername\0ADEL:guid
as it is not giving error (at least yet...) in the setup
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2013 install fails on Organisation preparation Stage

Hey Guys ,
I'm facing an issue while installing exchange 2013 on existing 2010 organisation , below are the details . I'm installing it on test bed however i'm failing at organisation preparation stage.
I do have existing exchange 2010 on ma domain
I would really appreciate your help.
Configuring Microsoft Exchange Server
Organization Preparation FAILED
The following error was generated when "$error.Clear();
install-RuleCollection -Name:"ClassificationDefinitions" -DomainContro
ller $RoleDomainController;
New-ClassificationRuleCollection -InstallDefaultCollection
" was run: "Unable to continue processing classification rule collection
payload for decryption or further validations. Payload may contain invalid data
Thanks

Hi
When you prepared the Schema and AD did you run the commands and did you run the install from an elevated prompt?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange 2013 : OWA failing after login with error "HTTPS 400"

Greetings,
I am in phase of Upgrading my existing Exchange 2007 Infra to Exchange 2013.
The environment is as mentioned below:
4 Mailbox Server (DAG)
4 CAS Servers (NLB)
Everything has been configured and working properly, except Only one CAS server is able to pass the login request
https://servername/owa
Rest of all the CAS servers are failing with error "HTTPS 400" while accessing OWA
https://localhost/owa
Its happening only while accessing OWA, ECP works fine.
Please let me know the fix to counter this strange issue.
Thanks in advance.
Regards

Hi,
Please check if IIS log is enabled on the CAS server, if not, please enable it.
Then check the detailed error code from IIS logs (Path: inetpub\logs\Logfiles\W3SVC1 ) , some code like 400.1, 400.2 ect.
Refer to this KB for more details
http://support.microsoft.com/kb/943891
After that, please post the OWA related login entry with error code shows 400.
Thanks for your time and patience.
Meanwhile, please check the OWA authentication method by command
Get-OWAVirtualDirectory –Server “Ex2013 CAS server” | fl *authentication*
We should set the authentication as the below:
Get-OWAvirtualdirectory -Server “Ex2013_CAS_server” | set-OWAvirtualdirectory -windowsAuthentication $False -BasicAuthentication $True -FormsAuthentication $True
Then perform iisreset and try to access OWA again.
Best Regards.

Installing Exchange 2013 CU7 fails - multiple Receive connectors

Coming from CU4 (aka SP1) and running this upgrade (to comply with hybrid requirements!), setup errors out on the transport role, that I have 2 receive connectors bound to the same IP address, and stops there.
The problem is that Exchange won't come back up for me to fix or delete the additional Recv connector.
Now what?
[12/17/2014 00:28:07.0489] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0489] [2] User specified parameters: -Identity:'MAIL\Default Frontend MAIL' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0490] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0494] [2] Searching objects "MAIL\Default Frontend MAIL" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0503] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0504] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0544] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0572] [2] Processing object "MAIL\Default Frontend MAIL".
[12/17/2014 00:28:07.0588] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0607] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0611] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0614] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0615] [2] User specified parameters: -Identity:'MAIL\Outbound Proxy Frontend MAIL' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0615] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0619] [2] Searching objects "MAIL\Outbound Proxy Frontend MAIL" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0630] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0631] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0669] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0696] [2] Processing object "MAIL\Outbound Proxy Frontend MAIL".
[12/17/2014 00:28:07.0711] [2] No properties changed for the object "MAIL\Outbound Proxy Frontend MAIL".
[12/17/2014 00:28:07.0711] [2] [WARNING] The command completed successfully but no settings of 'MAIL\Outbound Proxy Frontend MAIL' have been modified.
[12/17/2014 00:28:07.0712] [2] Saving object "MAIL\Outbound Proxy Frontend MAIL" of type "ReceiveConnector" and state "Unchanged".
[12/17/2014 00:28:07.0712] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0714] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0717] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0718] [2] User specified parameters: -Identity:'MAIL\Client Frontend MAIL' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0718] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0723] [2] Searching objects "MAIL\Client Frontend MAIL" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0732] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0733] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0778] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0806] [2] Processing object "MAIL\Client Frontend MAIL".
[12/17/2014 00:28:07.0820] [2] No properties changed for the object "MAIL\Client Frontend MAIL".
[12/17/2014 00:28:07.0821] [2] [WARNING] The command completed successfully but no settings of 'MAIL\Client Frontend MAIL' have been modified.
[12/17/2014 00:28:07.0821] [2] Saving object "MAIL\Client Frontend MAIL" of type "ReceiveConnector" and state "Unchanged".
[12/17/2014 00:28:07.0822] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0824] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0827] [2] Active Directory session settings for 'Set-ReceiveConnector' are: View Entire Forest: 'True', Configuration Domain Controller: 'DC1.contoso.local', Preferred Global Catalog: 'DC1.contoso.local', Preferred Domain Controllers: '{ DC1.contoso.local }'
[12/17/2014 00:28:07.0828] [2] User specified parameters: -Identity:'MAIL\Scanner email' -MaxLocalHopCount:'5'
[12/17/2014 00:28:07.0828] [2] Beginning processing Set-ReceiveConnector
[12/17/2014 00:28:07.0832] [2] Searching objects "MAIL\Scanner email" of type "ReceiveConnector" under the root "$null".
[12/17/2014 00:28:07.0840] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0841] [2] Searching objects "MAIL" of type "Server" under the root "$null".
[12/17/2014 00:28:07.0884] [2] Previous operation run on domain controller 'DC1.contoso.local'.
[12/17/2014 00:28:07.0912] [2] Processing object "MAIL\Scanner email".
[12/17/2014 00:28:07.0925] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0927] [2] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0931] [2] Ending processing Set-ReceiveConnector
[12/17/2014 00:28:07.0933] [1] The following 2 error(s) occurred during task execution:
[12/17/2014 00:28:07.0934] [1] 0. ErrorRecord: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0934] [1] 0. ErrorRecord: Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". 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)
[12/17/2014 00:28:07.0965] [1] [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\Scanner email". 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)".
[12/17/2014 00:28:07.0965] [1] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Scanner email". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0966] [1] 1. ErrorRecord: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0966] [1] 1. ErrorRecord: Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default 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)
[12/17/2014 00:28:07.0966] [1] [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\Default 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)".
[12/17/2014 00:28:07.0966] [1] [ERROR] The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Default Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
[12/17/2014 00:28:07.0967] [1] [ERROR-REFERENCE] Id=TransportCommonComponent___79d82f60693f413588aa8c3a58e90b41 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[12/17/2014 00:28:07.0980] [1] Setup is stopping now because of one or more critical errors.
[12/17/2014 00:28:07.0980] [1] Finished executing component tasks.
[12/17/2014 00:28:08.0061] [1] Ending processing Install-BridgeheadRole
[12/17/2014 00:28:40.0012] [0] CurrentResult setupbase.maincore:396: 0
[12/17/2014 00:28:40.0013] [0] End of Setup
[12/17/2014 00:28:40.0013] [0] **********************************************

Someone already found a fix for this here:
https://exchangeshare.wordpress.com/2014/07/14/exchange-2013-setup-error-a-receive-connector-must-have-a-unique-combination-of-a-local-ip-address-port-bindings-and-remote-ip-address-ranges/#comment-1219
Just in case this link won't work some day, here was the fix:
Open ADSI edit on your Domain Controller
Go to Configuration, and drill down Services, Microsoft Exchange, First Organization, Administrative Groups, Exchange Administrative Groups, Servers, <Your Server Name>, Protocols, SMTP Receive Connectors
Find the offending connector and delete it.
Setup will resume as normal, and recreate the connector after setup completes.

Exchange 2013 mailbox migration from third party cloud to on premises

Hi,
we are currently utilizing a third party exchange 2013 cloud service to host user's mailboxes ( intermedia), now we implemented an exchange 2013 on-premises environment in Hyper V infrastructure and want to plan migration of mailboxes and related configuration.
cloud and on-premises environment have same SMTP domain ( Eg: XYZ.ORG) and currently an additional Temporary SMTP domain ( XYZ.CO ) used to test the external mailflow of on-premises since xyz.org is registered with cloud.
we need to migrate all mailboxes to on premises and enable XYZ.ORG for on-premises.
Pls suggest the prerequisites,steps, best practices for migration
Thanks in advance.

Hi Sumesh,
1. Please make sure your mails are flowing correctly using XYZ.CO domain. Hope you have XYZ.ORG also created in Exchange.
2. Hope you already created the users in your Exchange2013 server and distribution groups for current users
3. You plan a weekend for changing your MX records.
4. Change MX and A records to a lower TTL days before the migration to decrease DNS update time on migration day
5. Export Hosted Exchange data for each user to PST files using the PST capture tool and move your PSTs to a centralized location.
6. Change MX and A records to point to on-premises Exchange 2013
7. Import Hosted Exchange data from PST files into the new Exchange profiles
Please check these as well
http://community.office365.com/en-us/b/office_365_community_blog/archive/2011/08/15/exchange-hybrid-configuration-tips-moving-cloud-based-mailboxes-to-the-on-premises-organization.aspx
http://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/microsoft-pst-capture-tool-part1.html
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013 Cu6 fails to install

When I attempt to install CU6 on Exchange 2013 I get this error message and cannot continue, occurs after reboot as well and trying to re-run setup. Any ideas how to fix?
Thanks,
Setup Error 2nd time 5 of 9 after restart
Error:
The following error was generated when "$error.Clear();
$name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
$dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
$dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
if( $dismbx -ne $null)
$srvname = $dismbx.ServerName;
if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
$mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
if( $mountedMdb -eq $null )
Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
mount-database $dismbx.Database;
$mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
if( $mountedMdb -ne $null )
$dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
$dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
if( $dmRoleGroup -ne $null )
trap [Exception]
Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
continue;
Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
" was run: "Microsoft.Exchange.Data.Common.LocalizedException: Couldn't resolve the user or group "Domain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest
principal, you must have either a two-way trust or an outgoing trust. ---> System.SystemException: The trust relationship between the primary domain and the trusted domain failed.
at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed)
at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
at System.Security.Principal.NTAccount.Translate(Type targetType)
at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
--- End of inner exception stack trace ---
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.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetSecurityPrincipal(IRecipientSession session, SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
at Microsoft.Exchange.Management.RecipientTasks.SetMailboxPermissionTaskBase.InternalValidate()
at Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Hi,
Thanks. This did work for me. CU6 applied, Exchange back up. Go live in 2 weeks.
Delete the Discovery Search mailbox user from Active Directory. Start your Active Directory Users and Computers
mmc and look for your Discovery Search Mailbox user. Default this user will be placed in the Users organizational unit. It will be named something like: DiscoverySearchMailbox{D919BA05-46A6-415f-80AD-7E09334BB852}. After deletion you can restart the installation
of your Exchange Service Pack. It will not show the error anymore.
To recreate the user use: setup
/PrepareAD /IAcceptExchangeServerLicenseTerms

Exchange 2013 update fails from SP1 to CU5

Similar Messages

Maybe you are looking for