I don't normally post in these sort's of Forums for i feel like i'm still a newbie! but i had the EXACT same issue's as you where experiencing. and it's killing my desire for the product fast. Situation, and how long that will delay a solution to whatever problems may arise . I am afraid to know which parts of powershell I'll need to learn in an emergency I don't want to be forced to learn it in order to confidently run Exchange on our network. so I just get reds.Īnd a huge "BRAVO" to Microsoft for finally getting rid of the GUI in favor of powershell! Thank God! Really - it used to take me a week or two to figure out a new version of Exchange. my version of Exchange Powershell apparentlyĭoesn't come with this cmdlet (even after I run update). You can use the Get-EcpVirtualDirectory command to find the URL for your ECP site. I "sort of" solved the access to admin page problem with this URL: at least I got to the correct sign-in page. It automatically creates it in the default web Then recreate it, new-ecpvirtualdirectory, no switches on this one. If you copy and paste, check my spelling. Identity "yourservername\ecp (default web site)" (don't forget the quotes). On the Backend site, check the bindings and make sure it's port 444 is associated with your 3rd party certificate also with the correct names in it. Make sure it has your 3rd party certificate associated Also check the bindings of the default web site port 443. It should have SSL enabled, if not, you'll get the "page can't be found error". Once you are sure it points there,Ĭheck the security of the virtual directory. The "default web site" ecp virtual folder should point to, in my case, C:\Program Files\Microsoft\Exchange Server\v15\FrontEnd\HttpProxy\ecp". Something you might try if you haven't fixed it yet. I forgot to mention but the Backend site is the one that points to "C:\inetpub\wwwroot" You can do the OWA directory the same way. If it's okay and you still can't access it, remove it and recreate it. If that still doesn't work, drop to the Exchange Command Prompt and type get-ecpvirtualdirectory to check and make sure it's recognized and correct. Make sure it has your 3rd partyĬertificate associated with it. Points there, check the security of the virtual directory.
Source File: C:\inetpub\wwwroot\ecp\web.config Line: 32 This error can be caused by a virtual directory not being configured as an application in IIS. Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. Please review the specific error details below and modify your configuration file appropriately. Which seems to be valid, however it doesn't work.Īfter testing both of those VD's I noticed that like with ecp it all points to c:\inetpub\wwwroot\ecp,autodiscover,EWS,etc so I tried copying the HttpProxy folder for ecp into c:\inetpub\wwwroot\ and tested again and got the following rather than the 404ĭescription: An error occurred during the processing of a configuration file required to service this request. I have tried manually changing the IIS site (Exchange Back End) to point its physical path to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp The error page points the physical path to c:\inetpub\wwwroot\ecp however that folder does not exist. Unfortunately, as you can see in that thread, it is still unresolved.Ĭurrent Issue: trying to access (or any other variation) returns a 404 Not Found. I've searched every possible web guide/forum thread and the only one which is the same issue I'm having is this one:
Still, now I cannot figure out how to fix my next problem - Accessing the EAC/ECP.
Getting extremely frustrated now with a new Exchange 2013 installation on a Windows Server 2012 VM.Īfter having a lot of problems with the installation (didn't uninstall visual c++ which caused failure, then needed to delete the AD Microsoft Exchange System Objects group due to permission failures, etc) I've now got a fully installed Exchange