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

Similar Messages

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

ECP redirect to OWA after server migration

I have an odd problem with my Exchange 2013 environment after a migration (moving of a server).
My Exchange environment is as follows:
2 x CAS/MBX servers (physical machines)
1 x CAS server (virtual machine used for internal ECP access only)
All machines were in the same site
We have two sites and we wanted the virtual CAS server to be moved to our datacentre as part of a DR strategy (it will have the MBX role installed eventually, but initially it will remain a CAS).
So I powered down the virtual machine, cloned it and moved the clone to the datacenter (all using VMWare). Brought it back up and re-addressed the network card with the correct IP for the new network it is now in.
I ran tests such as accessing the ECP both from within the datacenter and from our primary site and I was able to access the ECP without issue and create mailboxes etc. However this morning when I came in and attempted to access the ECP with my admin account
that has always previously worked I am now being redirected to OWA???
I cannot think of a reason as to why this would be happening.
Is anyone able to offer an advice?
Kind regards

Hi George,
Agree with Sathish. Please use the following URL from Exchange CAS server and check the result.
https://localhost/ecp/?ExchClientVer=15
Here is a thread for your reference.
ECP redirects to OWA in Exchange 2013
http://social.technet.microsoft.com/Forums/en-US/34ed5347-90f9-4ab7-91c3-9665f8ace432/ecp-redirects-to-owa-in-exchange-2013?forum=exchangesvradminlegacy
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

ECP redirects to OWA in Exchange 2013

When logging into ECP 2013, the Exchange Admin Center login does not come up. A Windows Security login window comes up instead and it takes me into Outlook Web
App.
What am I missing?
July 2, 2014 Update. This has been resolved via reinstall. Thank you everyone to assist with this issue.

Have a look here:
http://technet.microsoft.com/en-us/library/jj150562.aspx
"If you’re in a coexistence scenario, where you’re running Exchange 2010 and Exchange 2013 in the same organization, and your mailbox is still housed on the Exchange 2010 Mailbox server, the browser will default to the Exchange 2010 ECP. You can access
the EAC by adding the Exchange version to the URL. For example, to access the EAC whose virtual directory is hosted on the Client Access server CAS15-NA, use the following URL:
https://CAS15-NA/ecp?ExchClientVer=15. Conversely, if you want to access the Exchange 2010 ECP and your mailbox resides on an Exchange 2013 Mailbox server, use the following URL:
https://CAS14-NA/ecp?ExchClientVer=14."
Try the URL modification:
https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15
It will show up as OWA authentication but after you provide credentials it will redirect back to EAC.
Flame to MS guys: this modification does not harm the scenario when you do not have the exchange 2010 or 2007 coexistance. Why could not you set the param by default when accessing Exchange 2013 CAS ECP application? Why make all those who attempt
to migrate from older exchange versions (2007 and 2010) stumble upon this problem? Shame on you.
Regards,
Eugene
I added the user to groups and that didnt work. But https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15
as suggested in above posted worked for me. (make sure you log out 1st and then try it)

Exchange 2013 CU2 to CU3 OWA now redirects to IIS page

so i did the the update from Exchange 2013 CU2 to CU3 last night and i am unable to access OWA. when i go to the site i initially received a 403 forbidden error but i cleared out the require SSL, which somehow got re-enabled, and now it redirects to the
IIS 8 page.
In IIS it seems like the redirect values for default web site got cleared away. I put in the address that was previously there and then e-mail for the whole company goes down after an IIS reset. In the default web site i entered to redirect to https://mail.contoso.com/owa
like how it was before but that doesn't work.
any ideas/feedback would be great!
Thanks!

I guess you are running a multirole server.
Did you try removing the OWA virtual directories - for both Default Website and Exchange Back End site with:
#Replace ServerName
Remove-OwaVirtualDirectory "ServerName\owa (Default Web Site)"
Remove-OwaVirtualDirectory "ServerName\owa (exchange back end)"
and re-creating them again with:
#Replace ServerName & mail.domain.com
New-OwaVirtualDirectory -InternalUrl "https://ServerName/owa" -ExternalUrl "https://mail. domain.com/owa"
New-OwaVirtualDirectory -InternalUrl "https://ServerName/owa" -ExternalUrl "https://mail. domain.com/owa" -WebSiteName "Exchange Back End"

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 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 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 CU2, Alert for OWA Health set unhealthy from SCOM 2012

