I was installing Exchange 2013 on Server 2012. The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin. There has never been an Exchange instance on this domain. I got past the prerequisite checks, and the installer showed 15 steps, so I walked away. When I came back, I saw this: Step 8 of 15: Mailbox role: Transport service 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: "Unable to set shared config DC.". The only option on the screen was exit, so I did. I checked the start menu, and there were two new Exchange icons, but I did not click them. I ran the installer again, and it detected an incomplete install, the only option was to click next to finish the install, so I clicked next. This time, I eventually got the same error, except the screen showed "Step 8 of 15: Mailbox role: Transport service." I did install some Exchange 2010 prerquisites on the server before Exchange Server 2013 came out, and I can rebuild the server and try the install again if that would be best, but I thought I should post here first and try to work through this since the product is so fresh. Any suggestions?

hey i same problem and try and try not help have some Swedish expert helping me but not good luck yet tryed install in powershell but not helping is that an bug or do we wrong Best Regards Bengt

Hi, Can you tell us the detailed installation steps you installed the DCs ad Exchange Servers? Please double confirm you have installed all the prerequisites. Also see the following video and make sure anything were not miss. http://www.youtube.com/watch?v=YOlrLQhgg1Y Thanks, Simon

I pasted this command from the youtube video: Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation It said it was successful and no restart was needed. Afterwards I ran the setup again, it detected the incomplete installation, I clicked next, it got to step 2 of 3, and then it disappeared. I don't know where it was previously getting to prior to displaying the error. I ran setup again to see if it was complete, and it still said incomplete installation detected. This time, it wouldn't do anything at all, so I finally just exited Regarding detailed installation steps, a server 2008 R2 machine was set up some time ago, and the domain was created on it. I don't remember if it was installed with the 2008 R2 functional level, or if that was raised later, but the current functional level is 2008 R2. A DC with 2012 was added recently using the GUI, installed AD DS services and then performed the additional steps to make it a DC. Another separate 2012 machine was set up and joined to the domain. This is where I am trying to install Exchange. It said all prerequisite checks were met, and even if they weren't, they should certainly be after copying and pasting the powershell command to make sure they are all installed. The video did say to uninstall Visual C++ Redist 2011. I am running RTM server and Exchange installer, and I have Visual C++ Redist 2012, not 2011. Does this need uninstalled? The prerequisite check didn't say it needed uninstalled, and for all I know, the Exchange installer is what put it on. Since the above, I have rebooted the server I am trying to install Exchange on just in case, installed an update for Windows Server 2012 from WSUS, and rebooted again. I then try to run Exchange Setup and still get "Incomplete Installation Detected". After I click on next, it still won't do anything. It says "Setup Progress" and the progres bar is stuck on 0%. One thing I did different than that video is this: I didn't disable malware scanning (on the exchange installer, there is no antimalware software on the server yet). So right now, in addition to my original problem, I guess I have two questions: 1) Should I uninstall Visual C++ Redist 2012 2) Should I start fresh and disable malware scanning (on the Exchange installer)

If you are installing Exchange Server 2013 Preview, then you have to uninstall C++ ... before the Exchange installation. If it is an Exchange Server 2013 RTM, then there is no need to perform the uninstall. No need to disable malware. - ----------------------------- Since the installation is keep on failing... try to perform the following steps (If it is not a domain controller) 1. Rename that server name which is giving error 2. Run this command Install-WindowsFeature RSAT-ADDS Once completed then run the below command Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation Make sure the below 3 prerequisites are installed Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bitMicrosoft Office 2010 Filter Pack 64 bitMicrosoft Office 2010 Filter Pack SP1 64 bit and then run the below command, Point to Installation media file path\Setup.exe /Mode:Install /Roles:ClientAccess, Mailbox, ManagementTools /t D:\Exchange2013 /IAcceptExchangeServerLicenseTerms if any issue.. refer this link - http://msexchange2010.info/archives/2330 Note: Your previous exchange 2013 installation will be in orphaned state.. you have to manually remove the server details using ADSI edit.

