Exchange 2013 CU7 Installation crash on Mailbox role: Transport Service!!
Hi
I need some help, very urgent.
I started cu7 Installation, and in the middle the Installation failed:
Error:
The following error was generated when "$error.Clear();
# Apply XML Transforms to FIPS configuration file if schema changed
Write-ExchangeSetupLog -Info "Applying XML Transforms to FIPS configuration";
$FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\bin");
[Reflection.Assembly]::LoadFile([System.IO.Path]::Combine($FipsBinPath, "FSCConfigurationServerInterfaces.dll"));
[Reflection.Assembly]::LoadFile([System.IO.Path]::Combine($FipsBinPath, "FSCConfigSupport.dll"));
$configServer = New-Object Microsoft.FSC.Configuration.ConfigManagerClass;
if(! $configServer)
Write-ExchangeSetupLog -Error "Configuration Server object could not be created.";
else
try
$configServer.Upgrade();
Write-ExchangeSetupLog -Info "Configuration.xml was upgraded successfully";
catch
Write-ExchangeSetupLog -Error "Upgrade of Configuration.xml was unsuccessfull, $_";
# Stop the process if it is still running
# We silently continue because if process has already exited, Stop-Process will throw error
# Error is non-terminating and so can be suppressed
Stop-Process -processname FSCConfigurationServer -Force -ErrorAction SilentlyContinue;
" was run: "System.Exception: Upgrade of Configuration.xml was unsuccessfull, Exception calling "Upgrade" with "0" argument(s): "Root element is missing."
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.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
I couldn't find any information about that
Any sugggestion what I can do?
Regards
Peter
Hi,
If it is unable to start Transport service, please try the following method to solve this issue.
Go to “C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Data”
Deleted the file "Configuration.xml" and renamed "Configuration.xml.back" to Configuration.xml.
Then try to re-install Exchange Mailbox Server.
Note: remember to back up the file "Configuration.xml" and "Configuration.xml.back"
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support
Similar Messages
-
Exchange 2013 SP1 Installation Error in "Mailbox Role: Transport service"
I tried an installation last week on a Windows Server 2008 R2 but was unable to get it to work. With the value of hindsight, I am inclined to think the error was more with the Web Site making EAC unavailable. I subsequently got it installed in my personal
lab environment by creating a VM with a fresh install of Windows Server 2008 R2 SP1.
With this information I then went back to the customer's site and installed a clean version of Windows Server 2008 R2 SP1 in a virtual machine under Hyper-V. After installing all the prerequisites the install appeared to be going just fine but then in failed
in Step 7 with the following error:
The following error was generated when "$error.Clear();
if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
" was run: "Database is mandatory on UserMailbox.".
I know MS Exchange hides most of its information in AD so my suspicion is that the failed install on the real server has left some residual information in AD. Note that the original install on the real machine won't uninstall because the prior install attempt
hasn't finished.
The relevant part of the Exchange Setup Log is:
[07/22/2014 14:22:57.0593] [2] Active Directory session settings for 'Update-RmsSharedIdentity' are: View Entire Forest: 'True', Configuration Domain Controller: 'AWSDC.aws.local', Preferred Global Catalog: 'AWSDC.aws.local', Preferred Domain Controllers: '{
AWSDC.aws.local }'
[07/22/2014 14:22:57.0593] [2] User specified parameters: -ServerName:'EXCHANGE'
[07/22/2014 14:22:57.0593] [2] Beginning processing Update-RmsSharedIdentity
[07/22/2014 14:22:58.0031] [2] RMS Shared Identity user 'CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,CN=Users,DC=aws,DC=local' (originating server = 'AWSDC.aws.local') is being linked to computer 'CN=EXCHANGE,CN=Computers,DC=aws,DC=local' (originating
server = 'AWSDC.aws.local').
[07/22/2014 14:22:58.0156] [2] [ERROR] Database is mandatory on UserMailbox.
[07/22/2014 14:22:58.0156] [2] Ending processing Update-RmsSharedIdentity
[07/22/2014 14:22:58.0156] [1] The following 1 error(s) occurred during task execution:
[07/22/2014 14:22:58.0156] [1] 0. ErrorRecord: Database is mandatory on UserMailbox.
[07/22/2014 14:22:58.0156] [1] 0. ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[07/22/2014 14:22:58.0156] [1] [ERROR] The following error was generated when "$error.Clear();
if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
" was run: "Database is mandatory on UserMailbox.".
[07/22/2014 14:22:58.0156] [1] [ERROR] Database is mandatory on UserMailbox.
Does anyone have suggestions about what to do with ADSI Edit to fix the problems?
I think I am getting close to having a working Exchange!!Hi,
Agree with Amit's suggestion. Please use the following cmdlet to re-home the arbitration mailbox which does not have database attribute stamped and check the result.
Set-Mailbox "FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042" -Arbitration -Database "xxx"
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support -
Echange 2013 Installation Failing at Mailbox Role: Transport Service - 97%
Hi all, let me just preface by saying thank you very much all your time, help, and patience!
So I've gone through the Exchange 2013 deployment guide, have installed all the pre-requisites, and am now trying to install Exchange 2013 CU7 on (2) 2008 R2 Enterprise SP1 servers. Unfortunately it is failing on both of them at the Mailbox
Role: Transport Service - 97% with the following error:
Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
" was run: "System.Exception: Unable to set shared config DC.
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.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
I've seen and heard the suggestions about enabling IPv6 on the servers as well as the Domain Controllers which I've done to no avail. We do not have IPv6 addresses available on our network as we use IPv4 space, but I've heard just having the
IPv6 adapter disabled is a lot of times the issue. So the adapters are set to DHCP even though there's no IPv6 address for it to grab. The 2008 R2 servers that I'm trying to install Exchange 2013 on are VMs on ESX. Will the
install fail even if it offers to pick up the installation where I left off? Do I need to completely start from scratch? Any help would be wonderful!Hi,
Please verify whether the port 3268 listen on DC.
Please try to enable GC role on all DCs.
Then restart Exchange server, try to find whether Event 2080 exists with all DCs.
Then try to re-install Exchange Server 2013 CU7.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support -
Exchange Installation Error on Mailbox role: Transport Service Step
The error I receive occurs at 47% of the Mailbox Role: Transport Service installation. The details of the error are as follows:
Mailbox role: Transport service
FAILED
The following error was generated when "$error.Clear();
if ($server -eq $null)
set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainController
" was run: "Active Directory operation failed on DC1.xxxxxx.xxxxxx.com. This error is not retriable. Additional information: The object cannot be added because the parent is not on the list of possible superiors.
Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
'CN=EXCH-MBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxxxx,DC=xxxxxx,DC=com'
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
Also, when opening the setup log I have this:
[12/26/2012 17:51:25.0809] [1] [ERROR] A naming violation occurred.
[12/26/2012 17:51:25.0809] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___a16cb82f909348d3a32b9046f3bfb9ba Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[12/26/2012 17:51:25.0809] [1] Setup is stopping now because of one or more critical errors.
[12/26/2012 17:51:25.0809] [1] Finished executing component tasks.
[12/26/2012 17:51:25.0809] [1] Ending processing Install-BridgeheadRole
[12/26/2012 17:51:25.0825] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/26/2012 17:51:25.0825] [0] End of Setup
[12/26/2012 17:51:25.0825] [0] **********************************************
I have done a ton of searches trying to find a resolution to this error and there are two pages with a similar issue for Exchange 2007 but after trying the solutions suggested, the installation still fails with the same error.
http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploylegacy/thread/dfa9961a-9b20-4c17-ae4d-ebf44c66c18f/
http://exchangetroubleshooting.blogspot.com/2011/05/unable-to-run-preparead-command.html/
Some additional information:
This is a clean installation of Exchange 2013 in a forest that has never had exchange.
The domain and forest preparations run without errors and are at functional level of 2003.
The Exchange server has all prerequisites installed for a Mailbox server role and is running on a VM with Server 2012 as the OS.
This error occurs on other VMs as well that we are trying to implement as mailbox servers in the same forest.
I am running the installation as an enterprise, schema, domain admin.
Thanks for your help in advance.Yes. I cleaned out Exchange with ADSIEdit so I could re-run the Prepare Schema, domain and all domains and then re-ran setup to show the output here. But the install still failed.
PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareSchema
Welcome to Microsoft Exchange Server 2013 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
Configuring Microsoft Exchange Server
Extending Active Directory schema
COMPLETED
The Exchange Server setup operation completed successfully.
PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAD /OrganizationName:AZGT
Welcome to Microsoft Exchange Server 2013 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
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
aspx
Configuring Microsoft Exchange Server
Organization Preparation
COMPLETED
The Exchange Server setup operation completed successfully.
PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAllDomains
Welcome to Microsoft Exchange Server 2013 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
Configuring Microsoft Exchange Server
Prepare Domain Progress
COMPLETED
The Exchange Server setup operation completed successfully.
PS F:\>
PS F:\> .\setup /IAcceptExchangeServerLicenseTerms /mode:install /roles:Mailbox /TargetDir:"C:\Program Files\Microsoft\Exchange Server\V15"
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Languages
Management tools
Mailbox role: Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites
COMPLETED
Prerequisite Analysis
COMPLETED
Configuring Microsoft Exchange Server
Preparing Setup
COMPLETED
Stopping Services
COMPLETED
Copying Exchange Files
COMPLETED
Language Files
COMPLETED
Restoring Services
COMPLETED
Language Configuration
COMPLETED
Exchange Management Tools
COMPLETED
Mailbox role: Transport service
FAILED
The following error was generated when "$error.Clear();
if ($server -eq $null)
set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainCo
ntroller
" was run: "Active Directory operation failed on DC1.XXXX.XXXX.com. This error is not retriable. Addi
tional information: The object cannot be added because the parent is not on the list of possible superiors.
Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
'CN=EXCHMBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
Microsoft Exchange,CN=Services,CN=Configuration,DC=XXXX,DC=XXXX,DC=com'
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
PS F:\> -
Installation of Exchange 2013 Failed on Mailbox Role Transport Service
Hi All,
Getting this error when trying to install a new exchange 2013 server. Thanks in advance
Error:
The following error was generated when "$error.Clear();
if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
" was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".Hi,
This problem occurs because the federated built-in e-mail account that links to the computer account no longer exists. Or, the federated built-in e-mail account in the AD
directory service is corrupted.
Please try to follow these steps to solve this problem.
1. Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:
Click Start, click Run, type adsiedit.msc, and then click
OK.
Locate the Default Naming Context node, and then locate to the
CN=Users container.
Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click
Delete.
2. Rerun the Exchange Server 2013 Mailbox role setup application.
3. Create a new federated e-mail account by using the following command:
New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
If this issue persistes, please let me know.
Best Regards. -
Exchange 2013 CU7 - Frequent Outlook 2013 Disconnections and Delays
We currently have the following environment:
Windows 2012 VM on Hyper-V with 24GB of RAM and 4 virtual procs (1 socket)
Cisco UCS, B200 M3 Blades
Exchange 2013 CU7
Exchange 2007 is in our environment, but public folders have been removed and only a few stale, unused accounts exist on it.
Two dual-role CAS/Mailbox servers
Mailbox servers are in a DAG
MAPI/HTTP is our connection protocol
.NET Framework 4.5.2
Clients are Outlook 2013 SP1 on Windows 7 and 8.1
(Currently round robin DNS, but we have a hardware load balancer we've temporarily taken out of the mix to solve this problem)
What we're seeing is frequent disconnections from Exchange, regardless of the CAS server. That is, both CAS servers will disconnect clients, but not at the same time. When we look at the Exchange boxes, we notice that the CPU is 99% - 100% each time the
disconnections occur. When we hunt down the IISWorker process causing the sudden CPU run, we see it comes back to the following app pools:
MSExchangeMAPIFrontEndAppPool
MSExchangeMAPIMailboxAppPool
(We were running RPC/HTTP, but switched to MAPI/HTTP to resolve the problem. We had the same issue with equivalent RPC app pools at the time.)
Eventually, within a minute or two, the CPU load will decrease and the clients connected via that CAS will regain connection. As you can imagine, the pain is felt more frequently by uncached clients--although everyone, regardless of caching, will see
the disconnections.
Basically, the problem sounds exactly as shown in this KB: http://support.microsoft.com/kb/2995145 Unfortunately, we already had .NET 4.5.2 installed, and have changed the environment variable and registry as shown in the article.
We're in contact with Microsoft Support, but thus far they're scratching their heads.
I'm clearing up all small errors to decrease the noise in the application error logs, but the most persistent one is Event ID 106 (MSExchange Common):
"Performance counter updating error. Counter name is Time in Resource per second, category name is MSExchange Activity Context Resources. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: Instance 'ad-powershell-defaultdomain'
already exists with a lifetime of Process. It cannot be recreated or reused until it has been removed or until the process using it has exited."
Loading/reloading and recreation of the performance counters does not fix the problem, by Microsoft Support or us. Of course, this error existed before we started having issues; I'd just like to clean it up just in case it's a contributing factor.
Has anyone seen anything similar?We're using a Barracuda load balancer (641), but we've eliminated that as a source of the problem. The CPU spikes and disconnections happen whether or not the load balancer is in use.
This problem is still ongoing, and we're still working with Microsoft Support. Right now they're focused on our environment, but having combed through it numerous times, there's nothing that stands out. I suspect this is a bug in CU7 (yet I would
readily accept our environment being at fault if it means we can identify and resolve the problem), but that's not the road Support is going down.
We've looked at storage I/O on the VM hosts (disk responses are 10 MS or less), added double the CPUs to each mail server (for a total of 8, each), disabled TCP chimney offload, run numerous Experfwiz log collections, etc... Now
the tech is focused on a particular mailbox database being the culprit because it also takes up more CPU when the MAPI app pools are gunning pretty high. I suspect that it is a symptom and not the problem, but I have no choice but to follow his lead.
What is your environment like? Are you also CU7? And did the problem show itself after a cumulative update was applied? -
Exchange 2013 SP1 Installation Errors I Cannot Resolve
Good Afternoon All -
Note: I updated this post an hour after posting. Still no solution, but please see updated info at end of this post)
I'm trying to introduce Exchange into an existing, small environment. The server I'm trying to install it onto is an SBS 2011 server (single server.) Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
had attempted to uninstall it before. Yes, it's being installed onto a server with a DC. I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
Before I started, I made sure all Exchange data had been removed. I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
When I try to install Exchange 2013 SP1, I get the below errors. I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one. I've restarted the server many times when making
changes or applying various updates and still get flagged to restart during installation. I've tried the SBS 2011 repair disc as well, but had many issues with it. In all honesty, the whole server needs to be wiped and re-installed, but
cannot do at this point.
Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below. Also below are system specs. The only edit I made in them is a find/replace for server and domain name.
ExchangeSetupLogs Folder
System Specs
Xeon E31270 3.4Ghz
16gb RAM
Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
C:\ - RAID 1 = 500gb
D:\ - SATA HDD = 320gb
E:\ - SATA HDD = 320GB
Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
Any help would be appreciated - Thanks!
Error:
This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
Without this update, the Outlook Anywhere feature may not work reliably.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then
run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.aspx
Error:
This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from
http://go.microsoft.com/fwlink/?LinkId=260990.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Ben K.
UPDATE
I just tried fixing a few things and tried again. Still no luck. Below is what I changed as well as the errors received. Only option was Retry. Can I just not install it onto this environment?
What I Changed
Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
Installed KB2619234 for Outlook Anywhere
Installed 12 updates - Server fully patched
Exchange Setup Errors
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Thanks Guys -Hi,
Agree. Windows Server 2011 SBS x64 can be the problem.
Thanks,
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 Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support -
Server Exchange 2013 SP1 installation on Hyper-V server
Dear colleges, I seek your help with ExchangeServer 2013 installation on a Hyper-V server issue I've been having.
Getting below errors during prerequisites check of XCHG SVR installation. Installation is done on a Hyper-V server. This server is member of a domain. I have also promoted this server to a Active Directory Domain Controller. In other words there's 2 AD DC
- one is on the main server and the other on this one. The user the installation is run under has ALL required access rights. Please advise as this issue is getting on my nerves. I believe something is wrong setup on a AD DC part. Please suggest what to check
and post on the forum, so somebody can just point out what I am doing wrong.
Error:
The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container. See the Exchange setup log for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit:Got the same errors when ran on the main AD DC server:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\system32>setup /ps /iacceptexchangeserverlicenseterms
'setup' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>h:
H:\>setup /ps /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis FAILED
The Active Directory schema isn't up-to-date, and this user account isn't a
member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
Setup encountered a problem while validating the state of Active Directory:
Couldn't find the Enterprise Organization container. See the Exchange setup lo
g for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.AdInitErrorRule.aspx
The forest functional level of the current Active Directory forest is not W
indows Server 2003 native or later. To install Exchange Server 2013, the forest
functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.CannotAccessAD.aspx
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
H:\> -
Hi Experts,
I am facing issue while installing exchange 2013 sp1 in mixed(2007, 2010 and 2013) environment, the issue is: CAS role not installing/configuring "Echangeweb" (ews) virtual directory if i install only CAS role. If i install CAS role and mailbox
role then there is no issue, everything is fine.
In single CAS role installation, "EWS" folder is creating inside "Exchangeweb" folder but it shows empty folder.
If any one have any idea please let me know, why this is happening? was i am doing anything wrong while installing?
Regards,
Ravi Nalla
Hewlett-Packard
ravinallaHi Ravi,
Agree with Martina. I install Exchange 2013 CAS server and Mailbox server separately. "exchweb" folder exists on Mailbox server only. Here is the exchweb folder information on Mailbox server for your reference.
Here is the ews folder information on CAS server for your reference.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support -
Exchange 2013 incomplete installation - click Next stuck at 0%
Hi All
Recently we're upgrading exchange 2007 sp3 to Exchange 2013, but I encountered a wierd problem during the exchange 2013 install.
Everything was good during schema prep, adprep, domainprep.
During the installation, it had a problem with discoverysearch mailbox, i followed one of the article over the net, which is disabled it and then re-enabled, then successfully resumed installation. (It's 10/14 steps at that time, which is mailbox role)
BUT, few seconds later after resume, the installation window disappear, I am not sure whether it's running at backend or it's just stopped running, so i waited and waited for nearly 1:30 minutes. I checked all the services, it seems to be all started.
I try to run the setup from installation media again, the first window saying is "incomplete installation detected", then I click next, it's just stuck at 0% percent.
I restarted computer, after reboot it's still showing me incomplete installation detected, then click next, it will stay at 0%.
If i try to open ECP page, it throws me an error, same as OWA. For some reason, the ECP doesn't use port 443, instead it's using 444. Both error looks like there's some configurations missing. It looks like the client access role hasn't been installed successfully,
as in my IIS, the default website only shows powershell under its virtual directory.
I am wondering if anyone has experienced any of the above problem, any solutions?
Thank you very muchHi all
I managed to fix this issue by installing exchange 2013 cu1, by running /m:upgrade switch.
Then i found my client access role hasn't been installed (must be something happened during the original installation).
I ticked client access role, and started to install, but it shows this:
08/17/2013 07:50:18.0317] [1] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://QBEXH01.Uptime.local/W3SVC/1/ROOT/owa' on 'QBEXH01'.
[08/17/2013 07:50:18.0317] [1] [ERROR] Cannot create a file when that file already exists. (Exception from HRESULT: 0x800700B7)
[08/17/2013 07:50:18.0317] [1] [ERROR-REFERENCE] Id=CafeComponent___bb7da0d258a640c18755eae1daec22c1 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Looks like it failed to create IIS virtual directory, any ideas?
Much appreicated!
Thank you -
Exchange 2013 CU7 OWA 400 Bad Request after successful login
Scenario:
Exchange 2007/2013 Migration
One
Exchange 2007 Server [removed]
One
Exchange 2013 Server Std, Windows 2012
All mailboxes moved to 2013
- November 27-30 2014
All public folders moved to
2013 - December 2, 2014
Exchange
2007 is still running and has not been removed from the domain, yet. [update]
Exchange
2007 removed from domain - 12-13-14
SSL
Certs are current for: Autodiscover.ExtDom.com, ex13.ExtDom.com, ex13.IntDom.com
Applied
CU6 (Dec 3, 2014) to fix Mobile access issues. Since applying CU6, OWA does not work with the exception of mobile browsers (Chrome - Nexus 7) or Safari 5.1.7 on Windows 7. These browsers get the OWA 2010 theme (Yellow).
User
logs into OWA with Domain\UserName and PWD(IE). After clicking Sign In, page returns Bad Request. No errors logged in w3scv logs.
[update]
CU7 applied 12-11-2014
All
users can connect using Outlook 2013 or Mobile (iPhone & Android)
Exchange
Admin Center (ECP) still works!
Browsers
tested: IE10 (windows 7 x64),Chrome 39.0.2171.71m, Opera 26.0, FireFox 34.0.5, Safari 5.1.7
Attempted:
https://ex13.ExtDom.com/owa
https://ex13.IntDom.com/owa
https://ex13.ExtDom.com/owa?ExchClientVer=15
https://ex13.IntDom.com/owa?ExchClientVer=15
https://localhost/owa
(on Ex 2013 server)
https://localhost/owa?ExchClientVer=15
(on Ex 2013 Server)
Fixes
attempted:
remove
| create Virtual Directories for OWA
Change
authentication through Exchange PowerShell - Integrated/Basic from FBA/Basic
reverted
since change didn’t work.
Run
UpdateCas.ps1
Run
UpdateConfigFiles.ps1
IISReset
(iisReset /NoForce fails)
OWA
(Default Web Site) displays as Version 15.0 (Build 995.29) in EAC. [update] Build 1044.25 (CU7)
Links
used for troubleshooting:
http://community.spiceworks.com/topic/514617-exchange-2013-unable-to-login-to-owa-ecp
https://social.technet.microsoft.com/Forums/ie/en-US/f8aa95d4-19e4-483c-8c4b-b039ab0d0127/400-bad-request-when-logging-in-to-owa-exchange-2013?forum=exchangesvrclients
http://tecfused.com/2013/09/23/exchange-2013-ecp-double-login-error-400/
https://social.technet.microsoft.com/Forums/lync/en-US/c25ce81c-76ea-471a-93ae-eeaf9e5015ac/exchange-2013-owa-error-400-bad-request?forum=exchangesvradmin
http://support.microsoft.com/kb/2871485/en-gbHi,
Does it work if you disable the FBA and only use the basic authentication?
Please also let us know the authentication settings on the Default Web site.
Thanks,
Simon Wu
TechNet Community Support -
Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.
Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11 -
Exchange 2013 CU7 server performance/outage issues.
Hi Forum,
We are constantly faced with incidents from users that the connections are lost with the exchange server. As a result, we hired a consultant to install an new Exchange 2013 environment based on the Microsoft, VM-Ware and NetApp best practices.
We are still having problems with performance issues. From the client prospective, the performance has not changed, weekly hangs are still happening and I’m at my wits end.
This is our configuration:
2 Windows Server 2012 R2 CAS and DB
VM with 4 vCpu, 16GB, 1 Vmxnet3, IPv6 disabled (the Microsoft way)
VM Ware 5.1 U1
Cluster without AAP
DB1 active on Server 1 (Datacenter 1 with 3 host cluster)
DB2 active on Server 2 (Datacenter 2 with 3 host cluster)
Veeam 8 Backup (Move-ActiveMailboxDatabase DB2 -ActivateOnServer Server1 , backup server 2 then Move-ActiveMailboxDatabase back to
Server2.
Exchange is in Online-Mode due to Citrix XD VDI clients.
1300 Mailboxes and 750 users.
NetApp with SATA disks. (1.5TB E: Vol for DB1/1.5TB F: Vol for DB2)
No archiving
Unlimited mailbox sizes.
The problems are:
If we migrate a non-Exchange VM in the same cluster or to\from the same host, this results in a 30 second to 5 min Outlook outage;
If we make both DB’s active on mail server 1 and reboot server 2, this results in a 30 second to 5 min Outlook outage;
If we make both DB’s active on mail server 1 and do a Veeam backup of server 2, sometimes one of the DB’s go back to server 1, on its own;
While monitoring we see that the w3wp.exe and the Microsoft.Exchange.Store.worker.exe are consuming most of the cpu and memory;
What can I do to solve the outages?
Tnx. Timotatty.
Exchange server performance issues.
Hi Forum,
We are constantly faced with incidents from users that the connections are lost with the exchange server. As a result, we hired a consultant to install an new Exchange 2013 environment based on the Microsoft, VM-Ware and NetApp best practices.
We are still having problems with performance issues. From the client prospective, the performance has not changed, weekly hangs are still happening and I’m at my wits end.
This is our configuration:
2 Windows Server 2012 R2 CAS and DB
VM with 4 vCpu, 16GB, 1 Vmxnet3, IPv6 disabled (the Microsoft way)
VM Ware 5.1 U1
Cluster without AAP
DB1 active on Server 1 (Datacenter 1 with 3 host cluster)
DB2 active on Server 2 (Datacenter 2 with 3 host cluster)
Veeam 8 Backup (Move-ActiveMailboxDatabase DB2 -ActivateOnServer Server1 , backup server 2 then Move-ActiveMailboxDatabase back to
Server2.
Exchange is in Online-Mode due to Citrix XD VDI clients.
1300 Mailboxes and 750 users.
NetApp with SATA disks. (1.5TB E: Vol for DB1/1.5TB F: Vol for DB2)
No archiving
Unlimited mailbox sizes.
The problems are:
If we migrate a non-Exchange VM in the same cluster or to\from the same host, this results in a 30 second to 5 min Outlook outage;
If we make both DB’s active on mail server 1 and reboot server 2, this results in a 30 second to 5 min Outlook outage;
If we make both DB’s active on mail server 1 and do a Veeam backup of server 2, sometimes one of the DB’s go back to server 1, on its own;
While monitoring we see that the w3wp.exe and the Microsoft.Exchange.Store.worker.exe are consuming most of the cpu and memory;
What can I do to solve the outages?
Tnx. Timotatty.Hi Simon,<o:p></o:p>
Apparently we are using basic authentication which result in a FailingCode=401 as seen in the Event Log under Active Monitoring --> Probe Results from ECP and others. This
became apparent after reading this blog:
http://blogs.technet.com/b/ehlro/archive/2014/02/20/exchange-2013-managed-availability-healthset-troubleshooting.aspx<o:p></o:p>
We are now overriding some of the monitors which require Forms Based Authentication.<o:p></o:p>
Regarding the other 2 issues we have changed the licensing model for Veeam 8 to allow full throughput which will reduce the backup time and add compression.
The KEMP support team helped us by deselecting Use HTTP/1.1 under View/Modify Services --> ECP –> Modify --> Real Servers. This
now only flags a service (ECP or ActiveSync or OWA) as being down instead of an etire server should one component fail.<o:p></o:p>
I am satisfied but still not happy with the steps required to troubleshoot an Unhealthy Health Sets:<o:p></o:p>
Invoke-MonitoringProbe always returns with: WARNING: Could not find assembly or object type associated with monitor identity '<Healthe Set >\< Probe >'. Please ensure
that the given monitor identity exists on the server.
This makes it very difficult to troubleshoot
Unhealthy Health Sets.
Regards,
Timotatty -
Exchange 2013 CAS incorrectly proxying after mailbox move to Exchange 2013
Hi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
RamanHi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
Raman
Does simply recycling the ActiveSync app pool speed things up?
Also, I would recommend installing CU6 instead of SP1.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
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.
Maybe you are looking for
-
AT&T has great support for WP, why not VZW?
So first the Lumia 928 is released in only black and white, even though Nokia had made a cyan and red version. Why? The Lumia Icon was ready from Microsoft/Nokia to be released in November 2013, but Verizon didn't release it until after the holiday s
-
How see if material exist in the center?
Hi gurus. Iam a abaper and I hene a problem. I am using BAPI_SALESORDER_CREATEFROMDAT2 and ocurrs log error in txt file : The material 40000221 does not exist in the center CE52 / country BR How see if material exist in the center?(transaction ?tabl
-
How to set dynamic color , based on xml element
Hi, We have a requirement, where based on certain conditions, a cell will be shown in a specific color. We would like the coloir to be based on an XML element. The xml element will have values like '#FF00FF' etc.. We tried using xsl attribute with th
-
Open powerpoint encrypted files that are read only
I'm trying to open a powerpoint encrypted file that is read only with keynote version 5.1.1. however keep getting the error message it must first be saved un encrypted. is there a way to mark the file read only so keynote will open it like powerpoint
-
Which MacBook air should I buy??
I have 2 options for buying MacBook air? 1) 11 inch i7 4 GB Ram and 128 GB flash memory 2) 13 inch i5 4 GB Ram and 128 GB flash memory Which laptop will best suit me for word excel PowerPoint and day to day office use. Would be replacing my desktop w