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 much

Hi 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

Similar Messages

Exchange 2013 issues - (new send email Stuck in Drafts not send)

Exchange 2013 issues - (new send email Stuck in Drafts folder not send)

I am also having this issue.
server 2012 VM with exchange 2013. plenty of resources, more than recommended so cannot be a BAck Pressure issue especially as no clients are connected yet.
In the early stages of setup and testing, mail sent to other mailboxes worked fine in outlook 2007 and OWA but after a few issue that developed and are now resolved, any e-mail send within outlook or OWA just goes straight into the drafts folder.
I tried, DNS setting changes under roles, on the server, on DNS server, MX DNS records, increased resources, looked at received connectors, changed and even deleted send connectors as this is not required for internal mail. Tried changing authentication
types but then outlook won't connect to, staying with Basic Auth.
Have not been able to test inbound e-mail as this is going to replace a production server and is not ready, although I could probably simulate a route from another server and push e-mail to it. Will try tomorrow.
I have spent about 20 hours trying to figure this out and made probably 40 changes. Change, test, rollback etc. Been searching through loads of forums and technet sites all with no help.
All services are started, server has been rebooted several times.
It is also an AD server and has both Exchange roles installed. There is no reason why it should not work. This is so frustrating, we don't have these issues with the now end of life Scalix, or MDaemon or Zimbra. Pity the client wanted a Microsoft solution.
To be honest there are not a lot of things that cannot be changed in ECP although there is more under exchange powershell however I am not familiar with all the commands yet. I have resorted to watching training videos even though I am a seasoned IT Pro, although
not so much with exchange it seems.
I have seen many people have this issue on Exchange 2007, 2010 and 2013. Someone must know how to resolve this or find a work around?
So far I have an expensive solution the client has purchased that I cannot get running properly.
Aside from this issue, I really like the new Server 2012 and new Hyper-V.
I was about to install Exchange Server 2013 on a physical machine due to this f#ckin' issue. But a post for the DNS change has saved my life:
http://social.technet.microsoft.com/Forums/en-US/exchangeserverpreview/thread/04c0147b-f4e3-4041-a566-310854e71068/ (rafael9908's answer)
And thanks Jesper Bernle for excellent info provided by your link.

Exchange 2013 CU6 installation hangs on step 9: Languages

Just had Exchange 2013 CU6 update hang on Step 9 of 18: Languages. It was stuck at 0% for almost an hour. I was able to get it moving forward by disabling SCEP 2012 by killing the process and deselecting check certificate for server certificate
revocation in IE. Both steps were taken nearly simultaneously and the install process for Exchange jumped up immediately. Both steps were taken based on info from:
https://social.technet.microsoft.com/Forums/exchange/en-US/2a346a37-d092-4189-8a07-e8a9971925f1/cu2-installation-hangs-on-step-9-languages?forum=exchangesvrdeploy
and
https://social.technet.microsoft.com/Forums/exchange/en-US/0975bb5e-f270-4e39-abf3-70809cd98161/exchange-2010-sp3-installation-hangs-language-pack-hell
Just wanted to post that this issue was encountered on CU6 as well. Has anyone had a similar experience or able to tell which of these two steps (or both) is actually needed?

Hello,
Thanks a lot for sharing, saved my day!
Cheers:)

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:\>

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

Exchange 2013 SP1 Installation

Hello
After installation on windows domain server/controller 2012 R2.
I got this message:
VERBOSE: Connecting to GolfServer.GOLFKLUB.local.
New-PSSession : [golfserver.golfklub.local] Connecting to remote server golfserver.golfklub.local failed with the follo
wing error message : The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication
mechanism, but the destination computer (GolfServer.GOLFKLUB.local:80) returned an 'access denied' error. Change the c
onfiguration to allow Kerberos authentication mechanism to be used or specify one of the authentication mechanisms supp
orted by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the c
lient computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as th
e remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanis
ms reported by server: Digest Negotiate For more information, see the about_Remote_Troubleshooting Help topic.
I tried to find solution on many forums and I also check other erros in Event Log and Kerberos...
I also cannot connect to Administration center.
Can anyone help me, please.
Thank you very much

