We have Exchange 2013 CU2 running on Windows Server 2012.

While installing Exchange 2013 CU3 we got following error:

The following error was generated when "$error.Clear(); & $RoleBinPath\ServiceControl.ps1 EnableServices Critical" was run: "AuthorizationManager check failed"

Now we cannot see the Exchange Administration console. All the Exchange Services are disabled automatically.

I get following error while trying to start Microsoft Exchange Active Directory Topology Service.

Windows Could not start the Microsoft Exchange Active Directory Topology Service on Local Computer.
 Error 2: The System cannot find the file specified.

I checked in C:\Program Files\Microsoft\Exchange Server\V15\Bin\ and don't see Microsoft.Exchange.Directory.TopologyService.exe.

I copied the Microsoft.Exchange.Directory.TopologyService.exe from CU2-> Setup -> serverrole ->common and pasted to C:\Program Files\Microsoft\Exchange Server\V15\Bin\>

Then tried to start the Microsoft Exchange Active Directory Topology Service Error 1053: The Service did not respond to the start or control request in a timely fashion

I tried Setup /m:RecoverServer and that failed too.

Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
 Setup.exe /Prepare AD /IAcceptExchangeServerLicenseTerms
 Setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms

All these completed successfully.

Ran Setup/Mode:Upgrade/IAcceptExchangeServerLicenseTerms

Error:
 The following error was generated when "$error.Clear(); & $RoleBinPath\ServiceControl.ps1 EnableServices Critical" was run: "AuthorizationManager check failed"

I have uploaded the Exchange Setup logs:

https://onedrive.live.com/redir?resid=F3743C55DC76B1EE!1099&authkey=!AL40dKaAzl-_trc&ithint=folder%2c.log

Hello,

In order to troubleshoot the issue, please try the following stpes:

 ========================================================

1. Please try to use the GPMC or the Gpedit.msc to turn off the GPO or the local policy.

2. Please try to reinstall Exchange Server 2013.

3. Please set the execution policy for the LoalMachine scope to RemoteSigned.

If the issue persists, please disable IPv6 and check if there is any related error in application log.

If you have any feedback on our support, please click here

Disabled the Group Policy which was set to set the execution policy to Unrestricted.

Ran the setup again and this time got the new error:

C:\Software\CU3>setup /Mode:Upgrade /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
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
    Preparing Files                                           COMPLETED
    Copying Exchange Files                                    COMPLETED
    Language Files                                            COMPLETED
    Restoring Services                                        COMPLETED
    Language Configuration                                    COMPLETED
    Mailbox role: Transport service                           FAILED
 An unexpected error has occurred and a Watson dump is being generated: The foll
owing error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
            {
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath
 "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "In
stallConfig.ps1";
                $dataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Searc
h\Ceres\HostController\Data";

                # Remove previous SearchFoundation configuration
                &$command -action u -silent;
                try
                {
                    if ([System.IO.Directory]::Exists($dataFolderPath))
                    {
                        [System.IO.Directory]::Delete($dataFolderPath, $true);
                    }
                }
                catch
                {
                    $deleteErrorMsg = "Failure cleaning up SearchFoundation Data
 folder. - " + $dataFolderPath + " - " + $_.Exception.Message;
                    Write-ExchangeSetupLog -Error $deleteErrorMsg;
                }

                # Re-add the SearchFoundation configuration
                try
                {
                    # the BasePort value MUST be kept in sync with dev\Search\sr
c\OperatorSchema\SearchConfig.cs
                    &$command -action i -baseport 3800 -dataFolder $dataFolderPa
th -silent;
                }
                catch
                {
                    $errorMsg = "Failure configuring SearchFoundation through in
stallconfig.ps1 - " + $_.Exception.Message;
                    Write-ExchangeSetupLog -Error $errorMsg;

                    # Clean up the failed configuration attempt.
                    &$command -action u -silent;
                    try
                    {
                        if ([System.IO.Directory]::Exists($dataFolderPath))
                        {
                            [System.IO.Directory]::Delete($dataFolderPath, $true
);
                        }
                    }
                    catch
                    {
                        $deleteErrorMsg = "Failure cleaning up SearchFoundation
Data folder. - " + $dataFolderPath + " - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $deleteErrorMsg;
                    }
                }
            }
        " was run: "Error occurred while uninstalling Search Foundation for Exch
