Exchange 2013 ECP failure after installing RDP

I have a fresh install of Server 2012 and Exchange 2013, everything was working great and I could access the ECP, I then installed Remote Desktop Services and I could no longer access the ECP or OWA, I have now removed the Remote Services but still cannot
access the ECP, does anyone know how to repair this without having to wipe and start again? any help appreciated.
Thanks
J

Have you tried to recreate the ECP virtual directory?
http://www.curu.ca/2013/01/how-to-re-create-ecp-virtual-directory-in-exchange-2013/
For OWA -
http://exchangeonline.in/re-create-owa-virtual-directory-exchange-2013/

Similar Messages

  • SharePoint Server 2013 Upgrade failure after Updating SP1 + Nov10 CU " Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown"

    After Successfully having SharePoint Server 2013 Farm Installation on 2 Servers AD + Central Admin Application server, OS: win server 2008 R2 Ent SP1.
    I set up the configuration for SharePoint app and Workflow Manager to work properly on the Den environment,  the time for SP1 running has come and after downloading the Service pack 1 of SharePoint server 2013 and completing the wizard, I run the SharePoint
    2013 Configuration Wizard after installing SharePoint 2013 SP1, and the wizard failed on step 2 with the Error from the Log file as showing below,
    "Task upgradebootstrap has failed with an unknown exception 
    01/04/2015 00:43:30  11  ERR                  Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown.
       at Microsoft.SharePoint.Upgrade.SPManager.BootStrap(Guid sessionId, SPUpgradeOperationFlags flags)
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()"
    Also I was not able to create websites like before, and the creating of new site is failed with error message :
    "Failed to call GetTypes on assembly Microsoft.Office.TranslationServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Method not found: 'Microsoft.Office.Web.Common.ProcessImageInfo"
    Is there any solution to my problem with SP1 of SharePoint Server 2013, I don't think that SP1 should generate such bugs in a stable environment.
    Basel Badr ,SharePoint Specialist ,MCAD ,MCTS.

    Hi Basel,
    What edition of SharePoint do you have and what patch did you attempt to install?
    If you are on SharePoint 2013 Enterprise, please make sure you are installing Service Pack 1 for SharePoint Server:
    http://www.microsoft.com/en-us/download/details.aspx?id=42544
    If you are on SharePoint 2013 Foundation, please make sure you are installing  Service Pack 1 for SharePoint Foundation :
    http://www.microsoft.com/en-us/download/details.aspx?id=42548
    For more information, you can refer to the thread:
    https://social.technet.microsoft.com/Forums/sqlserver/en-US/ba9656e9-837e-4261-b164-b5bdfe8adce3/why-does-machine-translation-fail-when-i-do-not-use-it?forum=sharepointgeneral
    http://sharepoint.stackexchange.com/questions/84284/failed-to-call-gettypes-on-assembly-microsoft-office-translationservices
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • Problem with Exchange 2010 Public Folders after installing Exchange 2013 in my environment.

    I currently have an Exchange 2010 server with all the roles installed.  Before installing Exchange 2013, I was able to launch the Public Folder Management Console but now I get an error.  When I installed Exchange 2013, I got an error saying I
    had a instance of Exchange 2000 or Exchange 2003, but I didn't have any of these servers left.  There was still something in AD referencing my old server. I went into ADSIedit and deleted an old administrative group.  This deletion caused my access
    to my public folders to get messed up.  I followed this article, http://blog.bruteforcetech.com/archives/766, and I was able to gain access back in my outlook client but I still can't see the public folders in OWA.  I also get this error when
    trying to access either Default or System Public Folders.  "Cannot complete the operation because there isn't an available public folder database on server 'ExchangeServer'. It was running the command 'get-publicfolder - getchildren -identity '\'
    -server 'ExchangeServer' "
    My Public Folder Database exists and is mounted.  Any help is appreciated.

    Hi Belinda,
    Thank you for responding.  Yes you do understand my problem correctly.  One correction is that after deleting this entry in ADSIEdit, we couldn't access public folders at all either in Outlook or OWA.  I followed these steps in the below article:
     http://blog.bruteforcetech.com/archives/766
    After following these steps and recreating the entry on FolderHieachies in ADSI edit, I was able to gain access to the public folders again through Outlook, but still can't see them in OWA and can't access them in Public Folder Management Console.
    Here are the results to your requests:
    et-PublicFolder -Recurse | Format-List Name
    Name : IPM_SUBTREE
    Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRAT
    GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
        + CategoryInfo          : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
        + FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
    [PS] C:\Windows\system32>Get-PublicFolder -Identity \NON_IPM_SUBTREE -Recurse | Format-List Name
    Name : NON_IPM_SUBTREE
    Name : EFORMS REGISTRY
    Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRATIVE
    GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
        + CategoryInfo          : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
        + FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
    Also the msExchOwningPFTree attribute should be correct because this was edited with the correct value when I followed the instructions in the above article:
    CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Heroix Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hero,DC=net

  • Exchange 2013 ECP "500 Unexpected Error" after Updates

    Hi *,
    after installing the latest Server 2012 Updates, i get the error "500 Unexpected Error" when i try to Login to the Exchange ECP. There wer no changes to the URL or front-/backend.
    I also tried the Workaround focussed over here: http://social.technet.microsoft.com/Forums/exchange/en-US/777b51ee-330d-43cc-a56e-4614d44aed7b/unable-to-access-owa-or-ecp-something-went-wrong-or-500-unexpected-error?forum=exchangesvrclientsentries but
    there were no entries like CN=Services at the ADSI edit.
    Best Regards
    Max @ Magelan Support

    Hi Max,
    Please double check the port bindings are correct.
    Please try to run lodctr /r and reset IIS as administrator.
    Found a similar thread for your reference:
    Unable to access ECP. -  "500 unexpected error"
    http://social.technet.microsoft.com/Forums/en-US/b4b7c47e-cde4-4c62-8bb1-91a5430d4814/unable-to-access-ecp-500-unexpected-error?forum=exchangesvrclients
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 ECP redirects to OWA

    Dear Collegues,
    after that I ve installed Exchange 2k13 on my win server 2012 std, I am not able to reach the EAC, when I tried to enter this URL: https://servername/ecp or https://servername/ecp?ExchClientVer=15 it redirects me always to OWA. I ve also tried this solution
    http://www.telnetport25.com/2012/11/quick-tipcreating-an-icon-on-the-desktop-for-the-exchange-2013-eac/ with no effect, also this http://lyncdude.com/2013/02/07/cannot-access-exchange-contorl-panel-ecp-in-exchange-server-2013/, but what really strange is,
    that my powershell cant recognize for ex. this syntax -  Get-owavirtualdirectory | fl or Set-owavirtualdirectory -identity “owa <Default Web site>” -FormAuthentication:$true at all.
    I am really confused with all of that Exchange 2k13 installation and configuration, from the beginning there are so many problems.
    Please can anyone help me?

    Hi,
    To enable the system mailboxes, I’d like to confirm how you disable them: delete the mailboxes from the Exchange management tool or delete the account from the ADUC.
    For more detailed steps to enable the system mailbox, you can refer to the following article:
    http://social.technet.microsoft.com/wiki/contents/articles/6874.how-to-recreate-system-mailbox-federatedemail-discoverysearchmailbox-in-exchange-2010.aspx
    For the redirection issue, I recommend you check the result if you login with a admin account: check it’ OWA or EAC.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2013 ECP 503 error

    I have a problem with my two Exchange 2013 servers. There are no mailboxes on the servers, because we are just beginning our migration from Exchange 2007. We are running Exchange 2013 SP1 on Server 2012R2
    When I try to access ecp/owa on ex01 (https://localhost or https://ex01.domain.local), I am presented with a login page, but after entering my credentials,
    I get a 503 error:
    Service Unavailable HTTP Error 503. The service is unavailable
    On ex02, I can RDP to the server and log into ecp/owa just fine. However, if I log in (https://ex02.domain.local) from another computer (like my PC), I get the
    same credential page and 503 error.
    I verified the following:
    All of the application pools and Exchange services are started
    I do not have any instances of event 2280 in the Application log
    I have also restarted the server
    Local security policy shows that Administrators and Backup Operators have "Allow log on locally" permission
    This feels like a permissions issue in IIS, but I'm not sure.
    My ECP virtual directory settings (both servers) look like this:
    InternalAuthenticationMethods : {Basic, Fba}
    BasicAuthentication : True
    WindowsAuthentication : False
    DigestAuthentication : False
    FormsAuthentication : True
    LiveIdAuthentication : False
    AdfsAuthentication : False
    OAuthAuthentication : False
    ExternalAuthenticationMethods : {Fba}
    Why won't ex01 let me log in and why would the login on ex02 work from the server, but 503 from my machine? Thanks.

    Hi,
    From your description, I would like to clarify the following things for troubleshooting:
    1. Make sure that the services are running under the Local System account.
    2. Ensure that the mailbox database that you want to access are mounted. Besides, the account you use to access ECP should have a mailbox in the Exchange server you are accessing.
    Hope my clarification can be helpful to you.
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2010 SP3 cohabitation Exchange 2013 ecp?exchver=15 from external not work

    Hi
    i have installed an exchange 2013 cohabitation with exchange 2010 for migration. outlookanywere,ecp,owa, autodiscovery...etc are configurered
    when i try to connect to the eac or owa internaly its work, but when i try to do externaly https://mail.mydomain.com/ecp?exchver=15
    i have error 302, 301 to many redirections
    how can i fix this
    thanksin advance

    Hi,
    Generally, status 301 means that the resource (page) is moved permanently to a new location. Please refer to Sneff_Gabor's suggetsion to check the Redirect setting s for OWA and ECP in IIS manager.
    Additionally, please provide more information about your issue and collect any error logs for further troubleshooting.
    Regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 ECP redirects to 2010 OWA still

    I have a new Exchange 2013 SP1 server on a 2012 R2 OS where I've installed both Mailbox and Client Access roles in an existing Exchange 2010 environment.  Initially ran into some DNS issues that caused errors installing the Client Access server, but
    I fixed those, removed Exchange 2013 and reinstalled with no errors.  In every scenario so far, trying to access the ECP redirects you to the 2010 OWA.  I have been scouring threads for hours and tried everything I've seen, but to no avail.  I
    have tried:
    1) Using the https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15 URL, which still
    redirects to the 2010 OWA
    2) Creating a new user account with all of the same rights as the domain admin but has no mailbox, which redirects to the 2010 OWA and throws an error that there is no mailbox.
    3) Setting the domain in IIS authentication settings for the ECP on both the 2013 and 2010 server.
    Does anyone have any ideas here on what to try next?

    Try creating a mailbox for the administrative account on the Exchange 2013 server or moving the existing mailbox.
    I've seen issues like you're experiencing in various forms before myself, though not exactly as you've reported.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Error During Exchange 2013 Mailbox Transport Role Install On Server 2012

    I was installing Exchange 2013 on Server 2012.  The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin.  There has never been an Exchange instance on this domain.  I got past
    the prerequisite checks, and the installer showed 15 steps, so I walked away.  When I came back, I saw this:
    Step 8 of 15: Mailbox role: Transport service
    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: "Unable to set shared config DC.".
    The only option on the screen was exit, so I did.  I checked the start menu, and there were two new Exchange icons, but I did not click them.  I ran the installer again, and it detected an incomplete install, the only option was to click next to
    finish the install, so I clicked next.  This time, I eventually got the same error, except the screen showed "Step 8 of 15: Mailbox role: Transport service."  I did install some Exchange 2010 prerquisites on the server before Exchange Server 2013
    came out, and I can rebuild the server and try the install again if that would be best, but I thought I should post here first and try to work through this since the product is so fresh.  Any suggestions?

    I've tried three times since my last post, following
    http://msexchange2010.info/archives/2330 as closely as possible the most recent time.  I am consistently getting the same error that appears to imply I don't have write access to the domain.  I don't understand this, because I am using the
    same domain admin account I have been using all along.  Nonetheless, here is the powershell output starting with the first Exchange setup.exe step (all other steps were already performed, all available updates were installed, and the server was rebooted
    prior to this):
    Windows PowerShell
    Copyright (C) 2012 Microsoft Corporation. All rights reserved.
    PS (domain admin home)> D:
    PS D:\> .\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
    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 COMPLETED
    Configuring Microsoft Exchange Server
    Extending Active Directory schema COMPLETED
    The Exchange Server setup operation completed successfully.
    PS D:\> .\Setup.exe /PrepareAD /OrganizationName:PRD-INC /IAcceptExchangeServerLicenseTerms
    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 COMPLETED
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
    een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
    aspx
    Configuring Microsoft Exchange Server
    Organization Preparation COMPLETED
    The Exchange Server setup operation completed successfully.
    PS D:\> .\Setup.exe /Mode:Install /Roles:ClientAccess, Mailbox, ManagementTools /t E:\Exchange /IAcceptExchangeServe
    rLicenseTerms
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Languages
    Management tools
    Mailbox role: Transport service
    Mailbox role: Client Access service
    Mailbox role: Unified Messaging service
    Mailbox role: Mailbox service
    Client Access role: Front End Transport service
    Client Access role: Client Access Front End service
    Performing Microsoft Exchange Server Prerequisite Check
    Configuring Prerequisites COMPLETED
    Prerequisite Analysis COMPLETED
    Configuring Microsoft Exchange Server
    Preparing Setup COMPLETED
    Stopping Services COMPLETED
    Copying Exchange Files COMPLETED
    Language Files COMPLETED
    Restoring Services COMPLETED
    Language Configuration COMPLETED
    Exchange Management Tools COMPLETED
    Mailbox role: Transport service COMPLETED
    Mailbox role: Client Access service COMPLETED
    Mailbox role: Unified Messaging service COMPLETED
    Mailbox role: Mailbox service FAILED
    The following error was generated when "$error.Clear();
    if ($RoleIsDatacenter -ne $true)
    if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
    $sysMbx = $null;
    $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
    $dispName = "Microsoft Exchange";
    Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
    $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
    if ($mbxs.Length -eq 0)
    Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
    $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
    if ($dbs.Length -ne 0)
    Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
    $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
    if ($arbUsers.Length -ne 0)
    Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
    $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0
    ].Identity;
    else
    if ($mbxs[0].DisplayName -ne $dispName )
    Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
    Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
    $sysMbx = $mbxs[0];
    # Set the Organization Capabilities needed for this mailbox
    if ($sysMbx -ne $null)
    # We need 1 GB for uploading large OAB files to the organization mailbox
    Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
    set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions
    :$true -MailRouting:$true -MaxSendSize 1GB -Force;
    else
    Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
    else
    Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
    " was run: "Database is mandatory on UserMailbox.".
    The following error was generated when "$error.Clear();
    if ($RoleIsDatacenter -ne $true)
    if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
    $sysMbx = $null;
    $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
    $dispName = "Microsoft Exchange";
    Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
    $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
    if ($mbxs.Length -eq 0)
    Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
    $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
    if ($dbs.Length -ne 0)
    Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
    $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
    if ($arbUsers.Length -ne 0)
    Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
    $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0
    ].Identity;
    else
    if ($mbxs[0].DisplayName -ne $dispName )
    Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
    Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
    $sysMbx = $mbxs[0];
    # Set the Organization Capabilities needed for this mailbox
    if ($sysMbx -ne $null)
    # We need 1 GB for uploading large OAB files to the organization mailbox
    Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
    set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions
    :$true -MailRouting:$true -MaxSendSize 1GB -Force;
    else
    Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
    else
    Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
    " was run: "Database is mandatory on UserMailbox. Property Name: Database".
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    PS D:\>
    I am cleaning out in ADSI and rebuilding the server for now, because the server is behaving oddly (not as oddly as it was with 6GiB, but oddly, nonetheless).  I probably won't try to install Exchange again before tomorrow.  What should I do to prevent
    encountering the above again and/or if I encounter it again?

  • Exchange 2013 ECP Login fails HTTP 404 Requested URL: /owa/auth/logon.aspx

    Hi,
    One of our Exchange servers stopped allowing access to OWA and ECP. I have now managed to get OWA working but ECP is still failing. When connecting to ECP using https://servername/ecp/ it asks me for my username and password. After hitting enter it shows
    me an error page:
    Server Error in '/owa' Application.
    The resource cannot be found.
    Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.
    Requested URL: /owa/auth/logon.aspx
    URL in the address bar while on this screen: https://exchangeserver:444/owa/auth/logon.aspx?url=https://exchangeservera:444/ecp/&reason=0
    Question: When the URL points to servername:444/owa/auth/logon.aspx - Is it trying to find the logon.aspx in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\auth? There is no such file in that directory?
    I have removed and recreated the ECP and OWA virtual directories several times.
    I am trying to login using a domain administrator account.
    Thanks,

    Hi,
    Is there any Exchange server 2010 coexistence with your Exchange 2013 server? If it is, please try the URL
    https://CAS15-NA/ecp?ExchClientVer=15 to access ECP.
    Also run the following to check your OWA and ECP virtual directories:
    Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Authentication*
    Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Authentication*
    And make sure the Basic and Forms authentications are enabled in
    Default Web Site and Ntlm, WindowsIntegrated
    authentication methods are enabled in
    Exchange Back End. Then restart IIS service by running
    iisreset /noforce from a command prompt window.
    If the issue persists, please collect any event logs or IIS logs for further analysis.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 : OWA failing after login with error "HTTPS 400"

    Greetings,
    I am in phase of Upgrading my existing Exchange 2007 Infra to Exchange 2013.
    The environment is as mentioned below:
    4 Mailbox Server (DAG)
    4 CAS Servers (NLB)
    Everything has been configured and working properly, except Only one CAS server is able to pass the login request
    https://servername/owa
    Rest of all the CAS servers are failing with error "HTTPS 400" while accessing OWA
    https://localhost/owa
    Its happening only while accessing OWA, ECP works fine.
    Please let me know the fix to counter this strange issue.
    Thanks in advance.
    Regards

    Hi,
    Please check if IIS log is enabled on the CAS server, if not, please enable it.
    Then check the detailed error code from IIS logs (Path: inetpub\logs\Logfiles\W3SVC1 ) , some code like 400.1, 400.2 ect.
    Refer to this KB for more details
    http://support.microsoft.com/kb/943891
    After that, please post the OWA related login entry with error code shows 400.
    Thanks for your time and patience.
    Meanwhile, please check the OWA authentication method by command
    Get-OWAVirtualDirectory –Server “Ex2013 CAS server” | fl *authentication*
    We should set the authentication as the below:
    Get-OWAvirtualdirectory -Server “Ex2013_CAS_server” | set-OWAvirtualdirectory -windowsAuthentication $False -BasicAuthentication $True -FormsAuthentication $True
    Then perform iisreset and try to access OWA again.
    Best Regards.

  • Exchange 2013 disconnects externally after every hour but works fine internally

    Hello All,
    I have a very strange problem in my office. At the new years eve, there was a disconnection in our Internet from our ISP and everything came back online again after 1 hour. before this happened everything was working fine such as externally all the mobile
    devices were able to connect to exchange 2013 and event owa was working fine and laptop devices as well. All was good, but once the disconnect happened, i am only able to access my emails over 3 G connection but not over the ISP connection, what i mean from
    that is that if i try to connect to owa or my outlook from home DSL connection i cannot connect but with my 3g connection on my phone i can connect and everything works fine. i have re issued the certificates and installed them again, but still the same thing,
    after every hour or sometimes less the exchange 2013 sort of disconnects and starts working when i restart the CAS server where the traffic is routed to.
    Has any one faced this issue, please help, i was thinking that something wrong with my firewall as i was not even able to connect to my ssl vpn so i thought that firewall is culprit, but i have replaced the firewall as well and still the same issue.
    Please help, i am trying to troubleshoot this problem since last 10 days but with no luck.
    Thank You. 

    Have you checked the network settings? Do you have multiple network adapters? May be DNS related also. Check, if you have configured DNS correctly.  
    Regards from ExchangeOnline.in|Windows Administrator Area | Skype:[email protected]

  • Exchange 2013 Cu6 fails to install

    When I attempt to install CU6 on Exchange 2013 I get this error message and cannot continue, occurs after reboot as well and trying to re-run setup.  Any ideas how to fix?
    Thanks,
    Setup Error 2nd time 5 of 9 after restart
    Error:
    The following error was generated when "$error.Clear(); 
              $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
              $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
              $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
              if( $dismbx -ne $null)
              $srvname = $dismbx.ServerName;
              if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
              Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
              $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
              if( $mountedMdb -eq $null )
              Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
              mount-database $dismbx.Database;
              $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
              if( $mountedMdb -ne $null )
              $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
              $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
              if( $dmRoleGroup -ne $null )
                trap [Exception]
                  Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
                  continue;
                Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
            " was run: "Microsoft.Exchange.Data.Common.LocalizedException: Couldn't resolve the user or group "Domain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest
    principal, you must have either a two-way trust or an outgoing trust. ---> System.SystemException: The trust relationship between the primary domain and the trusted domain failed.
       at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed)
       at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
       at System.Security.Principal.NTAccount.Translate(Type targetType)
       at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
       --- End of inner exception stack trace ---
       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.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
       at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetSecurityPrincipal(IRecipientSession session, SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
       at Microsoft.Exchange.Management.RecipientTasks.SetMailboxPermissionTaskBase.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Hi,
    Thanks.  This did work for me.  CU6 applied, Exchange back up.  Go live in 2 weeks.  
    Delete the  Discovery Search mailbox user from Active Directory.  Start your Active Directory Users and Computers
    mmc and look for your Discovery Search Mailbox user. Default this user will be placed in the Users organizational unit. It will be named something like: DiscoverySearchMailbox{D919BA05-46A6-415f-80AD-7E09334BB852}. After deletion you can restart the installation
    of your Exchange Service Pack. It will not show the error anymore.
    To recreate the user use: setup
    /PrepareAD /IAcceptExchangeServerLicenseTerms

  • Exchange 2013 ECP/OWA Error 503 Service Unavailable

    Hi,
    Hoping that someone can clarify or assist with an issue relating to Exchange 2013 CU3..
    Both roles installed on a single 2012 server, mailboxes created, able to login to ECP/OWA using ht tps://servername.int.domain.com/ecp using the out of the box internally generated SSL certificate.
    Virtual directory internal and external settings for all directories were configured to be ht tps://mail.domain.com/owa /ecp /EWS etc and a UCC certificate (containing mail.domain.com, autodiscover.domain.com)from GoDaddy was imported and assigned to
    IIS and SMTP, internal DNS records were setup internally and externally for mail.domain.com and full propagated, Outlook Anywhere enabled and configured to mail.domain.com, external access configured for all virtual directories
    The issue is that ECP and OWA can only be accessed internally by the full internal server FQDN URL ht tps:// serverame.int.domain.com/ecp whereas it should be accessible at this point by ht tps:// mail.domain.com/ecp
    Error received both internal and external when trying ht tps://mail.domain.com / owa / rpc etc is error 503 Service Unavailable
    I know that the ECP and OWA sites are up and running as I can login and do anything by internal servername URL but no joy at all using the external (which is to be used for internal clients aswell for seamless access)
    The only way it works is by adding a host name to the 2 x 443 bindings in IIS for the front end website and set it to mail.domain.com but this means autodiscover.domain.com internally and externally wont work
    Is this normal and required for Exchange 2013 or is there a way to resolve this?
    Thanks in advance!

    Hi,
    I found a article might help you, for you reference:
    http://support.microsoft.com/kb/2619402
    Generally, this error occurs if the application pool that is associated with the web application doesn't start.
    To troubleshoot this issue, follow these steps:
    In Event Viewer, view the System log to find errors from the Microsoft-Windows-WAS source. An event is frequently logged in the System log if the application pool fails to start.
    If you don't find any relevant events in the System log, search for relevant entries in the HTTPERR log file. The httperr1.log file is located in the following system folder:
    c:\windows\system32\logfiles
    In the file, search on "503" to locate any relevant information about why the application pool failed. For example, you may see an entry that resembles the following:
    2011-12-08 18:26:42 ::1%0 6721 ::1%0 443 HTTP/1.1 GET /owa 503 3 N/A SharePoint+Web+Services+Root
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Exchange 2013 ECP and DAG issue

    Good Day,
    We have Exchange 2013 setup in Coexistence with Exchange 2007. Everything is working well except for two small issues I have noticed.
    Current Setup of 2013:
    SiteA:
    2x CAS Servers on Windows 2012 R2 configured with windows NLB (Internet Facing).
    2x MBX servers Configured in a DAG also running on Windows 2012 R2.
    SiteB:
    2x CAS Server on Windows 2012 R2.
    2x MBX servers Configured in a DAG also running on Windows 2012 R2.
    Issues I am having:
    Issue 1:
    When working on the ECP:
    I can do all tasks on servers in the same site but get some errors when trying to do tasks on servers in the other site.
    When trying to Activate a DB copy on the DAG at SiteB I get "The Microsoft Exchange Replication service does not appear to be running on Server name"
    And just trying to go to the properties of a server at SiteB "An error occurred while accessing the registry on the server servername"
    This happens vice versa.
    I can access all servers on the same site but not between sites with some tasks.
    I have made sure firewall is disabled and remote registry is indeed running but no luck.
    From a network perspective all ports are open between the sites.
    Issue 2:
    When I reboot a DAG member with the active mailbox databases for testing outlook connectivity I get two issues.
    Then I cannot access ECP at all until the server is up again.
    Outlook keeps staying on trying to connect until it is reopened.
    Any Ideas?
    I will gladly give more information if needed.
    Thank You
    Riaan Rourke
    Senior System Engineer

    Since I don't see this with Hyper-V I'll assume this is on ESX. Please let me know it that's not correct.
    In terms of virtualization best practices - whose list was that :) 
    There are multiple configuration things that you *MUST* do when using WLBS on ESX.  It will depend upon multiple things in the environment.  I'd start with this
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1556
    Fix that, and chances are the other item will be also remediated.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Maybe you are looking for