.\SetupLogReviewer.ps1 -SetupLog C:\ExchangeSetupLogs\ExchangeSetup.log
Alternatively you can review the log located at C:\ExchangeSetupLogs\ExchangeSetup.log for the following error:
"Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter on a computer in the domain <domain_name> and site <Default_First_Site_Name>, and wait for replication to complete."
If you find this error, run the following command from a machine that is in the same domain as the schema master.
.\setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
Note: The user who runs the command must be a member of the Enterprise Admin, Domain Admin, and Schema Admin groups.
To find the Domain Controller (DC) which holds the schema master, run the following command from administrative command prompt on the DC:
netdom query fsmo
Back to top
Error during update rollup installation
Issue:
When you install the update rollup on a computer that isn't connected to the internet, you may experience a long installation delay. Additionally, you may receive the following error message:
Creating Native images for .Net assemblies.
Cause:
This issue is caused by the network requests to connect to the following URL:
http://crl.microsoft.com/pki/crl/products/CodeSigPCA.crl
The network requests are attempts to access the Certificate Revocation List for each assembly for which Native image generation (Ngen) compiles to native code. Because the server that's running Exchange Server isn't connected to the internet, each request must wait to time out before the process can continue.
Resolution:
Do the following:
In Internet Explorer, select Tools > Internet Options.
Select the Advanced tab.
In the Security section, clear the Check for publisher's certificate revocation check box, and then select OK.
Clear this security option only if the computer is in a tightly-controlled environment.
After the Setup process completes, select the Check for publisher's certificate revocation check box again.
Back to top
Setup fails with "Cannot start the service" error
Issue:
The CU setup might fail with the following error message:
Cannot start the service Microsoft Exchange Service Host
You might find that the Microsoft Exchange Service Host and/or all other Exchange services are stopped and in Disabled mode.
Resolution:
Do the following:
Rename the C:\ExchangeSetupLogs folder (for example, ExchangeSetupLogs-OLD).
Change the startup type for all Exchange services in the services.msc console to Automatic.
Assuming that the Exchange CU media is on D: drive, open a command prompt as administrator and resume setup by using the following command:
D:\setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms
Back to top
SU installation fails because of existing IU
Issue:
During the SU installation, you might see the following error message:
Installation cannot continue. The Setup Wizard has determined that this Interim Update is incompatible with the current Microsoft Exchange Server 2013 Cumulative Update 23 configuration.
Resolution 1:
Uninstall the previously installed Interim Update (IU) before applying this SU because the updates are cumulative. You can find the previous IUs in Add/Remove Programs.
Resolution 2:
This error message may also display on a server that has no IUs installed but is not connected to the internet. So it can't check the Certificate Revocation List. In this situation, do the following:
In Internet Explorer, select Tools > Internet Options.
Select the Advanced tab.
In the Security section, clear the Check for publisher's certificate revocation check box, and then select OK.
Clear this security option only if the computer is in a tightly-controlled environment.
After the Setup process completes, select the Check for publisher's certificate revocation check box again.
Back to top
Setup installs older CU or fails to install language pack
Issue:
You're upgrading to the latest CU but Setup either displays that it is installing an existing CU on the server OR fails with the following error message:
Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\<package name>. This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.
Cause:
These issues occur if you start the installation from Windows PowerShell and use the Setup.EXE command.
Resolution:
If the Exchange CU media is on D: drive, run an upgrade using PowerShell by using either of the following commands:
".\setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms" (PowerShell) or "D:\setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms" (PowerShell and command prompt)
Back to top
Restart from previous installation is pending
Issue:
You keep getting the following error message even after restarting the server several times:
Microsoft Exchange Server setup cannot continue because a restart from a previous installation or update is pending.
Resolution:
Follow the information provided in A Restart from a Previous Installation is Pending to fix the issue.
If you still see the error message, do the following:
Run the HealthChecker script.
Run the SetupAssist.ps1 script.
Back to top
Mail flow has stopped
Issue:
Mail flow stops after you install a CU or an SU.
Resolution:
To get mail flow working again, make sure that the following requirements are met:
All Exchange services are enabled and running.
The server is not in Maintenance mode
There is enough free space available in the Exchange message queue database.
Back to top
Exchange Setup or PrepareAD error
Issue:
When you run either Exchange setup or the PrepareAD command, the process fails with the following error message:
The well-known object entry B:<guid>:CN=Recipient Management\0ADEL:<guid>,CN=Deleted Objects,DC=contoso,DC=com on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com points to an invalid DN or a deleted object. Remove the entry, and then rerun the task. at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
Cause:
This issue occurs because "otherWellKnownObjects", the object referenced in the error, is no longer in Active Directory. So the link to the object needs to be removed.
Resolution:
Download and run the SetupAssist.ps1 script.
.\SetupAssist.ps1 -OtherWellKnownObjects
The script will dump the otherWellKnownObjects attribute into a file named ExchangeContainerOriginal.txt. Then it will check the file for deleted objects. If any are found, the script will generate a new file named ExchangeContainerImport.txt and use it to remove the bad values.
If the script asks you to verify the results, do the following:
Review the ExchangeContainerImport.txt file for the changes made by the script.
Import the ExchangeContainerImport.txt file into Active Directory by following the instructions provided by the script.
Rerun the PrepareAD command.
Now you should be able to continue with the setup.
Back to top
Exchange setup fails with error code 1603
Issue:
You see the following error message during Exchange installation:
Installing product F:\exchangeserver.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'The installer has insufficient privileges to access this directory: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa\auth\15.1.2106'.
Resolution:
Make sure that the setup is run by using a local administrator account.
Check whether the following permissions are assigned to the folder specified in the error:
Read permission to Authenticated users
Full Control permission to System
Full Control to <local_machine>\administrators>
Make sure that inheritance is enabled on the folder. If it isn't, then enable inheritance.
After updating folder permissions, resume setup.
If the error message still occurs, follow the steps provided in this article.
Back to top
Update .NET when migrating from an unsupported CU
If you're upgrading Exchange Server from an unsupported CU to the current CU and no intermediate CUs are available, you should first upgrade to the latest version of .NET that's supported by your version of Exchange Server and then immediately upgrade to the current CU. This method doesn't replace the need to keep your Exchange servers up to date and on the latest supported CU. Microsoft makes no claim that an upgrade failure will not occur by using this method.
Important
Versions of the .NET Framework that aren't listed in the tables in the Exchange Server supportability matrix are not supported on any version of Exchange. This includes minor and patch-level releases of the .NET Framework.
Follow these steps to install the latest version of the .NET Framework:
Put the server into Maintenance Mode.
Run the following command:
set-servercomponentstate \<server_name\> -Component serverwideoffline -State inactive -Requester Maintenance
Stop all Exchange Services by using either the Services MMC or PowerShell. If you want to use PowerShell, run the following command twice to stop all Exchange services:
Get-service \*exch\* \| stop-service
Note: It is not recommended to use the -Force command to stop all the services.
Download and install the correct version of the .NET Framework according to the Exchange Server supportability matrix.
After the installation is complete, reboot the server.
Update to the newest CU available for Exchange 2013, 2016, or 2019.
Reboot the server after the CU is installed.
Ensure all Exchange services are in their normal start mode and have started. You can use PowerShell to run the following command to start them:
Get-service \*exch\*
Take the server out of Maintenance Mode. Run the following command:
set-servercomponentstate \<server_name\> -Component serverwideoffline -State active - Requester Maintenance
Back to top
Handle customized OWA or .config files
Important
Before you apply a CU, make a backup copy of your customized files.
When you apply a CU (for Exchange Server 2013, 2016 or 2019) or Rollup package (for Exchange Server 2010), the process updates OWA files and .config files if necessary. As a result, any customization that you may have made to Exchange or Internet Information Server (IIS) settings in Exchange XML application configuration files on the Exchange server will be overwritten when you install an Exchange CU. Examples of such application configuration files include web.config files, EdgeTransport.exe.config files, and any customized logon.aspx Outlook on the web files. Make sure to save this information so you can easily reapply the settings after the CU is installed.
Back to top
Install the update for CAS-CAS Proxying deployment
If your scenario meets both the following conditions, apply the update rollup on the internet-facing CAS before you apply the update rollup on the non–internet-facing CAS:
You're a CAS Proxy Deployment Guidance customer.
You have deployed CAS-CAS proxying.
For other Exchange Server 2010 configurations, you don't have to apply the update rollup on your servers in a specific order.
Back to top
Install the update on DBCS version of Windows Server 2012
To install or uninstall Update Rollup 32 for Exchange Server 2010 SP3 on a Double Byte Character Set (DBCS) version of Windows Server 2012, the language preference for non-Unicode programs should not be set to the default language. If it is, then you must change this setting before beginning the installation.
In Control Panel, select Clock, Region, and Language > Region > Administrative.
In the Language for non-Unicode programs area, select Change system locale.
In the Current system locale list, select English (United States), and then select OK.
Now you can install or uninstall Update Rollup 32 as needed. After the process completes, revert the language setting as appropriate.
Back to top