ange.System.Exception: Cannot determine the product name registry subkey, neithe
r the 'RegistryProductName' application setting nor the 'CERES_REGISTRY_PRODUCT_
NAME' environment variable was set
   at Microsoft.Ceres.Common.Utils.Registry.RegistryUtils.get_ProductKeyName()
   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.DeleteDataDirectory()

   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.Uninstall(String inst
allDirectory, String logFile)
   at CallSite.Target(Closure , CallSite , Type , Object , Object )".

     The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
            {
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath
 "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "In
stallConfig.ps1";
                $dataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Searc
h\Ceres\HostController\Data";

                # Remove previous SearchFoundation configuration
                &$command -action u -silent;
                try
                {
                    if ([System.IO.Directory]::Exists($dataFolderPath))
                    {
                        [System.IO.Directory]::Delete($dataFolderPath, $true);
                    }
                }
                catch
                {
                    $deleteErrorMsg = "Failure cleaning up SearchFoundation Data
 folder. - " + $dataFolderPath + " - " + $_.Exception.Message;
                    Write-ExchangeSetupLog -Error $deleteErrorMsg;
                }

                # Re-add the SearchFoundation configuration
                try
                {
                    # the BasePort value MUST be kept in sync with dev\Search\sr
c\OperatorSchema\SearchConfig.cs
                    &$command -action i -baseport 3800 -dataFolder $dataFolderPa
th -silent;
                }
                catch
                {
                    $errorMsg = "Failure configuring SearchFoundation through in
stallconfig.ps1 - " + $_.Exception.Message;
                    Write-ExchangeSetupLog -Error $errorMsg;

                    # Clean up the failed configuration attempt.
                    &$command -action u -silent;
                    try
                    {
                        if ([System.IO.Directory]::Exists($dataFolderPath))
                        {
                            [System.IO.Directory]::Delete($dataFolderPath, $true
);
                        }
                    }
                    catch
                    {
                        $deleteErrorMsg = "Failure cleaning up SearchFoundation
Data folder. - " + $dataFolderPath + " - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $deleteErrorMsg;
                    }
                }
            }
        " was run: "Error occurred while uninstalling Search Foundation for Exch
ange.System.Exception: Cannot determine the product name registry subkey, neithe
r the 'RegistryProductName' application setting nor the 'CERES_REGISTRY_PRODUCT_
NAME' environment variable was set
   at Microsoft.Ceres.Common.Utils.Registry.RegistryUtils.get_ProductKeyName()
   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.DeleteDataDirectory()

   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.Uninstall(String inst
allDirectory, String logFile)
   at CallSite.Target(Closure , CallSite , Type , Object , Object )".

The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

C:\Software\CU3>

The new Exchange Setup log is uploaded here:

https://onedrive.live.com/redir?resid=F3743C55DC76B1EE!1099&authkey=!AL40dKaAzl-_trc&ithint=folder%2c.log

Solution : Disabled IPV6 via regedit http://support.microsoft.com/kb/929852 and the process completed successfully.

Many thanks!!!!

1.Open registry.exe

2.Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters \

3.Double-click DisabledComponents to change the DisabledComponents entry

Note : If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps:

1. In the Edit menu, point to New, and then click DWORD (32-bit) Value.
2. Type DisabledComponents, and then press ENTER.
3. Double-click DisabledComponents.

4.Type any one of the following values in the Value data field to configure the IPv6 protocol to the desired state, and then click OK:

Type 0xffffffff to disable all IPv6 components except the IPv6 loopback interface. This value also configures

5.To use the DisabledComponents registry value to check whether IPv6 was disabled, run the following command at a Windows command prompt:

reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents

6.Restart computer and,try again to upgrade CU3.