I decided to do the ADSI cleanup first and was installing again. Note that all prerequisites except possibly RSAT-ADDS (if the GUI installer doesn't check for it) were previously installed when I was having problems. This time, the install seemed to hang very near the end, and the server started to act very funny (for instance, task manager only showed a process list) until it suddenly logged me off. Now the two icons in the start menu both crash, and it appears to be memory related. Are the hardware requirements for Exchange 2013 higher than those for Exchange 2010? ETA: I re-installed Server 2012 before all of the above. This is on a Server 2012 Hyper-V VM. ETA2: I shut down the VM, added more memory, and started it back up. Everything seems to function, and if I run setup.exe from the Exchange ISO, it appears to be for adding roles with no roles available, perhaps implying everything is installed. Is there anything I can/should do to verify the consistency of the install?

Low memory could be the issue in your case.. make sure you have more than 2 GB of RAM allocated to your Exchange server 2013 To confirm the successful installation, open the setuplogs from exchangesetuplogs folder on the c drive and check the status. If you are able to login to ecp and owa and EMS... then it confirms that everything is working fine. from EMS, type Get-ExchangeServer and see both the roles are installed..

OK, ExchangeSetup.log looks like this toward the end: [11/05/2012 21:13:10.0036] [2] [ServiceControl.ps1] (1) Enter: RestoreServiceAndDependents 'MSExchangeIMAP4BE'. [11/05/2012 21:13:10.0036] [2] [ServiceControl.ps1] 'MSExchangeIMAP4BE' did not exist. [11/05/2012 21:13:10.0036] [2] [ServiceControl.ps1] (1) Starting MSExchangeIMAP4BE... [11/05/2012 21:13:10.0036] [2] Active Directory session settings for 'start-SetupService' are: View Entire Forest: 'True', Configuration Domain Controller: 'PRDAD1.prd-inc.com', Preferred Global Catalog: 'PRDAD1.prd-inc.com', Preferred Domain Controllers: '{ PRDAD1.prd-inc.com }' [11/05/2012 21:13:10.0036] [2] Beginning processing start-setupservice -ServiceName:'MSExchangeIMAP4BE' -ErrorVariable:'script:serviceControlError' -IgnoreTimeout:'True' [11/05/2012 21:13:10.0333] [2] [WARNING] Service 'MSExchangeIMAP4BE' failed to reach status 'Running' on this server. [11/05/2012 21:13:10.0333] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'. [11/05/2012 21:13:10.0333] [2] Previous service status query time is '11/5/2012 4:13:10 PM'. [11/05/2012 21:13:10.0333] [2] Current service status query time is '11/5/2012 4:13:10 PM'. [11/05/2012 21:13:10.0333] [2] Will wait '25000' milliseconds for the service 'MSExchangeIMAP4BE' to reach status 'Running'. The last 5 lines repeat 29 times before the log suddenly ends. It doesn't really end, but it's like this: [11/05/2012 21:25:21.0926] [2] Service 'MSExchangeIMAP4BE' failed to reach status 'Running' on this server after waiting for '25000' milliseconds. [11/05/2012 21:25:21.0926] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'. [11/05/2012 21:25:21.0926] [2] Previous service status query time is '11/5/2012 4:24:56 PM'. [11/05/2012 21:25:21.0926] [2] Current service status query time is '11/5/2012 4:25:21 PM'. [11/05/2012 21:25:21.0926] [2] Will wait '25000' milliseconds for the service 'MSExchangeIMAP4BE' to reach status 'Running'. [11/05/2012 21:26:13.0459] [0] ********************************************** [11/05/2012 21:26:13.0475] [0] Starting Microsoft Exchange Server 2013 Setup [11/05/2012 21:26:13.0475] [0] ********************************************** Obviously that's when I tried to run setup again after getting logged out due to being out of memory. Note that I had 6GiB assigned to the VM. Things seemed to work better after increasing it to 8GiB, but I couldn't finish setup regardless. Given that I didn't get anything in the log indicating setup finished successfully, but setup obviously thinks it did when it re-runs because it sees the expected installed components, is there anything I can do to perform a repair? Should that be necessary? Would it be best to rebuild and start fresh again? I did try to go to http://<serverip> and got 403 forbidden. I then tired to go to http://<serverip>/owa and got 503 unavailable (in case it isn't obvious, I'm not sure where to connect to ECP or OWA). Next, I loaded IIS, and tried to connect to the server (while on the server). I got an error that IIS couldn't be connected to because the SMTP service was not installed. Then I looked again and noticed I was in IIS 6.0 Manager. IIS 8.0 Manager showed me what I needed. I am not sure why IIS 6.0 Manager is installed since I did a clean build and followed the steps you mentioned. Nonetheless, http://<serverip>/ecp also returns 503 unavailable. EMS loaded fine yesterday, but seems to hang today at "Connecting to <serverfqdn>." As such, I haven't run Get-ExchangeServer. Eventually it put up an error and then tried to connect again. I couldn't seem to highlight in the PS instance to copy the error, but it failed to connect amongst other things. Exchage Toolbox doesn't appear to connect today either, even though it did yesterday.

Seems like you are installing Exchange 2013 Preview. error message you mentioned on the last part will occur on that version. Better, rebuild the setup by downloading the RTM version of Exchange 2013.

I downloaded from Microsoft's Licensing Service Center using the java download manager, so it's not likely to be preview. Nonetheless, I will rebuild and try again with 8 GiB. Is there any quick way to confirm the image is RTM vs previeW? It did install with Visual C++ 2012 installed, which I think is a good indicator... Is there an updated hardware requirement or IPD doc I should review since I am installing 2013? I came up with 6GiB from "IPD - Exchange Server 2010 version 1.2.docx".

I've tried three times since my last post, following http://msexchange2010.info/archives/2330 as closely as possible the most recent time. I am consistently getting the same error that appears to imply I don't have write access to the domain. I don't understand this, because I am using the same domain admin account I have been using all along. Nonetheless, here is the powershell output starting with the first Exchange setup.exe step (all other steps were already performed, all available updates were installed, and the server was rebooted prior to this): Windows PowerShell Copyright (C) 2012 Microsoft Corporation. All rights reserved. PS (domain admin home)> D: PS D:\> .\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms 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 D:\> .\Setup.exe /PrepareAD /OrganizationName:PRD-INC /IAcceptExchangeServerLicenseTerms 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 D:\> .\Setup.exe /Mode:Install /Roles:ClientAccess, Mailbox, ManagementTools /t E:\Exchange /IAcceptExchangeServe rLicenseTerms 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 Client Access role: Front End Transport service Client Access role: Client Access Front End service Performing Microsoft Exchange Server Prerequisite Check Configuring Prerequisites COMPLETED Prerequisite Analysis COMPLETED Configuring Microsoft Exchange Server Preparing Setup COMPLETED Stopping Services COMPLETED Copying Exchange Files COMPLETED Language Files COMPLETED Restoring Services COMPLETED Language Configuration COMPLETED Exchange Management Tools COMPLETED Mailbox role: Transport service COMPLETED Mailbox role: Client Access service COMPLETED Mailbox role: Unified Messaging service COMPLETED Mailbox role: Mailbox service FAILED The following error was generated when "$error.Clear(); if ($RoleIsDatacenter -ne $true) { if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue) { $sysMbx = $null; $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}"; $dispName = "Microsoft Exchange"; Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name."); $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 ); if ($mbxs.Length -eq 0) { Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName."); $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController); if ($dbs.Length -ne 0) { Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name."); $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1); if ($arbUsers.Length -ne 0) { Write-ExchangeSetupLog -Info ("Enabling mailbox $name."); $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0 ].Identity; } } } else { if ($mbxs[0].DisplayName -ne $dispName ) { Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName."); Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force; } $sysMbx = $mbxs[0]; } # Set the Organization Capabilities needed for this mailbox if ($sysMbx -ne $null) { # We need 1 GB for uploading large OAB files to the organization mailbox Write-ExchangeSetupLog -Info ("Setting mailbox properties."); set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions :$true -MailRouting:$true -MaxSendSize 1GB -Force; } else { Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name."); } } else { Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission." } } " was run: "Database is mandatory on UserMailbox.". The following error was generated when "$error.Clear(); if ($RoleIsDatacenter -ne $true) { if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue) { $sysMbx = $null; $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}"; $dispName = "Microsoft Exchange"; Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name."); $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 ); if ($mbxs.Length -eq 0) { Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName."); $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController); if ($dbs.Length -ne 0) { Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name."); $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1); if ($arbUsers.Length -ne 0) { Write-ExchangeSetupLog -Info ("Enabling mailbox $name."); $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0 ].Identity; } } } else { if ($mbxs[0].DisplayName -ne $dispName ) { Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName."); Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force; } $sysMbx = $mbxs[0]; } # Set the Organization Capabilities needed for this mailbox if ($sysMbx -ne $null) { # We need 1 GB for uploading large OAB files to the organization mailbox Write-ExchangeSetupLog -Info ("Setting mailbox properties."); set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions :$true -MailRouting:$true -MaxSendSize 1GB -Force; } else { Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name."); } } else { Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission." } } " was run: "Database is mandatory on UserMailbox. Property Name: Database". The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder. PS D:\> I am cleaning out in ADSI and rebuilding the server for now, because the server is behaving oddly (not as oddly as it was with 6GiB, but oddly, nonetheless). I probably won't try to install Exchange again before tomorrow. What should I do to prevent encountering the above again and/or if I encounter it again?

OK, I tried again this morning after trying to be a lot more thorough on cleaning up AD. I found and deleted some users I missed before. The account in question is in the Schema Admin group, but can't delete the CN=msExch-* items from the Schema. I am not sure if that is relevant, but thought I should point it out. After cleaning everything else up that I could find, I tried again and got the same error. This time I looked at the log again and it's like this: [11/07/2012 14:13:39.0741] [2] [Microsoft Cmdlet Extension Agent] Read Email Address Policy for organization "" from domain controller PRDAD1.prd-inc.com. [11/07/2012 14:13:39.0741] [2] [Microsoft Cmdlet Extension Agent] Found Email Address Policy "Default Policy". [11/07/2012 14:13:39.0741] [2] Processing object "prd-inc.com/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}". [11/07/2012 14:13:39.0741] [2] [ERROR] Database is mandatory on UserMailbox. [11/07/2012 14:13:39.0741] [2] [ERROR] Database is mandatory on UserMailbox. [11/07/2012 14:13:39.0741] [2] [ERROR] Database is mandatory on UserMailbox. [11/07/2012 14:13:39.0741] [2] [WARNING] The object prd-inc.com/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted, and it's in an inconsistent state. The following validation errors happened: [11/07/2012 14:13:39.0741] [2] [WARNING] Database is mandatory on UserMailbox. [11/07/2012 14:13:39.0741] [2] [WARNING] Database is mandatory on UserMailbox. [11/07/2012 14:13:39.0741] [2] Ending processing get-mailbox [11/07/2012 14:13:39.0741] [2] Ending processing set-mailbox [11/07/2012 14:13:39.0756] [2] Active Directory session settings for 'Get-Mailbox' are: View Entire Forest: 'True', Configuration Domain Controller: 'PRDAD1.prd-inc.com', Preferred Global Catalog: 'PRDAD1.prd-inc.com', Preferred Domain Controllers: '{ PRDAD1.prd-inc.com }' [11/07/2012 14:13:39.0756] [2] Beginning processing get-mailbox -Filter:'name -eq $name' -IgnoreDefaultScope:'True' -ResultSize:'1' [11/07/2012 14:13:39.0756] [2] Searching objects of type "ADUser" with filter "(&((|((RecipientTypeDetails Equal RoomMailbox)(RecipientTypeDetails Equal EquipmentMailbox)(RecipientTypeDetails Equal LegacyMailbox)(RecipientTypeDetails Equal LinkedMailbox)(RecipientTypeDetails Equal UserMailbox)(RecipientTypeDetails Equal DiscoveryMailbox)(RecipientTypeDetails Equal TeamMailbox)(RecipientTypeDetails Equal SharedMailbox)))(Name Equal DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852})))", scope "SubTree" under the root "$null". [11/07/2012 14:13:39.0756] [2] Previous operation run on global catalog server 'PRDAD1.prd-inc.com'. [11/07/2012 14:13:39.0756] [2] Preparing to output objects. The maximum size of the result set is "1". [11/07/2012 14:13:39.0788] [2] [WARNING] The object prd-inc.com/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted, and it's in an inconsistent state. The following validation errors happened: [11/07/2012 14:13:39.0788] [2] [WARNING] Database is mandatory on UserMailbox. [11/07/2012 14:13:39.0788] [2] [WARNING] Database is mandatory on UserMailbox. [11/07/2012 14:13:39.0788] [2] Ending processing get-mailbox [11/07/2012 14:13:39.0788] [1] The following 2 error(s) occurred during task execution: [11/07/2012 14:13:39.0788] [1] 0. ErrorRecord: Database is mandatory on UserMailbox. [11/07/2012 14:13:39.0788] [1] 0. ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox. [11/07/2012 14:13:39.0803] [1] [ERROR] The following error was generated when "$error.Clear(); if ($RoleIsDatacenter -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: "Database is mandatory on UserMailbox.". [11/07/2012 14:13:39.0803] [1] [ERROR] Database is mandatory on UserMailbox. [11/07/2012 14:13:39.0803] [1] 1. ErrorRecord: Database is mandatory on UserMailbox. Property Name: Database [11/07/2012 14:13:39.0803] [1] 1. ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox. Property Name: Database at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow) at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.Validate(TDataObject dataObject) at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate() at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate() at Microsoft.Exchange.Management.RecipientTasks.SetMailEnabledRecipientObjectTask`3.InternalValidate() at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate() at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate() at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord() [11/07/2012 14:13:39.0803] [1] [ERROR] The following error was generated when "$error.Clear(); if ($RoleIsDatacenter -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: "Database is mandatory on UserMailbox. Property Name: Database". [11/07/2012 14:13:39.0803] [1] [ERROR] Database is mandatory on UserMailbox. Property Name: Database [11/07/2012 14:13:39.0803] [1] [ERROR-REFERENCE] Id=SystemAttendantDependent___590e51a8a98846d3a7fa8ddcc5472c74 Component=EXCHANGE14:\Current\Release\PIM Storage\Discovery [11/07/2012 14:13:39.0803] [1] Setup is stopping now because of one or more critical errors. [11/07/2012 14:13:39.0803] [1] Finished executing component tasks. [11/07/2012 14:13:39.0819] [1] Ending processing Install-MailboxRole [11/07/2012 14:13:39.0834] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder. [11/07/2012 14:13:39.0834] [0] End of Setup [11/07/2012 14:13:39.0834] [0] ********************************************** One thing I noticed in that log that seems odd is the first line (which I otherwise wouldn't have included) doesn't have an organization name even though I provided one. Beyond that, the log seems to indicate corruption/inconsistency, but I don't know why that would be. I'm still lost here, and any input on how to confirm my ISO is RTM or deal with this new error would be appreciated.

After some searching, I found this: http://support.microsoft.com/kb/978776 That isn't the account I was getting the error from, and the account I was getting an error from had a space in it, which seemed odd. I was going to try to perform the fix from that, but wasn't sure how to deal with the space in the UPN, so I just deleted the account and ran the setup command again. That allowed setup to complete successfully. The DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} account was not recreated. I am, again, not sure I have a good install... I rebooted the server and then triet to load the Exchange Toolbox, which crashed, Exchange Management Console, which returned an out of memory error even though there were 3 GiB free (and the server is NOT acting weird for the first time), and then tried to launch the Exchange Management Console again, but got an error stating that it failed to connect to an Exchange server in the current site (after a whole lot of red text including more out of memory errors in spite of the fact that memory usage never spiked). Next, I tried to connect to http://server/owa and http://server/ecp, and didn't have any luck (not even the errors I was getting before) in spite of the fact that IIS Manager listed them before the reboot. Then I noticed that Task Manager shows 8.4/8.4 GiB committed (memory) in spite of only having 4.7 GiB in use. Are there any good instructions for completely cleaning out AD from Exchange 2013 and starting fresh?

OK, I rebooted with more memory and the programs all seemed to work, but IIS still didn't. I tried using the IPV4 address instead of the server name, and then I got 403 forbidden for http://<serverip>/, http://<serverip>/ecp, and http://<serverip>/owa. Does Exchange 2013 not work with IPV6? If it does, does it not work with private addressing? Additionally, should this install be clean in spite of the initial Mailbox Service install failure, not having enouh memory on the first reboot after install completion, and lack of a DiscoverySearchMailbox account?

My Suggestion, Start fresh, format the server. Install windows Install Prerequisite for Exchange 2013 Install Prerequisite for Exchange 2013 RTM. You can download RTM from here.. Post the update.... Gulab Prasad, gulab@exchangeranger.com My Blog | Z-Hire Employee Provisioning App

I tried one more time before "dowloading RTM" (as I said, I'm pretty sure I already have RTM, for multiple reasons). It worked! I'm not sure what was different that made it work, but I have my guesses. To start with, I found this: http://technet.microsoft.com/en-us/exchange/fp179701 Obviously I should have done this from the get go, but I must've assumed it didn't exist this early in the release cycle (because I had a lot of trouble finding similar information for System Center 2012 later in the release cycle than this). I used the "get started" section. Beyond following the installation instructions there (which may or may not have been any different, but aren't much different if at all). I also increased the VM to 16 GiB of RAM and forced the swap file to 16394 MiB (as outrageous as that seems to me, SWAP=RAM+10MiB was listed in the hardware requirements). The DiscoverySearchMailbox account still has a space in the name before the ID, so I am guessing the RAM is what solved the problem since nothing else is so obviously different (to me) in this attempt. Nonetheless, if gytepr proposes someone else's response as an answer because it solved his/her problem, I will mark that post as an answer in addition to this one.

I was installing Exchange 2013 on Server 2012. The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin. There has never been an Exchange instance on this domain. I got past the prerequisite checks, and the installer showed 15 steps, so I walked away. When I came back, I saw this: Step 8 of 15: Mailbox role: Transport service 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: "Unable to set shared config DC.". The only option on the screen was exit, so I did. I checked the start menu, and there were two new Exchange icons, but I did not click them. I ran the installer again, and it detected an incomplete install, the only option was to click next to finish the install, so I clicked next. This time, I eventually got the same error, except the screen showed "Step 8 of 15: Mailbox role: Transport service." I did install some Exchange 2010 prerquisites on the server before Exchange Server 2013 came out, and I can rebuild the server and try the install again if that would be best, but I thought I should post here first and try to work through this since the product is so fresh. Any suggestions? I got the same error when I setup Exchange 2013 on DC Server (VM). But it was installed completely when I setup Exchange 2013 on other VM server.

I got the same issue, I first made some manual operations, (deleting mailbos object and federated mailbox etc..) I cannot install client acces in GUI mode, It says uncompleted exchange setup and its stuck at Setup initialing %0 I start setup from command line and it completed successfully.

hello, this error occure because the IPv6 is disabled in the domain controller server, check that IPv6 is enabled in all your dc server and also exchange server i have the same problem because my second dc, have IPv6 disabled Thanks

hello, this error occure because the IPv6 is disabled in the domain controller server, check that IPv6 is enabled in all your dc server and also exchange server i have the same problem because my second dc, have IPv6 disabled Thanks

Thanks sunsimo. I've enabled IPv6 and it completed the installation.

While IPv6 was not relevant to my issue, I will mark sunismo's post as an answer since it helped Igorek24 solve a similar problem.

Same error here also; Role installation stuck at 82% complete Server is w2K12 Std, 16Gb mem, non DC See the following in the eventlogs? DCOM was unable to communicate with the computer CAS.domain.local using any of the configured protocols; requested by PID 1670 (C:\Program Files\Microsoft\Exchange Server\V15\bin\ExSetup.exe).

I am getting the same error as well on a fresh Server 2012 install, IPv6 is enabled and I have executed the installer with elevated privileges using the domain admin account. All prerequisites have been installed and in the proper order. I have got this error message numerous times through several uninstall, cleanup, reinstall sessions. I have even scrapped the server install twice and rebuilt it from the ground up. Does anyone have any ideas as to why I am receiving this error message "Unable to set shared config DC."?? Now, I only have 4GB ram available in this system. Could this have anything to do with this constant error. Any help in this matter is greatly appreciated as I am under then gun to get this email server setup and working. Kevin kdbglobal@gmail.com

Hi Kevin, Is IPc6 enabled on DC? If its not, disable it on your exchange server, also disable firewall on dc and exchange and see if this Note: Do not enable IPv6 on your DC if its disabled or disable if its enabled.

Thanks for your reply Igor. IPv6 is enabled on the DC and exchange server as well. I kept it enabled based on other resources saying that it must be enabled. Also, I have tried configuring it with the static equivalent of my IPv4 address and this has not seemed to make a difference. I will try it again with the firewall disable on both servers. Hopefully this helps. Also, does it matter that I only have 4GB ram on the exchange server?

4GB ram is sufficient for installing it and it shouldn't be a problem. This error has to do something with communication between DC and the server that you are installing exchange on.