Upgrade Exchange server 2013 to CU7 error

Dear Microsoft Team
I have Exchange server 2013 SP1 and upgrade it to CU5 it is working normal
But wen I try to Upgrade it to CU7 I got this error massage
Error:
The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;
          while($currTime -le $timeout)
            $setSharedCDCErrors = @();
            try
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
              if($successfullySetConfigDC)
                break;
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            catch
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          if( -not $successfullySetConfigDC)
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, 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)".
Best Regards
Rawa Zangana

Hi Rawa Zangana,
According to the error message, it seems that the Global Catalog not reachable from DC.
Please perform following steps.
1. Port 3268 listened on DC.
2. Enable Global Catalog role on all DCs.
3. Restart Exchange Server 2013 CU5.
4. Check whether Event 2080 found on all DCs, Event 2080 means that AD connectivity works fine.
5. Repeat CU7 installation.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Similar Messages

  • Exchange Server 2013 Toolbox MMC Error ConsoleInitialize.ps1 not recognised

    Hello, after installing and configuring Exchange 2013 during a migration from 2010 (with both versions still running), I am now receiving a ConsoleInitialize.ps1 System.Management.Automation.RemoteException exception when trying to run the Management Toolbox
    (I am really after the Queue Viewer).
    This is the same when trying to connect locally on the server and remotely on a client computer with Management Tools installed - I can use EMC without any errors locally or remotely.
    I have tried various fixes found around the net, including:
    Changing the Identity of the Classic and DefaultAppPools in IIS and resetting - from LocalSystem to ApplicationPoolIdentity
    Adding the roles to Exchange Organisation Management in AD
    Disabling SSL on the Powershell virtual Directory and setting auth to anonymous
    I have not tried recreating the Powershell virtual directory as mentioned on a few sites, as I have not been able to test that in the lab, and I am not sure how it affects the powershell session that I am doing it from.
    The only thing that I can think that could be an issue is that Ex2010 is still up and running, could it be that Management Tools is looking at the old server, instead of the new?
    Can anyone point me in the right direction with this one?
    I can post more info if required.
    Thank you.
    Xpost here: http://serverfault.com/questions/666054/exchange-server-2013-toolbox-mmc-error-consoleinitialize-ps1-not-recognised

    Hi,
    If the EMS and EMC work properly, I think the powershell cannot be the problem. Is it possible to build up a new Exchange 2013 Server in test environment and make a replacement of
    the ConsoleInitialize.ps1 file?
    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

  • How to upgrade Exchange Server 2013 CU5 on my site?

    My site have four Exchange servers . The four Exchange Servers are installed mailbox and cas roles. The
    Dag achieved by the four servers. Please help me to upgrade exchange server 2013 cu5 on the four servers. how to do? Thanks.
    北京老马

    Hi Martin
    Find the below information.
    Upgrade Sequence for each Role:
    ==========================
    You should upgrade your Exchange 2013 server roles in the following order:
    Client Access
    Mailbox
    Edge 
    For DAG members
    Upgrade only passive servers in the first phase.
    Before you apply the service pack to a DAG member, move all active mailbox database copies off the server to be upgraded and configure the server to be blocked from activation.
    Place server in DAG maintenance mode before applying the service pack to any DAG member,
    Stop any scheduled tasks or other processes running on the DAG member or within that DAG that could adversely affect the DAG member being upgraded or the upgrade process
    Good Luck !!
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • What is the order for upgrading exchange server 2013 SP1 servers to CU7?

    Hi All 
    I am planning to upgrade my exchange server 2013 SP1CU4 to CU7 . As per my understanding , we always proceed with the CAS servers and then the Mailbox Servers during up-gradation.
    But I am confused now , since I have seen articles stating , that the Mailbox servers has to be upgraded first and then the CAS servers in exchange 2013. 
    What will be the correct order . My environment consists of 2 Mailbox servers in DAG and 2 CAS servers (Exchange server 2013 SP1)
    Thanks in Advance .
    Joyso Senior Messaging Admin

    Hi Joyso,
    The Microsoft recommendation regarding the order in which the Exchange 2013 server roles should be installed or Upgraded is Mailbox and then CAS.
    It makes sense as the CAS Role is a stateless server and all major components are held by the Mailbox Role.
    Until a 2013 mailbox server comes online, the CAS server is pretty much useless. Hence, the recommended installation order in 2013 is the reverse of 2010 – Mailbox role first & then CAS
    Note: If your DAG have more nodes, you need first upgrade all non-PAM nodes and then upgrade PAM node.
    Some References:
    The recommendation from the Product Group is to install Exchange 2013 Preview Mailbox Role first, and then the
    CAS role.
    If you're separating your server roles, we recommend installing the Mailbox server role first.
    Upgrade your Exchange 2013 server roles in the required order. First, upgrade Mailbox servers
    and then upgrade Client Access servers. -Upgrade DAG Mailbox servers
    Exchange 2013 Server Roles Installation Order – Mailbox First:
    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.

  • Upgrade Exchange Server 2013 SP1

    Hello,
    I have two Exchange 2013 SP1 servers with DAG configured. I want to upgrade them with CU8. Kindly advise how to do or is there any step by step document available for upgrading the DAG member server.
    Thanks in advance.

    yes you need to upgrade one at a time and putting them in maintenance mode
    this article has step by step info
    http://vanhybrid.com/2013/11/28/script-putting-exchange-server-2013-into-maintenance-mode/
    Where Technology Meets Talent

  • Mail flow completely broken after upgrading Exchange Server 2013 CU3 (Build 775.38) to Exchange Server 2013 SP1 (Build 847.32)

    internal mail flow completely broken.
    external mail flow completely broken.
    i upgraded exchange server as follows:
    1. setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
    2. setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
    3. upgraded the exchange server with GUI installer
    also considered this: http://support.microsoft.com/kb/2938053/en-us
    receive connectors :
    Transport Service couldn't start, then i disabled hub transports, and it starts, but no mail flow on port 25. according to this:
    http://social.technet.microsoft.com/wiki/contents/articles/24056.what-the-crash.aspx
    i didn't have any success to fix mail flow, any solution?

    Hi Alireza
    The above tech-net http://social.technet.microsoft.com/wiki/contents/articles/24056.what-the-crash.aspx
    will be applicable only if we get these events in the app log 1019,1018,1036,4999
    You can check the transport service is running in which service account - Local or network 
    It should be running in network account by default.
    You can run get-transportagent and check if there are any transport agents installed 
    If you find them then disable all the transport agents that you have installed on the Exchange servers by running disable-transportagents
    Disable the antivirus if you have any installed.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • Exchange Server 2013 CU3 Installation Error - Fresh Installation

    Hi All,
    I am trying to install Exchange 2013 CU3 on Windows Server 2012 Datacenter Edition. This is New Server Forest build.
    Forest Function Level and Domain functional Level is Windows Server 2008 R2
    As part of this Fresh installation, I have tried to install CAS Server Role first on the server.
    I have full admin (Schema,Entp, Domain) Previliges and installed MS recomended pre-requesities successfully.
    Set the Powershell Execution policy as unrestricted.
    But, When i run setup file using GUI option. I am getting the below error. I would like to know whether this is ignorable for installation or how to fix the issue.
    Error:
    Warning:
    Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type
    initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    Warning:
    Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type
    initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    Warning:
    Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for
    'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution
    result should not be affected.
    Note: Server OS hardening policy has been applied in this server as per company security policy and Symantec A/V also installed in this server.
    Regards
    Manoj

    Hi,
    Same Error for Mailbox Server also.
    Stopped the Symantec AV Service and Tried. But result is same.
    02/18/2014 06:39:06.0018] [0] Active Directory session settings for 'Get-OrganizationRelationship' are: View Entire Forest: 'True', Configuration Domain Controller: 'TESTPRADC01.Domain.LOCAL', Preferred Global Catalog: 'TESTPRADC01.Domain.LOCAL', Preferred
    Domain Controllers: '{ TESTPRADC01.Domain.LOCAL }'
    [02/18/2014 06:39:06.0050] [0] User specified parameters:
    [02/18/2014 06:39:06.0050] [0] Beginning processing Get-OrganizationRelationship
    [02/18/2014 06:39:07.0157] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Error" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution
    result should not be affected.
    [02/18/2014 06:39:07.0391] [0] [ERROR] Couldn't find the Enterprise Organization container.
    [02/18/2014 06:39:07.0469] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:07.0610] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:07.0688] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:07.0688] [0] Ending processing Get-OrganizationRelationship
    [02/18/2014 06:39:07.0766] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task
    execution result should not be affected.
    [02/18/2014 06:39:08.0015] [0] Active Directory session settings for 'Get-AcceptedDomain' are: View Entire Forest: 'True', Configuration Domain Controller: 'TESTPRADC01.Domain.LOCAL', Preferred Global Catalog: 'TESTPRADC01.Domain.LOCAL', Preferred Domain Controllers:
    '{ TESTPRADC01.Domain.LOCAL }'
    [02/18/2014 06:39:08.0015] [0] User specified parameters:
    [02/18/2014 06:39:08.0015] [0] Beginning processing Get-AcceptedDomain
    [02/18/2014 06:39:08.0078] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Error" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution
    result should not be affected.
    [02/18/2014 06:39:08.0078] [0] [ERROR] Couldn't find the Enterprise Organization container.
    [02/18/2014 06:39:08.0140] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:08.0202] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:08.0265] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:08.0265] [0] Ending processing Get-AcceptedDomain
    [02/18/2014 06:39:08.0327] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task
    execution result should not be affected.
    [02/18/2014 06:39:08.0327] [0] While running the On-Promises test, either Get-AcceptedDomains or Get-OrganizationRelationship return a null value.
    [02/18/2014 06:39:08.0717] [0] Finished loading screen WelcomePage.
    [02/18/2014 06:45:23.0242] [0] Finished loading screen EULAPage.
    [02/18/2014 06:45:26.0908] [0] Finished loading screen RecommendedSettingsPage.
    [02/18/2014 06:45:30.0012] [0] Setup is determining what organization-level operations to perform.

  • Exchange server 2013 setup encounter error

    anyone pls help me, i'm ready setup few time still facing same error.
    Error:
    The following error was generated when "$error.Clear();
    if ($RoleCustomerFeedbackEnabled -ne $null)
         $organizationConfig = get-OrganizationConfig;
    if ($organizationConfig.CustomerFeedbackEnabled -ne $False)
    Set-ExchangeServer -Identity $RoleFqdnOrName -CustomerFeedbackEnabled $RoleCustomerFeedbackEnabled;
    " was run: "Property CustomerFeedbackEnabled can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).".

    Hi,
    First, please make sure you have installed all the required prerequisites. For Exchange 2013 prerequisites, please refer to this
    article.
    Then please verify if there is a legacy server via ADSIEDIT. If there is a legacy object, please delete this legacy object. In registry editor, remove the watermark key and action key from the following path and then reinitiate the setup to check the result.
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\HubTranportRole
    If the issue persists, to narrow down the issue, I recommend you check the setup log for related error message.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange server 2013 showing some error on event Log ( "DCOM" and "MSExchangeMapiMailboxAppPool" )

    Error : DCOM was unable to communicate with the computer ADCB.ABCD.net using any of the configured protocols; requested by PID     2bec (c:\windows\system32\inetsrv\w3wp.exe).
    Error: A process serving application pool 'MSExchangeMapiMailboxAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '2412'. The data field contains the error number.
    Please suggest

    Hi Parvez,
    According to the error message, I understand that the Event error 10009 is received on DC. Please correct me if there is any misunderstand.
    To solve this issue, please follow the steps below:
    a. Please ensure that the remote computer is online.
    b. This problem maybe the result of a firewall blocking the connection.
    c. Other reasons for the problem might be found in the Extended RPC error information that is available in Event Viewer.
    More details in the following article:
    Event ID 10009 — COM Remote Service Availability
    http://technet.microsoft.com/en-us/library/cc774368(WS.10).aspx
    If the Remote server contains some 32 bit Applications, please make sure that each Application Pool in IIS, under "Advanced Settings" has "Enable 32 bit Application" set to "True".
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange Server 2013 CU7 Upgrade Failed

    I am trying to upgrade Exchange Server 2013 SP1 to CU7 but after complete 46% of Mailbox Role Transport Service the Upgrade Failed and automatically rebooted the server. After restart its showing memory dump. How can we solved it.

    Hi livesayed,
    According to your description, we cannot get the key of this question.
    Would you please help to collect related event log or setup log? It’s more helpful for further troubleshooting.
    Besides, I find an similar thread about Exchange 2013 CU2 upgrade to CU3 Failed at Front End Transport Service, for your reference:
    https://social.technet.microsoft.com/Forums/office/en-US/32e06b5b-76bb-45d0-bf99-0b83c3182199/exchange-2013-cu2-upgrade-to-cu3-failed-at-front-end-transport-service?forum=exchangesvrdeploy
    Best Regards,
    Allen Wang

  • Exchange Server 2013 CU3 Update

    Hello All,
    I need to upgrade Exchange server 2013 CU1 to CU3. I need the details procedure. Please suggest regarding this issue.
    Thanks

    Are you aware that
    SP1 (CU4) is available?
    Step by Step Screencasts and Video Tutorials

  • Error when try to install exchange Server 2013 in windows server 2008 R2 Sp1

    Hi
    I'm getting these errors while trying to install Microsoft Exchange Server 2013 on my Windows Server 2008 R2 SP1 the user i'm using is the Administrator and it is already a member of "Enterprise
    Admins" and "Schema Admins"
    in my organization there is 6 Exchange server 2013 in 3 site windows server 2012 in this case
    I have to install exchange 2013 in windows Server 2008 r2 sp1
    the functional level  2008 R2 I getting these errors please help.
    Errors:
    This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx
    Error:
    A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.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:
    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 the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.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: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.  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:
    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

    I think it's from subnet in site and services
    have 3 site A,B,C and new site is  "D"I have problem in "D" site
    A subnet is 10.33.50.0/24  AD 2012 ,exchange 2013
    B subnet is 10.35.50.0/24 AD 2012 ,exchange 2013
    C subnet is 10.36.50.0/24 AD 2012 ,exchange 2013
    D subnet is 10.100.100.0/25 AD 2008 ,exchange 2013 error when install it
    find event error
    The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair
    the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    test-SetupPrerequisites
    {Roles={LanguagePacks, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport, Cafe}, LanguagesAvailableToInstall=True, DomainController=, CustomerFeedbackEnabled=True, ExchangeVersion=15.0.847.32, LanguagePackDir=D:\Exchange
    Server Software, SufficientLanguagePackDiskSpace=True, ADInitError=Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites
    or by rep, ScanType=PrecheckInstall, LanguagePackVersioning=True, HostingDeploymentEnabled=False, TargetDir=C:\Program Files\Microsoft\Exchange Server\V15, SetupRoles={LanguagePacks, AdminTools, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport,
    Cafe}}

  • Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

    What am I trying to do?
    I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
    error logs at the bottom of the page but the basics are in order it will throw which loop around are:
    [01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
    What am I running?
    2 X DC on domain and forest functional level 2008R2 both writable
    1 X fresh install of Windows 2012 R2 which is domain joined
    What have I tried?
    Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
    Rebooted every server
    Run setup as Administrator
    My account is part of the domain Enterprise Admin group
    Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
    Computer Configuration Windows Settings
    Security Settings + Local Policies
    User Rights Assignment Mange auditing and security log
    Turned off firewall on DC and Exchange Server even stopped the service
    Turned off all AV on the DC and Exchange Server
    Checked I could telnet to global catalog servers on port 3268 which I can
    Checked the global catalog records existed in DNS which they all do
    Done the obvious ping tests all round which confirms connectivity
    Schema has been prepared using appropriate commands before running the setup exe
    setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
    Making sure the following path has full permissions:
    EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    Restarted Microsoft Exchange Active Directory Topology service
    DcDiag all looks good
    What have I noticed that is suspicious?
    Microsoft Exchange Transport service will not start even though both of its dependences services have started:
    Microsoft Filtering Management Service
    Microsoft Exchange Active Directory Topology Service
    It will eventually error with
    “Windows could not start the Microsoft Exchange Transport Service on local computer
    Error 1053: This Service did not respond to the start of control request in a timely fashion”
    This error is from the GUI wizard itself:
    Error:
    The following error was generated when "$error.Clear();
    $maxWait = New-TimeSpan -Minutes 8
    $timeout = Get-Date;
    $timeout = $timeout.Add($maxWait);
    $currTime = Get-Date;
    $successfullySetConfigDC = $false;
    while($currTime -le $timeout)
    $setSharedCDCErrors = @();
    try
    Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
    $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
    if($successfullySetConfigDC)
    break;
    Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
    catch
    Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
    Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
    Start-Sleep -Seconds 30;
    $currTime = Get-Date;
    if( -not $successfullySetConfigDC)
    Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
    " was run: "System.Exception: Unable to set shared config DC.
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Exchange logs which have been written:
    **The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
    [01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
    '{ mydomain.com}'
    [01/20/2015 17:13:20.0084] [2] User specified parameters: 
    -DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
    [01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    [01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
    No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
    [01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
    [01/20/2015 17:13:50.0288] [1] 0.  ErrorRecord: Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [1] 0.  ErrorRecord: System.Exception: Unable to set shared config DC.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    [01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
    $maxWait = New-TimeSpan -Minutes 8
    $timeout = Get-Date;
    $timeout = $timeout.Add($maxWait);
    $currTime = Get-Date;
    $successfullySetConfigDC = $false;
    while($currTime -le $timeout)
    $setSharedCDCErrors = @();
    try
    Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
    $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
    if($successfullySetConfigDC)
    break;
    Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
    catch
    Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
    Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
    Start-Sleep -Seconds 30;
    $currTime = Get-Date;
    if( -not $successfullySetConfigDC)
    Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
            " was run: "System.Exception: Unable to set shared config DC.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    [01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
    [01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
    [01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
    Windows Event Viewer:
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
    in either the local site 'Default-First-Site' or the following sites:

    Hi apl228,
    1. Please make sure the IPv6 is enabled.
    2. Please make sure the account that install Exchange server has Administrator permission.
    3. Please make sure DNS has been configured correctly.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Connecting to Exchange Server 2013 using IMAP command gives authenication error

    Hello All,
    My application (it is a C# code) connects to Microsoft exchange server 2013 using POP3 and IMAP, processes the emails, marks as read and move to particular folder if it is processed successfully else to an different folder.  In this sometimes,
    I am getting authentication failed error from IMAP however same mail is processed when it is executed next time. Few times it is processed with out error. I am not sure what is causing this issue.We are connecting to IMAP using tcpIMAP command.
    This is the same application which we used with exchange server 2010 now we are upgrading to exchange server 2013. I have verified that the setting of exchange 2010 and 2013 are the same.
    To verify the IMAP command I created a sample application using C# which will try to connect to IMAP service and log in to exchange server 2013; it fails to authenticate the user after connecting for few times and then it starts to authenticate
    successfully then again fails for few times and then authenticates. I am not sure why this is happening. 
    Please suggest how can I resolve this.
    Thank you, Santha

    Since I've upgraded to Snow Leopard I've also moved from Entourage 2008 to Mail, iCal & Addressbook with the new Exchange support.
    My company exchange server is Exchange 2007.
    Mail works fine except the occasional Mail crash.
    iCal worked fine the first two days and then it came with an error the it cannot connect to the Exchange server and asks me to type my email address again. Doesn't work so I need to put my exchange calendar in iCal in offline. But now there is no syncing with the Echange server.
    This only occurs when I add a meeting request in iCal.
    My Exchange administrator has reset my mailbox on the Exchange server.
    This helped for about 4 hours. Now it's the same problem.
    I have a feeling the when you setup your exchange account in Mail it uses different settings for Mail and iCal with the autoconfig.
    Anybody has a solution? My Exchange admin cannot find any problems on his side. Do I need to make changes on my iCal client or do we need to wait for OS 10.6.1 ?

  • Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

    Hi Team,
    Need urgent help in resolution of following error:
    Environment Details: VMware ESXi 5.5 (vMotion)
    Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
    Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
    OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
    Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
    Prerequisites: Installed
    Error: Installation gives Error at Step 10 during installation of Mailbox Service
    Error Details Below:
    Error:
    The following error was generated when "$error.Clear();
    if ([Environment]::OSVersion.Version.Major -ge 6)
    $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
    $reg= join-path (join-path $env:SystemRoot system32) reg.exe;
    $servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
    if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
    if ((get-service wsbexchange).Status -eq "Running")
    Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
    Exchange /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
    Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
    " was run: "Process execution failed with exit code 1.".

    Resolved ! :)
    Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
    As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
    Thanks to all.

Maybe you are looking for

  • How can I display more than one value in Calendar ? (2)

    Hi, I came across the "Calendar - Activity Monitor by month" in the HTMLDB admin section. This is exactly the view I like to develop asked earlier (the proposal was to work with concatination of fields). Can you provide for the source code used for t

  • Where is the "do not restore" option?

    Where is the "do not restore" option? I read a review somewhere that said it actually works in ML - but where is it? I can't find it in System Prefs.

  • Outputted date with unusual format mask

    I am getting a flat file outputed from Fusion Financials SAAS, and one of the columns has this: 2013-11-14T15:10:36.000-06:00 Clearly its a date. I am guessing its a datetime TIMESTAMP WITH TIME ZONE datatype. But, the Format Model is unfamiliar to m

  • Output control

    Hi ,   i developed the SAPscript for PO and created the output type by assigning the access sequence. Now the problem when creating or changed the PO  if the net amount is more than 5000 then it has to print and if it is less than 5000 then sapscript

  • New lightroom mobile synch question between DSLR and iPad

    If you are in the field and you synch wirelessly to the iPad or use import feature from cards, will lightroom mobile synch seamlessly to lightroom CC. For example, starting workflow from camera to iPad to computer?