none
ECP Problem after CU1 RRS feed

  • Question


  • Hi,

    thanks for CU1!

    I have installed CU1 in my test environment (2xExchange 2010 SP3, 1x Exchange 2013 CU1)(i have to mention, that I installed and tested the EX2013 last week and applyed the CU1 today).

    After having fined I was not able to display "ecp" on Exchange 2013 server, cause after logon (with url pinting to EX2013) with admin (whos mailbox is on Exchange 2010) I get a redirect to ecp on Exchange 2010!

    Only with admin whos mailbox is on EX2013 everything works fine!


    Whats wrong?


    Lars
    Wednesday, April 3, 2013 11:00 AM

Answers

All replies

  • Hi,
    I am surprised to hear that you could log on to ECP on EX2013 when your mailbox was on EX10 without modifying the URL to /ecp?ExchClientVer=15

    Anyway...that is was you need to do.

    Exchange Admin Center in Exchange 2013
    http://technet.microsoft.com/en-us/library/jj150562(v=exchg.150).aspx


    Martina Miskovic

    • Marked as answer by KL-AAH Wednesday, April 3, 2013 1:14 PM
    Wednesday, April 3, 2013 1:05 PM
  • Hi Martina,

    thanks again, this was the solution!

    I am able to log on to EX2013 ecp when having the mailbox on EX2010. What I get is proxiying to Ex2010 ecp (like it works with owa).

    Best regards

    Lars

    Wednesday, April 3, 2013 1:14 PM
  • Greetings Martina,

    CU1 was recently installed and I have been unable to login to the Admin Center or OWA.  I had to utlilize PowerShell to move my Mailbox from Exchange 2010 Server over to the 2013 box and that was successful.  My Outlook client is able to connect and send/receive messages just fine.  I have checked my AD account and all required permissions look correct for accessing the EAC.

    When attempting to log into EAC or OWA I get "The user name or password you enter isn't correct. Try entering it again."

    Any thoughts?

    Cheers

    Wednesday, April 3, 2013 2:34 PM
  • Hi,

    did you try "https://<yourCAS>/ecp?ExchClientVer=15"?

    Maybe you want to recreate the virtual directory? http://www.curu.ca/2013/01/how-to-re-create-ecp-virtual-directory-in-exchange-2013/

    Regards

    Lars

    Wednesday, April 3, 2013 2:46 PM
  • Hello,

    I tried to access it as well with the URL you provided.  Same results.

    My Exchange Back End virtual directory only includes aspnet_client, bin, and PowerShell.  In the screen shots of the link you provided the Exchange Back End VD, looks to bit a lot more populated.  Could this be related to the authentication issue I am seeing?

    Cheers

    Wednesday, April 3, 2013 3:01 PM
  • Hi,

    I checked it and I have many entries "under" ecp in the Backend VD (see screenshot).

    You can try to recreate it.

    Lars

    Wednesday, April 3, 2013 3:11 PM
  • I realized what I was seeing now.  I have my CAS role and Mailbox role on separate servers.  The Exchange Back End vd is correctly populated on my Mailbox Server.
    Wednesday, April 3, 2013 3:28 PM
  • Hi!

    I have just installed CU1 and experience the same problem.

    I have one single exchange 2013 and pure windows server 2012 environment.

    After the update I can not access EAC anymore.

    I can access ECP for my mailbox, but not ECP as an administrator (EAC) HTTP 400 bad request.

    I have tried to remove and create EcpVirtualDirectory but no success.

    Any suggestions?

    /MrT


    Mr Tbone

    Thursday, April 4, 2013 7:56 AM
  • Hi MrT,

    did you try  "https://<yourCAS>/ecp?ExchClientVer=15"? Does the "non working administrator" have a mailbox? Or is a member of Exchange Group "organization management"?

    Regards

    Lars


    • Edited by KL-AAH Thursday, April 4, 2013 8:19 AM
    Thursday, April 4, 2013 8:16 AM
  • Yes to both.

    <a href="https:///ecp?ExchClientVer=15">https://<yourCAS>/ecp?ExchClientVer=15

    HTTP 400

    i´m using the administrator account and it has a mailbox and is a member of organization management.

    The administrator account can log on to OWA and open ECP. But not EAC anymore. worked before CU1.

    I start to suspect permissions problems but no solution yet.

    /MrT


    Mr Tbone


    • Edited by Mr Tbone Thursday, April 4, 2013 9:52 AM spelling
    Thursday, April 4, 2013 9:17 AM
  • Hi Mr Tbone,
    Pls confirm that the right authentication methods is configured as shown below.

    [PS] C:\>Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | fl Identity,*auth*


    Identity                      : EX2013\ecp (Exchange Back End)
    InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
    BasicAuthentication           : False
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : False
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    ExternalAuthenticationMethods : {Fba}

    Identity                      : EX2013\ecp (Default Web Site)
    InternalAuthenticationMethods : {Basic, Fba}
    BasicAuthentication           : True
    WindowsAuthentication         : False
    DigestAuthentication          : False
    FormsAuthentication           : True
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    ExternalAuthenticationMethods : {Fba}

    Also see: Cannot access Outlook Web App or the EAC after you re-create the "owa" or "ECP" virtual directory on an Exchange Server 2013 Mailbox server


    Martina Miskovic

    Thursday, April 4, 2013 9:28 AM
  • Yes to both.

    <a href="https:///ecp?ExchClientVer=15">https://<yourCAS>/ecp?ExchClientVer=15

    HTTP 400

    i´m using the administrator account and it has a mailbox and is a member of organization management.

    The administrator account can log on to OWA and open ECP. But not EAS anymore. worked before CU1.

    I start to suspect permissions problems but no solution yet.

    /MrT


    Mr Tbone

    Hi,

    now you write abour EAS? In above Post it was ECP!

    Lars

    Thursday, April 4, 2013 9:45 AM
  • Pardon my french!

    As stated up the thread it´s the ECP failing to show EAC (misspelled EAS).

    EAC is not a "real" web, It´s part of ECP.

    Identity                      : MAIL\ecp (Exchange Back End)
    InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
    BasicAuthentication           : False
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : False
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    ExternalAuthenticationMethods : {Fba}

    Identity                      : MAIL\ecp (Default Web Site)
    InternalAuthenticationMethods : {Basic, Fba}
    BasicAuthentication           : True
    WindowsAuthentication         : False
    DigestAuthentication          : False
    FormsAuthentication           : True
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    ExternalAuthenticationMethods : {Fba}

    Nothing wrong with authentication.

    I tried to add a new member in "organization management" but no success with EAC on that user either.

    /MrT


    Mr Tbone

    Thursday, April 4, 2013 10:00 AM
  • Ok, no authentication problems.
    Since your problem is different from the Original Poster, I think you should start your own thread.

    Martina Miskovic

    Thursday, April 4, 2013 10:09 AM
  • Sorry I borrowed this thread!

    I solved it! It was a wierd url issue.

    https://mail.contoso.se/ecp FBA then HTTP 400

    https://mail.contoso.se/ecp?ExchClientVer=15 FBA then HTTP 400

    https://mail.contoso.se/ecp/ FBA then EAC, Working!

    /MrT


    Mr Tbone

    • Proposed as answer by Horsebox_irl Monday, May 27, 2013 2:41 PM
    Thursday, April 4, 2013 10:51 AM
  • Hi,

    did I understand your post correctly: Only the "/" at the end is the solution?

    Regards

    Lars

    Thursday, April 4, 2013 11:34 AM
  • I had an interesting situation regarding this.  I have multiple CAS servers in different AD sites and I was unable to login to the 2013 ECP site where my Mailbox was migrated to.  After logging into ECP on another 2013 CAS server in a different AD site, I clicked on the CAS server as the same site as my mailbox, then selected the virtual directories and then selected OWA.  I noticed that ever though this was a 2013 CAS Role Server the Outlook Web App Version was showing Exchanage2010. 

    I then selected the 2013 CAS server and selected the reset option.  Once the reset option completed I updated the authentication method.  I did this to both OWA and the ECP virtual directories that were located in the site I was unable to access.  Once the reset was complete, I was able to connect to the ECP as well as OWA.

    Cheers

    Thursday, April 4, 2013 11:48 AM
  • Sorry I borrowed this thread!

    I solved it! It was a wierd url issue.

    https://mail.contoso.se/ecp FBA then HTTP 400

    https://mail.contoso.se/ecp?ExchClientVer=15 FBA then HTTP 400

    https://mail.contoso.se/ecp/ FBA then EAC, Working!

    /MrT


    Mr Tbone


    I too can confirm that the / at the end is a workaround for the issue. However, it is not a fix.
    Monday, May 27, 2013 2:41 PM