Exchange Server 2013 - SChannel errors KB2992611

Hi,
At a customer we have Exchange 2013 setup on a Windows Server 2012 R2 virtual machine.
Last weekend we installed the latest patches and since then we are experiencing some errors regarding TLS. The System Eventlog is full of events from SChannel with ID 36887 saying: "A fatal alert received from the remote endpoint. The TLS Protocol defined
fatal alert code is 40." 
When I search the internet I immediately found this topic: http://support2.microsoft.com/kb/2992611/en-us stating it had something to do with KB2992611 being installed.
This stated that I should download the update KB3018238. But I can't seem to download this KB for Windows Server 2012 R2. I searched the internet, the Microsoft Update Catalog, etc.
Any ideas on where I could find this KB for 2012 R2?
Many thanks in advance!
Best regards,
Bert

Hi,
Depending on my research, KB3018238 is for Windows Server 2008 R2 and Windows Server 2012. KB2992611 only add the new cipher suites to Windows Server 2008 R2 and Windows Server 2012. KB3018238 is used to remove the new cipher.
For your question, I want to double confirm whether client failed connect to Exchange server with error. Please post relevant error, it’s more helpful for further troubleshooting.
Please check if the cipher suits used by the server and client are matched. Besides, There have a few Schannel updates in the last couple months, for example KB3011780. We can install it in Windows Server 2012 R2 for test.
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

