none
Exchange 2013 ECP error RRS feed

  • Question

  • Hi,

    I just installed Exchange 2013  on Server 2012 Std. in a test environment.  When I try to launch ECP, it comes up with HTTP Error 404.0 - Not Found message.  I'm using https://server_name/ecp to access it.

    The details of erro are as following:

    Detailed Error Information:

    Module    IIS Web Core
    Notification    MapRequestHandler
    Handler    StaticFile
    Error Code    0x80070002
    Requested URL    https://192.168.0.99:443/ecp/
    Physical Path    C:\inetpub\wwwroot\ecp\
    Logon Method    Anonymous

    Logon User

       Anonymous

     I've verified the path to 'ECP' in IIS Manager.  It is pointing to where 'ecp' folder is installed:

    C:\Program Files\Microsoft\Exchange Server\ClientAccess\ecp

    I don't understand why the error message is showing the path to be in C:\Inetpub\wwwroot\ecp

    Can anyone please shed some light as to how I can resolve this issue.

    Any help will be greatly appreciated.

    Best regards,

    Parm :)


    Parmjit Singh BR Systems

    Friday, February 1, 2013 6:14 PM

Answers

  • Just found the problem.......

    I had initially installed Exchange 2013 with just the Mailbox role.  I had omitted to install the Client Access Role.

    Once the Client Access Role was installed all worked as it should.

    • Proposed as answer by Rwaggers Sunday, February 24, 2013 9:19 AM
    • Marked as answer by BR Systems Sunday, February 24, 2013 6:03 PM
    Sunday, February 24, 2013 9:18 AM
  • Unbelievable that They would not install the Client Access Role. Installed the Clinet access Role fixed my issue.
    • Marked as answer by BR Systems Monday, April 8, 2013 12:34 AM
    Monday, April 8, 2013 12:09 AM