Hi VachtiCZ,
Thank you for your question.
By the error, we could do the following steps to troubleshoot:
If there are another application which is installed on GolfServer.GOLFKLUB, we could open IIS and navigate Default Web Site to check if
the port 80 has been used by another application. if that we could change the port of application.
Check if we have disable the Kerberos authentication
a. Run gpedit.msc in Run
b. Navigate Computer Configuration>Administrative Templates>Window Components>Window Remote Management(WinRM)>WinRM Service
c. Check if we have selected “Enable” on Disallow Kerberos authentication
d. Then we could use “gpupdate /force” to update group policy.
I also cannot connect to Administration center
A: It was caused by the above error. So if we solve this error, we will access EAC. if there are coexistence in organization, for example Exchange 2010, we could refer to the following link to access EAC:
https://technet.microsoft.com/en-us/library/jj150562(v=exchg.150).aspx
In addition, I strongly suggest we didn’t install Exchange server on Domain controller on production.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

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

Update Exchange 2013 CU5 to CU7 - Installation Order

Hi,
I have a multi-site, multi-DAG, Exchange 2010 and Exchange 2013 CU5 installation. All servers are multi-role. We are about to commence a server update to CU7 for all of the Exchange 2013 Servers.
What is the Microsoft supported order in which to upgrade the servers?
Can I do the upgrades over a number of nights, does everything need upgrading together, should I do it site at a time or a DAG at a time?
Are there any TechNet articles which explain the supported method? It is important that during the update to CU7 the installation stays in a supported configuration.
Thanks in advance.

Hi,
As Andy suggested, you need to upgrade Mailbox servers and then upgrade Client Access servers. What's more, if your DAG have more nodes, at first, you need upgrade all non-PAM nodes and then upgrade PAM node.
Here is a helpful blog for your reference.
How to Apply Exchange Server 2013 RTM to Cumulative Update 1 (Note: Though it is upgrading from Exchange RTM to CU1, it also applies to upgrading from Exchange 2013 CU5 to CU7 about the required order issue.)
http://blogs.technet.com/b/justin_gao/archive/2013/04/09/you-need-to-know-how-to-apply-exchange-server-2013-rtm-to-cumulative-update-1.aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Move Exchange 2013 installation to new virtual machine

Currently have: 1 virtual server - Server 2012 (DC, Global Catalog), Exchange 2013 CU1 installation (yes I know- dont install Exchange on DC etc etc ... ). Server2012/Exchange2013 is installed on one VMDK, EDB and logs are saved on another VMDK.
Want to do: Create second virtual machine and install Server 2012 (different name), add it as a member to the same domain (also in the same network), install Exchange 2013, move all mailboxes to the new server, uninstall the old Exchange 2013.
Question is- is it possible to somehow unmount the existing database (I am only using one database for mailboxes and public folders) and mount it to the new server or do I have to create a new database on the new server and move the mailboxes there? I've
heard that the Exchange EDB databases were supposed to be portable between same versions of Exchange.
Any advice is appreciated.

Hi,
Agree with Andy, to avoid down time, we can depend on database portability.
And here are the steps you can refer to:
1. Install new Exchange server on the member server.
2. Move Mailbox Database using Database Portability:
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx
3. Move the public folders (if any), re-home the offline address book, and move your SMTP connectors
http://support.microsoft.com/kb/822931
4. Remove the old Exchange server.
Thanks,
Angela Shi
TechNet Community Support
Thanks for the reply.
I'm a bit confused on the instructions from
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx- does step 4 instruct me to overwrite the newly created database (on the new server) with the old database and then mount it on the new server? Also, as the public folders are now in
a mailbox on the same database- aren't they moved with the database without extra hassle?
Also the link you gave me in Step 3 in your post refers to Exchange 2003.
Thanks in advance.

Exchange 2013 CU2 will not install, Exchange is now in an unuseable state.