Similar Messages

  • Exchange Server 2013 Installation error

    Hi Support,
    I have try to install exchange server 2013 on server 2012. after configure active directory when try to install exchange server command Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.
    C:\Windows\system32>CD\
    C:\>E:
    E:\>cd pradeep\Ex Setup 2013
    E:\pradeep\EX Setup 2013>Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseT
    erms
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for
    installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                     FAILED
         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
    The Exchange Server setup operation didn't complete. More details can be found
    in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    E:\pradeep\EX Setup 2013>

    Hi ,
    Please have a look in to the error message 
      "A reboot from a previous installation is pending. Please restart the system
     and then rerun Setup."
    Reboot the server and try again .
    Please reply me if you have any queries .
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Exchange Server 2013 installation error at Step 10/15

    I try to install Exchange Server 2013 on a fresh install of Windows Server 2012.
    Windows Server 2012, have already install on it:
    AD CD
    DNS
    IIS
    Exchange 2013 Prerequisites for Win.Server 2012 like described here
    http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
    And the (winner) error message is:
    Exchange Server component Mailbox role: Client Access service failed.
    Error: Error:
    The following error was generated when "$error.Clear();
    Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "Could not grant Network Service access to the certificate with thumbprint ABC7C6378BF63CED166794CFBF410C73B29EDD3A because a cryptographic exception was thrown.".
    I search online for a solution and I found many others with same problem but any solution yet. :(
    If anyone can help me I am able to dedicate him my next ode.
    Thank you,
    Adrian

    I am experiencing the same problem except that mine is definitely NOT a domain controller.  The error code indicates that the process is attempting to grant Network Access to the Certificate during Setup, but fails.
    "...Could not grant Network Service access to the certificate"
    Exchange 2013 is being installed on Windows Server 2012 R2 but it is a member server with no domain responsibilities.  Granting rights to the certificate during the Setup process is the root of the problem.
    Here is the complete error comment:
    The following error was generated when "$error.Clear();
              Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "Could not grant Network Service access to the certificate with thumbprint 681FC4E2C66D726EFB91A8E0FF7FF6F98942C2F4 because a cryptographic exception was thrown.".

  • Cannot overcome Exchange Server 2013 Install Error - "There was an error while running 'ldifde.exe' to import the schema file

    Hello,
    I am attempting to install Exchange 2013 on to a 2008R2 Server on a domain running 2008R2 DC's.  I have worked every error resolution I can find, but I can't get past this error.
    Error:
    The following error was generated when "$error.Clear();
    install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema27.ldf")
    " was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\schema27.ldf'. The error code is: 8224.
    Any assistance is appreciated.

    Are you running the installation from an ISO-file?
    If so, then copy the files (preferably
    Exchange 2013 w. SP1) to the local disk
    and run the install with elevated privileges.
    Martina Miskovic

  • Exchange server 2013 roles error

    Hello,
    After successfully installed Microsoft Exchange 2013 coexistence with Exchange 2007, I run into many problems. I am getting event ID 1023:Microsoft-Windows-Perflib: Windows cannot load the extensible counter DLL MSExchangeIS. The first four bytes (DWORD)
    of the Data section contains the windows error code.
    Event ID 6003: MSExchange Common: ConnectitityLog: Failed to create log directory: Access is denied to path. What kind of access permission do I give to the file directory?
    Jimmy
    Jimmy

    Hello,
    For event id 1023, here is the article for your reference.
    Event ID 1023 -Performance Library Availability
    http://technet.microsoft.com/en-us/library/cc727009(v=ws.10).aspx
    If the event persists, I suggest you post the event id to windows server forum.
    http://social.technet.microsoft.com/Forums/en-US/winserver8gen/threads
    For event id 6003, please make sure that the path of the log directory does not contain any directory with read-only permissions.
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • 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.

  • Exchange Server 2013 Client Mail are Return.Error is [0x80040305-0x0004de-0x00054a]

    Hi,
    We are using Exchange Server 2013.we have Outlook 2007 SP3 and 2010 SP2 client .Some clients inform mails are return.
    Return massage
    "This message could not be sent. Try sending the message again later, or contact your network administrator. Your server administrator has limited the number of items you can open simultaneously.
    Try closing messages you have opened or removing attachments and images from unsent messages you are composing. Error is [0x80040305-0x0004de-0x00054a]"
    Thanks,
    Gayan

    1) Disable TCPChimney and RSS on CAS and Mailbox Servers by running below commands
    netsh int tcp set global chimney=disabled
    netsh int tcp set global rss=disabled
    2) Disable unwanted Add-Ins in outlook that may open many sessions
    3) If above steps doesnt resolve, you can delete existing outlook profile and create new Outlook online profile

  • 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

  • Exchange Server 2013 // MFCMAPI could connect with errors

    While connecting with Exchange Server 2013 I have started facing problem with my application.
    My application fails to connect to Exchange with below parameters, then i have tried using MFCMAPI to if everything is okay. MFCMAPI could connect with above errors.
    And I have tried with program using below parameters, i still get network error from MAPI call. Can you kindly help, I can provide any additional
    details needed.
    ___ props[prop_count].ulPropTag = PR_PROFILE_UNRESOLVED_NAME;
        props[prop_count].Value.lpszA   = <ProfileUnresolvedName>;
        prop_count++;
        props[prop_count].ulPropTag     = PR_PROFILE_UNRESOLVED_SERVER;
        props[prop_count].Value.lpszA   = <[email protected]>;
        prop_count++;
        // Setting this to TRUE causes OpenMsgStore() to fail with MAPI_E_UNCONFIGURED
        props[prop_count].ulPropTag      = PR_CONVERSION_PROHIBITED;
        props[prop_count].Value.b        = FALSE;
        prop_count++;
        props[prop_count].ulPropTag     = PR_PROFILE_CONFIG_FLAGS;
        props[prop_count].Value.l       = CONFIG_SERVICE /*| CONFIG_PROMPT_FOR_CREDENTIALS
    | CONFIG_SHOW_CONNECT_UI */;
        prop_count++;
        props[prop_count].ulPropTag     = PR_DISPLAY_NAME;
        props[prop_count].Value.lpszA   = <Mailbox Profile Name>;
        prop_count++;
        //Above setting used to be sufficient to connect using RPC
        //Below parameters added to connect via HTTPS
        LPSTR pwszUser = "domain\\username"; //also tried
    [email protected] AND username
        LPWSTR pwszPassword = L"paswword"; // Password has been encrypted using CryptProtectData
        props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_W;
        props[prop_count].Value.lpszW = L"https://ProxyHostname.domain";
        prop_count++;
        props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_AUTH_PACKAGE;
        props[prop_count].Value.l = RPC_C_AUTHN_NONE;      // RPC_C_HTTP_AUTHN_SCHEME_NTLM,
    RPC_C_HTTP_AUTHN_SCHEME_BASIC
        prop_count++;
        props[prop_count].ulPropTag =  PR_PROFILE_RPC_PROXY_SERVER_FLAGS;
        props[prop_count].Value.l = PRXF_ENABLED | PRXF_SSL;// | PRXF_IGNORE_SEC_WARNING; // | PRXF_IGNORE_SEC_WARNING;
        prop_count++;
        props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_PRINCIPAL_W;
        props[prop_count].Value.lpszW = L"msstd:certificateserverhostname.domain";
        prop_count++;
        props[prop_count].ulPropTag = PR_PROFILE_AUTH_PACKAGE;
        props[prop_count].Value.l = RPC_C_AUTHN_GSS_NEGOTIATE;               
    // RPC_C_AUTHN_WINNT, RPC_C_AUTHN_GSS_NEGOTIATE, RPC_C_AUTHN_NONE
        prop_count++;
        props[prop_count].ulPropTag = PR_PROFILE_AUTH_USER_W;
        props[prop_count].Value.lpszA = pwszUser;
        prop_count++;
        props[prop_count].ulPropTag = PR_PROFILE_AUTH_PASSWORD;
        props[prop_count].Value.bin.lpb = dataBlobOut.pbData;
        props[prop_count].Value.bin.cb = dataBlobOut.cbData;
        prop_count++;
        DB( (DB_PR _T("ConfigureExchangeService() About to configureMsgService\r\n"),
    this ) );
        hres = lpServiceAdmin->ConfigureMsgService( exchUID, 0, config_flags, prop_count, props
        I still get MAPI_E_NETWORK not found
    Are there any configuration changes need to be done on Exchange Server?
    Is there any mistake in above parameters?
    Kindly suggest.

    You can refer Dave's blog post @
    http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx
    DeVa, M.S., {MSFT} Please remember to mark the replies as answers if they help

  • Exchange Server 2013 Missing file on ISO install Error Code 1603

    Hi all,   a mystery needs solving any suggestions much appreciated:
    We are trying to install Exchange Server 2013 on Windows 2012 server.
    The ISO File being used is: SW_DVD9_Exchange_Svr_2013w_SP1_MultiLang_Std_Ent_MLF_X19-35118
    All preparation and requisites in place.
    During Stage 2 Copying files, we receive an error code 1603 and installation halts.
    The error states:
    Installing product F:\exchangeserver.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'Source file not found: F:\Setup\ServerRoles\ClientAccess\Owa\prem\version\resources\themes\base\0\microsoft.o365.controls.timeline.mouse.css.
     Verify that the file exists and that you can access it.'.
    We have verified that the Path in the error is correct and exists BUT the file is not present within the 0 folder.
    We have downloaded the ISO from our Action Pack resources twice and attempted 4 separate installations.
    We have tried both Mailbox/Client Access  and Mailbox only installations.
    The missing file: microsoft.o365.controls.timeline.mouse.css. Hopefully the only file misisng???
    Any ideas anyone, could we source a different ISO or copy of the file or ?????
    Many thanks in advance

    Had the same issue with Exchange 2013 SP 1 Downloaded as an ISO from the Volume License Center, installing on a new Server 2012R2 STD box. I found the equivalent file in another ISO but discovered it was just an empty CSS file. So the easiest way is to not
    bother trying to find the file but: 1) open notepad, 2) set save to "All Files", and 3) save an empty CSS file with that filename then place it in the directory indicated in the path given in the error. (Make sure it saves as
    a CSS and not as a TXT.)
    I reran the install and it completed without issue.

  • Http 500 internal server error exchange server 2013

    Hello Everyone
    Here is my little scenario.
    i have a domain named contoso.com
    i then installed exchange server 2013 in my environment.  cas and mailbox server are on seperate box.
    switched of my exchange servers for a week, during that period i changed the netbios name of my domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
    a week later i switched on my exchange servers. during the same time i created two new servers one cas and the other mailbox
    i now have 2 cas server and 2 mailbox server
    problem now is that when i log into my ecp on one of my cas server using https://servername/ecp. after inserting my username and password i get http 500 internal error
    although with exchange management shell i can connect to all the servers

    -->switched of my exchange servers for a week, during that period i changed the netbios name of my
    domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
    Did you change your domain to toso.com? If yes then your first/previously installed exchange is broken. Exchange server is fully integrated with domain. 
    Renaming of domain is not supported in Exchange2007/2010/2013.  (Even in Exchange2000/2003 you need some netbios name resolution. Check this for an info)
    Anyway did you try login to the newly installed exchange (i.e. Exchange installed after Netbios rename)? 
    Try that first https://newserverip/ECP and https://newserverip/OWA (that is supposed to work), If
    that works I suggest you try to uninstall the previously installed Exchange after moving the database using database portabilityand install again as new
    server.
    Please get back with the result.
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • CANNOT ACCES EXCHANGE ADMIN CENTER (ECP) ON EXCHANGE SERVER 2013. GOT HTTP 500 INTERNAL SERVER ERROR

    HI, I just installed Exchange server 2013 Standar SP1 on a windows server 2012.  I have 3 servers one is a Domain Controller, the other one has the MBX role, and the last one the CAS role,  first i installed the MBX and after the CAS role, i passed
    prerequisite check without any issue.  However when I tried access Exchange Admin Centre (ECP) at https:\\servername\ecp
    I got HTTP 500 Internal Server Error saying  "This website cannot display the page.  Most likely causes: 1. The website is under maintenance. 2. The website has a programming error."   I tried access ECP at https://localhost/ecp and
    I got the same problem.  Under either cases I was able to see the logon page of  ECP and I was able to enter my credential (e.g. domain\user name, password).  However I got HTTP 500 Internal Server Error at the next page.
    I appreciate your help, on my case.

    Hi,
    The link that Jatin points to should be this.
    https://social.technet.microsoft.com/Forums/en-US/2f64d305-e9e2-4f48-a5b4-4f72d7bca801/exchange-2013-owaecp-http-500-internal-server-error?forum=exchangesvrclients
    Please view the Application Pool to check whether the version of .NET Framework is 4.0 and try the following command.
    %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i.
    If this does not help then please check if there is any warnings or errors in Event Log and take your time to post them for my further troubleshooting.
    Thanks.

  • Installation error for Exchange Server-2013

    I am trying to install exchange server-2013 on my Windows server-2012
    machine. I have configured per-requisite applications and develop the server environment with active directory roles.
    At my readiness check option, it shows the following error:-
    "An unsupported operating system was detected . Exchange server-2013 client access and mailbox server roles support windows server -2008R2 SP1 or later  and windows server-2012".
    I am not using any V-machine or option. So how do i resolve the issue to install the Exchange server-2013? Please help me.
    Regard
    Azad 
    Azadur Sarker 6, Seaford street Stoke-on-Trent, ST4 2EU

    Hi I found after promoting the exchange server as a Domain controller re-installing AD prep and running extending Schema completed successfully , I'm now able to get rid of exchange cmdlet logs event id and can successfully see and connect through  the
    exchange 2013  management shell  
    "Get-Exchangeserver" 
    However still not able to connect to https://localhost/eac and when i re-run setup 
    01-28-2014 21:10:16.0804] [0] Starting Microsoft Exchange Server 2013 Setup
    [01-28-2014 21:10:16.0804] [0] **********************************************
    [01-28-2014 21:10:16.0804] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
    [01-28-2014 21:10:16.0804] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
    [01-28-2014 21:10:16.0804] [0] Setup version: 15.0.516.32.
    [01-28-2014 21:10:16.0804] [0] Logged on user: TESTLAB\Administrator.
    [01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='sourcedir', Value='D:\'.
    [01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='mode', Value='Install'.
    [01-28-2014 21:10:16.0882] [0] RuntimeAssembly was started with the following command: '/sourcedir:D: /mode:Install'.
    [01-28-2014 21:10:17.0085] [0] The following roles are installed: BridgeheadRole AdminToolsRole 
    [01-28-2014 21:10:17.0726] [0] Setup is choosing the domain controller to use
    [01-28-2014 21:10:17.0820] [0] The MSExchangeADTopology has a persisted domain controller: Exch2013.Testlab.labyyz.testnet.rim.net
    [01-28-2014 21:10:18.0023] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use Exch2013.Testlab.labyyz.testnet.rim.net
    [01-28-2014 21:10:18.0023] [0] Setup is choosing a global catalog...
    [01-28-2014 21:10:18.0023] [0] Setup has chosen the global catalog server Exch2013.Testlab.labyyz.testnet.rim.net.
    [01-28-2014 21:10:18.0023] [0] Setup will use the domain controller 'Exch2013.Testlab.labyyz.testnet.rim.net'.
    [01-28-2014 21:10:18.0023] [0] Setup will use the global catalog 'Exch2013.Testlab.labyyz.testnet.rim.net'.
    [01-28-2014 21:10:18.0023] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0038] [0] Exchange organization container for the organization is 'CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0054] [0] Setup will search for an Exchange Server object for the local machine with name 'EXCH2013'.
    [01-28-2014 21:10:18.0210] [0] Exchange Server object found : 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0210] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole 
    [01-28-2014 21:10:18.0210] [0] The following datacenter roles are unpacked: 
    [01-28-2014 21:10:18.0210] [0] The following roles are installed: BridgeheadRole AdminToolsRole 
    [01-28-2014 21:10:18.0210] [0] The local server has some Exchange files installed.
    [01-28-2014 21:10:18.0226] [0] Server Name=EXCH2013
    [01-28-2014 21:10:18.0242] [0] Setup will use the path 'D:\' for installing Exchange.
    [01-28-2014 21:10:18.0257] [0] Setup will discover the installed roles from server object 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0257] [0] 'BridgeheadRole' is installed on the server object.
    [01-28-2014 21:10:18.0257] [0] The installation mode is set to: 'Install'.
    [01-28-2014 21:10:39.0632] [0] An Exchange organization with name 'TestLab' was found in this forest.
    [01-28-2014 21:10:39.0632] [0] Active Directory Initialization status : 'True'.
    [01-28-2014 21:10:39.0632] [0] Schema Update Required Status : 'False'.
    [01-28-2014 21:10:39.0632] [0] Organization Configuration Update Required Status : 'False'.
    [01-28-2014 21:10:39.0632] [0] Domain Configuration Update Required Status : 'False'.
    [01-28-2014 21:10:39.0632] [0] The locally installed version is 15.0.516.32.
    [01-28-2014 21:10:39.0632] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
    [01-28-2014 21:10:39.0664] [0] Applying default role selection state
    [01-28-2014 21:10:39.0710] [0] Setup is determining what organization-level operations to perform.
    [01-28-2014 21:10:39.0710] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
    [01-28-2014 21:10:39.0710] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
    [01-28-2014 21:10:39.0710] [0] InstallModeDataHandler has 0 DataHandlers
    [01-28-2014 21:10:39.0710] [0] RootDataHandler has 1 DataHandlers
    [01-28-2014 21:10:40.0273] [0] Finished loading screen IncompleteInstallationDetectedPage.
    [01-28-2014 21:11:08.0117] [0] Setup is determining what organization-level operations to perform.
    [01-28-2014 21:11:08.0117] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
    [01-28-2014 21:11:08.0117] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
    [01-28-2014 21:11:08.0117] [0] InstallModeDataHandler has 0 DataHandlers
    [01-28-2014 21:11:08.0117] [0] RootDataHandler has 1 DataHandlers
    [01-28-2014 21:11:08.0335] [0] Finished loading screen SetupProgressPage.
    [01-28-2014 21:15:30.0513] [0] End of Setup
    [01-28-2014 21:15:30.0513] [0] **********************************************

  • 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

Maybe you are looking for