All replies

  • Did you tried the full FQDN? Like https://server.domain.com/ecp 


    Gulab Prasad,
    gulab@exchangeranger.com
    My Blog | Z-Hire Employee Provisioning App

    Monday, February 4, 2013 6:34 AM
  • Hello,

    From your description, I suggest you follow these steps to test for the issue:

    <1> Use "https://localhost/ecp" (on CAS server)to have a try.

    <2> Go to IIS and browse to see whether it can work or not.

    Thanks,

    Evan Liu

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tnmff@microsoft.com


    Evan Liu
    TechNet Community Support

    Monday, February 4, 2013 8:02 AM
    Moderator
  • Thank you, Gulab.

    Yes, I have and had no luck.

    Best regards,

    Parm :)


    Parmjit Singh BR Systems

    Monday, February 4, 2013 5:07 PM
  • Thanks foryuor response, Evan.

    I've tried the https://localhost/ecp without any luck.

    I'm not sure about 'Step 2' - can you please elaborate for me?

    Thanks a bunch.

    Parm :)


    Parmjit Singh BR Systems

    Monday, February 4, 2013 5:09 PM
  • Do you see anything failed in Exchange Setup Log?

    Post the end Entry from Exchange Setup where setup is completing. Anything in App log?

    Is it happening with all the users?
    I would suggest delete and create new VD for ECP and OWA and check the issue.


    Gulab Prasad,
    gulab@exchangeranger.com
    My Blog | Z-Hire Employee Provisioning App

    Monday, February 4, 2013 6:49 PM
  • Hello Gulab,

    Thanks a lot for your efforts.

    I checked the Exchange Setup log file.  There were some warnings and some SharedAccess service related errors.  I've pasted just a few of them as examples below.  I hope it's okay.:

    [WARNING] 'FMS' did not exist, this is not an error as the sevice might have just been installed
    [01-24-2013 04:39:34.0100] [2] [ServiceControl.ps1] Enabling service 'hostcontrollerservice'.
    [01-24-2013 04:39:34.0100] [2] [WARNING] 'hostcontrollerservice' did not exist, this is not an error as the sevice might have just been installed
    [01-24-2013 04:39:34.0100] [2] [ServiceControl.ps1] Enabling service 'IISAdmin'.
    [01-24-2013 04:39:34.0100] [2] [WARNING] 'IISAdmin' did not exist, this is not an error as the sevice might have just been installed
    [01-24-2013 04:39:34.0100] [2] [ServiceControl.ps1] Enabling service 'MSExchangeADTopology'.
    [01-24-2013 04:39:34.0115] [2] [WARNING] 'MSExchangeADTopology' did not exist, this is not an error as the sevice might have just been installed

    *(Following are the warnings while the setup was starting all the services at the end)*

    [01-24-2013 04:47:00.0280] [2] Active Directory session settings for 'start-SetupService' are: View Entire Forest: 'True', Configuration Domain Controller: 'Server2012STD.brsystems.local', Preferred Global Catalog: 'Server2012STD.brsystems.local', Preferred Domain Controllers: '{ Server2012STD.brsystems.local }'
    [01-24-2013 04:47:00.0280] [2] Beginning processing start-setupservice -ServiceName:'SharedAccess' -ErrorVariable:'script:serviceControlError' -IgnoreTimeout:'True'
    [01-24-2013 04:47:00.0280] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
    [01-24-2013 04:47:00.0280] [2] Previous service status query time is '2013-01-23 9:47:00 PM'.
    [01-24-2013 04:47:00.0280] [2] Current service status query time is '2013-01-23 9:47:00 PM'.
    [01-24-2013 04:47:00.0280] [2] Will wait '2000' milliseconds for the service 'Netman' to reach status 'Running'.
    [01-24-2013 04:47:00.0545] [2] Service 'Netman' successfully reached status 'Running on this server while waiting for status change.
    [01-24-2013 04:47:00.0545] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
    Below is at the end of setup:

    [01-24-2013 04:47:01.0715] [1] The previous errors were generated by a non-critical task and will be ignored.
    [01-24-2013 04:47:01.0715] [1] Setup will continue processing component tasks...
    [01-24-2013 04:47:01.0715] [1] Finished executing component tasks.
    [01-24-2013 04:47:01.0731] [1] Ending processing Start-PostSetup
    [01-24-2013 04:47:02.0012] [0] Finished loading screen SetupCompletedPage.
    [01-24-2013 05:53:17.0810] [0] End of Setup
    [01-24-2013 05:53:17.0810] [0] **********************************************

    App log: No errors except occasional warnings re MSExchange Mid-Tier Storage (Event ID: 10010)  THere are also informational events regarding the same (Event ID 9000).

    I'm not sure about your question re other users.  I'm not able to get to the site at all.

    I have tried deleting and recreating VD without any success.

    I hope I've addressed all of your questions.

    One thing that boggles my mind is why it's looking at 'C:\inetpub\wwwroot\ecp' for physical path (as shown in the original post) when the actual path as per settings for ECP is 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\ecp'?

    Thank you once again for your efforts.

    Best regards,

    Parm :)


    Parmjit Singh BR Systems

    Tuesday, February 5, 2013 2:54 AM
  • Saturday, February 16, 2013 12:32 AM
  • I've just been playing with my test server and found that https://servername:444/ecp/ works, well sort of!

    This gets me to OWA - for the life of me I'm unable to get to the ECP itself.

    Friday, February 22, 2013 3:43 PM
  • Just found the problem.......

    I had initially installed Exchange 2013 with just the Mailbox role.  I had omitted to install the Client Access Role.

    Once the Client Access Role was installed all worked as it should.

    • Proposed as answer by Rwaggers Sunday, February 24, 2013 9:19 AM
    • Marked as answer by BR Systems Sunday, February 24, 2013 6:03 PM
    Sunday, February 24, 2013 9:18 AM
  • Yes, the Client Access Role installation took care of the problem. Thank you. Parm ;)

    Parmjit Singh BR Systems

    • Proposed as answer by Woodster74 Monday, April 8, 2013 12:07 AM
    Sunday, February 24, 2013 6:07 PM
  • Please try this:

    https://%computername%/ecp/?ExchClientVer=15

    Like this, I can access now ECP.

    Thanks!


    Patrick Gerber

    Sunday, March 3, 2013 11:25 PM
  • Unbelievable that They would not install the Client Access Role. Installed the Clinet access Role fixed my issue.
    • Marked as answer by BR Systems Monday, April 8, 2013 12:34 AM
    Monday, April 8, 2013 12:09 AM
  • Quick question please folks. What led to the thought that the CAS role was not required? Just curious....

    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.

    Monday, May 6, 2013 1:03 PM
  • Well, CAS is not selected/offered as part of the default installation options. Also, in my mind CAS is for client access not for management.

    Thank you.  :)


    Parmjit Singh BR Systems

    Monday, May 6, 2013 4:39 PM
  • Well, CAS is not selected/offered as part of the default installation options. Also, in my mind CAS is for client access not for management.

    Thank you.  :)


    Parmjit Singh BR Systems

    I concur with Parmjit - I always tend to do my first install using the defaults.

    Richard Wagstaff

    Tuesday, May 7, 2013 12:58 PM
  • Check http://www.howexchangeworks.com/2013/05/eac-access-while-co-existing-exchange-2013-with-2010.html to avoid any surprises if you are co-existing.

    CAS and Mailbox is needed for a full 2013 deployment.


    Rajith Enchiparambil | http://www.howexchangeworks.com |

    HowExchangeWorks.Com

    Wednesday, May 8, 2013 11:22 AM
  • I'd make the language even clearer than that Raj.

    CAS is needed for *ANY* 2013 deployment, and right from the start.


    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.

    Wednesday, May 8, 2013 11:46 AM
  • The option to install the Client Access was greyed out until after the install of the mailbox role.

    This allowed me to run \ecp\ now as well.

    Sunday, November 30, 2014 4:42 AM