I am facing issue in Exchange 2013 CU2, I got this alert from SCOM 2012 atleast 5-6 times a day, OWA health set is unhealthy, I have done all the steps mentioned in this web link. Authentication type for OWA Virtual directory is integrated windows and Basic.
I have 2 CAS servers, and this alert generated from both of them.
http://technet.microsoft.com/en-us/library/ms.exch.scom.OWA(EXCHG.150).aspx?v=15.0.712.24
Alert: Health Set unhealthy
Source: EX-CAS - OWA
Path: EX-CAS;EX-CAS
Last modified by: System
Last modified time: 1/5/2014 8:15:08 PM
Alert description: Outlook Web Access logon is failing on ClientAccess server EX-CAS.
Availability has dropped to 0%. You can find protocol level traces for the failures on C:\Program Files\Microsoft\Exchange Server\V15\Logging\Monitoring\OWA\ClientAccessProbe.
Incident start time: 1/6/2014 4:05:08 AM
Last failed result:
Failing Component - Owa
Failure Reason - CafeFailure
Exception:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
Failure source: Owa
Failure reason: CafeFailure
Failing component:Owa
Exception hint: CafeErrorPage: CafeFailure Unauthorized Inner exception: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
WebExceptionStatus: Success
GET https://localhost/owa/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
Accept: */*
Cache-Control: no-cache
X-OWA-ActionName: Monitoring
Cookie:
HTTP/1.1 401 Unauthorized
request-id: 211474d2-a43e-4fab-8038-3aab35353568
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
X-Powered-By: ASP.NET
X-FEServer: EX-CAS
Date: Mon, 06 Jan 2014 04:14:47 GMT
Content-Length: 0
Response time: 0s
---> Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
WebExceptionStatus: Success
GET https://localhost/owa/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
Accept: */*
Cache-Control: no-cache
X-OWA-ActionName: Monitoring
Cookie:
HTTP/1.1 401 Unauthorized
request-id: 211474d2-a43e-4fab-8038-3aab35353568
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
X-Powered-By: ASP.NET
X-FEServer: EX-CAS
Date: Mon, 06 Jan 2014 04:14:47 GMT
Content-Length: 0
Response time: 0s
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Net.MonitoringWebClient.BaseExceptionAnalyzer.Analyze(TestId currentTestStep, HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, Action`1 trackingDelegate)
   at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.AnalyzeResponse[T](HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
   at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndSend[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse, Boolean fireResponseReceivedEvent)
   at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndGet[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
   at Microsoft.Exchange.Net.MonitoringWebClient.Authenticate.AuthenticationResponseReceived(IAsyncResult result)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
   at Microsoft.Exchange.Net.MonitoringWebClient.Owa.OwaLogin.AuthenticationCompleted(IAsyncResult result)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Bool
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'EX-CAS' -HealthSet 'OWA'
State
Name
TargetResource                     HealthSet
AlertValue     ServerComponent
NotApplicable       OwaCtpMonitor
OWA
Unhealthy      None
States of all health sets:
Note: Data may be stale. To get current data, run: Get-HealthReport -Identity 'EX-CAS'
State
HealthSet
AlertValue     LastTransitionTime
MonitorCount
NotApplicable       ActiveSync
Healthy        1/3/2014 5:21:13 AM
2
NotApplicable       AD
Healthy        11/24/2013 6:54:18 AM
10
NotApplicable       ECP
Healthy        1/5/2014 3:03:05 AM
1
Online
Autodiscover.Proxy
Healthy        11/20/2013 10:06:37 AM
1
NotApplicable       Autodiscover
Healthy        1/3/2014 10:18:17 PM
2
Online
ActiveSync.Proxy
Healthy        11/20/2013 10:06:37 AM
1
Online
ECP.Proxy
    Healthy
11/21/2013 6:16:08 PM    4
Online
EWS.Proxy
Healthy        11/20/2013 10:06:37 AM
1
Online
OutlookMapi.Proxy
Healthy        11/24/2013 6:54:28 AM
4
Online
OAB.Proxy
Healthy        11/19/2013 7:14:34 PM
1
Online
OWA.Proxy
Healthy        11/20/2013 10:06:37 AM
2
NotApplicable       EDS
Healthy        1/3/2014 5:19:56 AM
10
Online
RPS.Proxy
Healthy        1/3/2014 5:21:27 AM
13
Online
RWS.Proxy                     Healthy
1/3/2014 5:20:09 AM      10
Online
Outlook.Proxy
Healthy        1/3/2014 5:21:12 AM
4
NotApplicable       EWS
Healthy        1/3/2014 10:18:17 PM
2
Online
FrontendTransport
Healthy        1/5/2014 3:47:09 AM
11
Online
HubTransport
Healthy        1/5/2014 3:47:09 AM
29
NotApplicable       Monitoring
Unhealthy      1/5/2014 4:05:57 AM
9
NotApplicable       DataProtection
Healthy        1/3/2014 5:25:42 AM
1
NotApplicable       Network                       Healthy
1/4/2014 1:51:16 PM      1
NotApplicable       OWA
Unhealthy      1/5/2014 8:05:08 PM
1
NotApplicable       FIPS
Healthy        1/3/2014 5:21:12 AM
3
Online
Transport
Healthy        1/5/2014 4:11:00 AM
9
NotApplicable       RPS
Healthy        11/20/2013 10:07:12 AM
2
NotApplicable       Compliance
Healthy        11/20/2013 10:08:10 AM
2
NotApplicable       Outlook
Healthy        11/21/2013 6:12:54 PM
2
Online
UM.CallRouter
Healthy        1/5/2014 3:47:10 AM
7
NotApplicable       UserThrottling
Healthy        1/5/2014 4:16:42 AM
7
NotApplicable       Search
                Healthy
11/24/2013 6:55:06 AM    9
NotApplicable       AntiSpam
Healthy        1/3/2014 5:16:43 AM
3
NotApplicable       Security
Healthy        1/3/2014 5:19:28 AM
3
NotApplicable       IMAP.Protocol
Healthy        1/3/2014 5:21:14 AM
3
NotApplicable       Datamining
Healthy        1/3/2014 5:18:34 AM
3
NotApplicable       Provisioning
Healthy        1/3/2014 5:19:56 AM
3
NotApplicable       POP.Protocol
Healthy        1/3/2014 5:20:44 AM
3
NotApplicable       Outlook.Protocol
Healthy        1/3/2014 5:19:46 AM
3
NotApplicable       ProcessIsolation
Healthy        1/3/2014 5:19:26 AM
9
NotApplicable       Store
Healthy       1/3/2014 5:20:38 AM
6
NotApplicable       TransportSync
Healthy        11/24/2013 6:53:09 AM
3
NotApplicable       MailboxTransport
Healthy        1/3/2014 5:21:11 AM
6
NotApplicable       EventAssistants
Healthy        11/21/2013 6:22:01 PM
2
NotApplicable       MRS
Healthy        1/3/2014 5:20:29 AM
3
NotApplicable       MessageTracing
Healthy        1/3/2014 5:18:15 AM
3
NotApplicable       CentralAdmin
Healthy        1/3/2014 5:17:25 AM
3
NotApplicable       UM.Protocol
Healthy        1/3/2014 5:17:08 AM
3
NotApplicable       Autodiscover.Protocol
Healthy        1/3/2014 5:17:13 AM
3
NotApplicable       OAB
Healthy        1/3/2014 5:20:51 AM
3
NotApplicable       OWA.Protocol
Healthy        1/3/2014 5:20:52 AM
3
NotApplicable       Calendaring
Healthy        11/24/2013 6:56:59 AM
3
NotApplicable       PushNotifications.Protocol
Healthy        11/21/2013 6:16:05 PM
3
NotApplicable       EWS.Protocol
Healthy        1/3/2014 5:19:07 AM
3
NotApplicable       ActiveSync.Protocol
         Healthy
1/3/2014 5:20:16 AM      3
NotApplicable       RemoteMonitoring
Healthy        1/5/2014 3:47:09 AM
3
Any solution for this alert, how to rectify it, but OWA is running perfect for all users.

Hi,
Sorry for the late reply.
Do we have Exchange 2010 coexistence?
If it is the case, I know the following known issue:
Release Notes for Exchange 2013
http://technet.microsoft.com/en-us/library/jj150489%28v=exchg.150%29.aspx
Please note the "Exchange 2010 coexistence" session.
If it is not related to our problem, please check the IIS log.
If there is any detailed error code, like 401.1, 401.2, please let me know.
Hope it is helpful
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange 2013 "Server Error in '/owa' Application" - System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1

Out of nowhere...literally this started happening to our standalone Exchange server / Domain Controller
Operating System: Microsoft Windows Server 2012 Standard
Problem Child: Microsoft Exchange Server 2013
Error: When i try to login to the OWA or ECP i receive the listed errors above.
OS and Exchange installed on C:\
Mailbox Databases installed on D:\
Mailbox Logs on E:\
Outlook is still working for the end-user, but Outlook Web Access, ECP and all other features required to make this server manageable are failing. I can access the login screen, though at:
https://<servername>/owa
or
https://<servername>/ecp
I have tried reset of virtual directories. Tried IISRESET /NOFORCE after this, but no success.

Hi MRXennix,
Base on my research, the issue is caused by corrupted Killbit.xml file on "ClientAccess\owa\15.0.xxx.x\owa2\ext\killbit".
I recommend you refer to the following method to solved the issue:
1. Remove the Killbit.xml file and restart IIS
2. Install the latest CU builds of the exchange 2013.
Best regards,
Niko Cheng
TechNet Community Support

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/

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

Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them.
With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
Questions are, Is this the right way to migrate all the users to Exchange 2013?
Will it affect the operation of existing Exchange 2007 server?

Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
2013 for standardization.
Refer article for configuring URLs -
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Sarvesh Goel - Enterprise Messaging Administrator

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.

Exchange 2013 ECP 500 Error

We are in the beginning phase of migrating from Exchange 2010 to Exchange 2013. When I login to the exchange 2013 admin console and navigate to servers it does not show me any of my servers. When I navigate to mailflow-receive connectors I receive a 500
error. When I run the powershell command to get-receiveconnectors it shows me the correct exchange 2013 connectors. I checked IIS and the permissions appear to be correct. Not sure where to look to resolve the issue.

Hi,
From your description, I would like to verify if you can see all the Exchange servers when running the Get-ExchangeServer cmdlet. If yes, the issue should be ECP virtual directory, you can remove this problematic ECP virtual directory and create a new
ECP virtual directory to check the result.
For your reference:
New-EcpVirtualDirectory
https://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx
Hope this 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 2013 ECP redirects to OWA

Similar Messages

Maybe you are looking for