I have downloaded Exchange 2013 CU2 and attempted to install it from a local drive. Exchange 2013 is installed on a Server 2012 Standard VM in Hyper-V. I ran the two following commands before trying to install
setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
Upon trying to run the installer, I recieve the following error.
Error:
The following error was generated when "$error.Clear();
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                " was run: "AuthorizationManager check failed.".
During my first install attept, the error was on step 4 of 15. I have tried to rerun the setup with no luck. I noticed the installer leaves all the Exchange services disabled, as well as winmgmt, remoteregistry, w3svc, iisadmin. These four services
are the critical services the errors refer to. I have verified my execution policy is correct
PS C:\Windows\system32> Get-ExecutionPolicy -list
Scope
ExecutionPolicy
MachinePolicy
Unrestricted
UserPolicy
Undefined
Process
Undefined
CurrentUser
Undefined
LocalMachine
RemoteSigned
Upon trying to rerun the setup, I have ran the following commands in order to start the critical services manually
Get-Service-name
winmgmt,
remoteregistry,
w3svc,
iisadmin
|
set-service -startuptype
automatic
Get-Service-name
winmgmt,
remoteregistry,
w3svc,
iisadmin
|
Start-Service
No matter what I do, the Exchange 2013 CU2 installer seems to fail. I'd appreciate any possible help with this.
Thanks,
Chris
To add to what I posted, I also have the following error in the event log.
[07/22/2013 13:57:01.0279] [1] Executing:
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
[07/22/2013 13:57:01.0373] [1] The following 1 error(s) occurred during task execution:
[07/22/2013 13:57:01.0373] [1] 0. ErrorRecord: AuthorizationManager check failed.
[07/22/2013
13:57:01.0373] [1] 0. ErrorRecord:
System.Management.Automation.PSSecurityException: AuthorizationManager
check failed. ---> System.Runtime.InteropServices.COMException: The
service cannot be started, either because it is disabled or because it
has no enabled devices associated with it. (Exception from HRESULT:
0x80070422)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObject.Initialize(Boolean getObject)
   at System.Management.ManagementObject.Get()
   at System.Management.Automation.PsUtils.GetParentProcess(Process current)
   at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId, ExecutionPolicyScope scope)
   at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId)
   at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason)
at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo
commandInfo, CommandOrigin origin, PSHost host, Exception& reason)
at
System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
commandInfo, CommandOrigin origin, PSHost host)
   --- End of inner exception stack trace ---
at
System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
commandInfo, CommandOrigin origin, PSHost host)
   at
System.Management.Automation.CommandDiscovery.ShouldRun(ExecutionContext
context, PSHost host, CommandInfo commandInfo, CommandOrigin
commandOrigin)
   at
System.Management.Automation.CommandDiscovery.LookupCommandProcessor(CommandInfo
commandInfo, CommandOrigin commandOrigin, Nullable`1 useLocalScope,
SessionStateInternal sessionState)
   at
System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String
commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
   at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
at
System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor
pipe, CommandParameterInternal[] commandElements, CommandBaseAst
commandBaseAst, CommandRedirection[] redirections, ExecutionContext
context)
   at
System.Management.Automation.PipelineOps.InvokePipeline(Object input,
Boolean ignoreInput, CommandParameterInternal[][] pipeElements,
CommandBaseAst[] pipeElementAsts, CommandRedirection[][]
commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
[07/22/2013 13:57:01.0373] [1] [ERROR] The following error was generated when "$error.Clear();
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                " was run: "AuthorizationManager check failed.".
[07/22/2013 13:57:01.0373] [1] [ERROR] AuthorizationManager check failed.
[07/22/2013
13:57:01.0373] [1] [ERROR] The service cannot be started, either
because it is disabled or because it has no enabled devices associated
with it. (Exception from HRESULT: 0x80070422)
[07/22/2013
13:57:01.0388] [1] [ERROR-REFERENCE]
Id=AllRolesMidFileCopyComponent___af0f15afe35c4e7cba121e546f405214
Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07/22/2013 13:57:01.0388] [1] Setup is stopping now because of one or more critical errors.
[07/22/2013 13:57:01.0388] [1] Finished executing component tasks.
[07/22/2013 13:57:01.0435] [1] Ending processing Start-MidFileCopy
[07/22/2013 13:58:09.0121] [0] End of Setup
[07/22/2013 13:58:09.0121] [0] **********************************************
I also have these two errors in event viewer that keep occuring.
Event 2280, IIS-W3SVC-WP
The Module DLL C:\Program Files\Microsoft\Exchange Server\V15\Bin\kerbauth.dll failed to load. The data is the error.
Event 2300, IIS-W3SVC-WP
The
worker process cannot access the CLR configuration file at 'C:\Program
Files\Microsoft\Exchange
Server\V15\bin\GenericAppPoolConfigWithGCServerEnabledFalse.config'.
Verify that the file exists and that the worker process has read access
to the file.

I kept quickly running the following two commands while the install was happening
Get-Service-name
winmgmt,
remoteregistry,
w3svc,
iisadmin
|
set-service -startuptype
automatic
Get-Service-name
winmgmt,
remoteregistry,
w3svc,
iisadmin
|
Start-Service
This caused the install to succeed.

Outlook 2010 connected to Exchange 2013 prior to coexistence

I installed Exchange 2013 into the environment (Exchange 2010 SP3) and left it at that (ie no additional config). I noticed Outlook 2010 client connected to Exchange 2013 somehow (it got a cert warning). Why would Outlook connect to the new
Exchange 2013 server like that? Although I enabled Outlook Anywhere, it is not trying RPC/HTTP first, but rather RPC/TCP.

Hi,
By design, if the user mailbox located in Exchange 2010 server, the Outlook client will connect to Exchange 2010 server automatically.
According to your description, I found that we have nothing additional configuration on Exchange 2013. So, only server name and internal services' URLs are configured automatically during the Exchange 2013 server installation.
If it has no mailbox located in Exchange 2013, it is odd that Outlook client connect Exchange 2013 first.
I suggest running "Test E-mail AutoConfiguration" in Outlook to verify which Exchange server the Outlook connected.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Anyone done SBS 2008 to Exchange 2013 migration - disable IPv6 on SBS?

IPv6 enabled on ours without any problems. THanks for the links Anil, had not heard of those problems before

Well, considering over the scenario you have mentioned, I would like to refer you on this informative article that covers few parts of causes when disabling IPV6 on Exchange 2013 Server installation : http://mike-graham.co.uk/blog/2013/08/12/disabling-ipv6-on-exchange-2013-servers-causes-problems/Here is a well documented technet resource that also provides step-wise instructions when proceeding to migrate from Exchange 2007 to 2013 by checking all the required prerequisites : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migra...Moreover, while need to migrate users mailboxes from Exchange 2007 to 2013, you may also consider on LepideMigrator for Exchange tool that provides a hassle-free environment to get this job done without having downtime or any further interruption.

New Installtion of Exchange 2013-Help

Hi Guys,
I wonder if someone can point me in the right direction.
I have just installed my first Windows Server 2012 R2 , which went fine, then Exchange 2013 and installation went fine. have setup one user on the system and connected Exchange to the user, also setup in mail flow send connectors as well not an issue.(We
do have internet on the server)
But when I try and send email using OWA they seat in the Draft folder, for the life on me I can't find why the emails are not going out.
Can some point me in the right direction as to what I have missed out.
Many Thanks.
JP
JP

Hi JP,
I thought its a lab setup :o.
Use the info below to set expectations with your management.
Installing Exchange on a domain controller is not recommended
Exchange services may not start correctly when the domain controller is also a global catalog server.
This point might be the issue you are facing. As Exchange needs atleast 1 GC and if your's is the only one then it has to be a GC too, and problems would start. It's not like it won't work, but reliability is in question.
Installing Exchange 2013 on directory servers
For security and performance reasons, we recommend that you install Exchange 2013 only on member servers and not on Active Directory directory servers. However, you can't run DCPromo on a computer running Exchange 2013. After Exchange 2013 is installed,
changing its role from a member server to a directory server, or vice versa, isn't supported.
Let me ask you a question, is this the only DC in your enviroment or only Physical server.
If no then refer below for the minimum supported Forest\Domain Levels:
Windows Server 2003 Standard Edition with Service Pack 2 (SP2) or later (32-bit or 64-bit)
Active Directory must be at Windows Server 2003 forest functionality mode or higher.
You might think upon Virtualization options too.
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013 SP1 CU8 installation stuck

Good Morning,
I'm just installing CU8 for Exchange 2013 on a DAG Member (only mailbox role installed), and setup is stuck at 49% of "Mailbox Role: Client Access service" for more than 2 hours now.
The ExchangeSetup logfile says:
[04/15/2015 06:44:20.0582] [2] Active Directory session settings for 'New-PerfCounters' are: View Entire Forest: 'True', Configuration Domain Controller: 'srv-dc02.oostvogels.com', Preferred Global Catalog: 'dc02.contoso.com', Preferred Domain Controllers: '{ dc02.contoso.com }'
[04/15/2015 06:44:20.0582] [2] User specified parameters: -DefinitionFileName:'ServiceProxyPoolCounters.xml'
[04/15/2015 06:44:20.0582] [2] Beginning processing new-PerfCounters
[04/15/2015 06:44:20.0582] [2] Processing file: C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\ServiceProxyPoolCounters.xml
[04/15/2015 06:44:20.0582] [2] Performance counter name is Proxy Instance Count, type is NumberOfItems32.
[04/15/2015 06:44:20.0582] [2] Performance counter name is Current Outstanding Calls, type is NumberOfItems32.
[04/15/2015 06:44:20.0582] [2] Performance counter name is Total Number of Calls, type is NumberOfItems32.
[04/15/2015 06:44:20.0582] [2] Performance counter name is Calls/sec, type is RateOfCountsPerSecond32.
[04/15/2015 06:44:20.0582] [2] Performance counter name is Average Latency, type is AverageCount64.
[04/15/2015 06:44:20.0582] [2] Performance counter name is Base for Average Latency, type is AverageBase.
[04/15/2015 06:44:20.0582] [2] Performance counter category name is 'MSExchange ServiceProxyPool'.
[04/15/2015 06:44:20.0738] [2] Performance counter category name is 'MSExchange ServiceProxyPool'.
[04/15/2015 06:44:22.0255] [2] Ending processing new-PerfCounters
Does anyone have any suggestions or did you experience a similar issue?
I also can see some events like this:
Cmdlet failed. Cmdlet New-PerfCounters, parameters -DefinitionFileName "ADDriverCachePerformanceCounters.xml".
Thanks and best regards,
Sebastian

Hi,
According to your post, I understand that install Exchange 2013 SP1 CU8 in a DAG with MBX role failed with error “Cmdlet failed. Cmdlet New-PerfCounters, parameters -DefinitionFileName ‘ADDriverCachePerformanceCounters.xml’”.
If I misunderstand your concern, please do not hesitate to let me know.
I want to double confirm whether you deploy clean install or implement upgrade an existing Exchange Server 2013 installation to Cumulative Update 8.
To rebuild all Performance counters including extensible and third-party counters, type the following commands at an Administrative command prompt. Press ENTER after each command:
1. Rebuilding the counters:
    cd c:\windows\system32
    lodctr /R
2. Resyncing the counters with Windows Management Instrumentation (WMI):
    WINMGMT.EXE /RESYNCPERF
3. Stop and restart the Performance Logs and Alerts service.
4. Stop and restart the Windows Management Instrumentation service.
If the issue persists, please run to reload all the perf counters. For your reference:
http://blogs.technet.com/b/mikelag/archive/2010/09/10/how-to-unload-reload-performance-counters-on-exchange-2010.aspx
Thanks
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]
Allen Wang
TechNet Community Support

Exchange 2013 incomplete installation - click Next stuck at 0%

Similar Messages

Maybe you are looking for