SOLVED

Exchange 2016 on prem - ECP redirects to OWA

%3CLINGO-SUB%20id%3D%22lingo-sub-1519631%22%20slang%3D%22en-US%22%3EExchange%202016%20on%20prem%20-%20ECP%20redirects%20to%20OWA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1519631%22%20slang%3D%22en-US%22%3E%3CP%3EI%20did%20search%20and%20found%20similar%20topics%20and%20tried%20the%20suggestions%20but%20no%20cigar.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EI%20should%20say%20this%20server%20is%20supposed%20to%20be%20a%20management%20server%20to%20all%20our%20mailboxes%20which%20are%20in%20Exchange%20Online.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20this%3A%3C%2FP%3E%3CP%3E%5BPS%5D%20C%3A%5CWindows%5Csystem32%26gt%3BGet-ExchangeServer%20fmdex7%20%7CGet-owaVirtualDirectory%20%7C%20fl%20identity%2C%20name%2C%20*URL*%2C%20*auth*%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIdentity%20%3A%20FMDEX7%5Cowa%20(Default%20Web%20Site)%3CBR%20%2F%3EName%20%3A%20owa%20(Default%20Web%20Site)%3CBR%20%2F%3EUrl%20%3A%20%7B%7D%3CBR%20%2F%3EInternalSPMySiteHostURL%20%3A%3CBR%20%2F%3EExternalSPMySiteHostURL%20%3A%3CBR%20%2F%3ESetPhotoURL%20%3A%3CBR%20%2F%3EExchange2003Url%20%3A%3CBR%20%2F%3EFailbackUrl%20%3A%3CBR%20%2F%3EInternalUrl%20%3A%20%3CA%20href%3D%22https%3A%2F%2Ffmdex7.ad.fasken.fmd%2Fowa%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Ffmdex7.ad.fasken.fmd%2Fowa%3C%2FA%3E%3CBR%20%2F%3EExternalUrl%20%3A%3CBR%20%2F%3EClientAuthCleanupLevel%20%3A%20High%3CBR%20%2F%3EInternalAuthenticationMethods%20%3A%20%7BBasic%2C%20Fba%7D%3CBR%20%2F%3EBasicAuthentication%20%3A%20True%3CBR%20%2F%3EWindowsAuthentication%20%3A%20False%3CBR%20%2F%3EDigestAuthentication%20%3A%20False%3CBR%20%2F%3EFormsAuthentication%20%3A%20True%3CBR%20%2F%3ELiveIdAuthentication%20%3A%20False%3CBR%20%2F%3EAdfsAuthentication%20%3A%20False%3CBR%20%2F%3EOAuthAuthentication%20%3A%20False%3CBR%20%2F%3EExternalAuthenticationMethods%20%3A%20%7BFba%7D%3C%2FP%3E%3CP%3Exxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%3C%2FP%3E%3CP%3E%5BPS%5D%20C%3A%5CWindows%5Csystem32%26gt%3BGet-ExchangeServer%20fmdex7%20%7CGet-EcpVirtualDirectory%20%7C%20fl%20identity%2C%20name%2C%20*URL*%2C%20*auth*%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIdentity%20%3A%20FMDEX7%5Cecp%20(Default%20Web%20Site)%3CBR%20%2F%3EName%20%3A%20ecp%20(Default%20Web%20Site)%3CBR%20%2F%3EInternalUrl%20%3A%20%3CA%20href%3D%22https%3A%2F%2Ffmdex7.ad.fasken.fmd%2Fecp%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Ffmdex7.ad.fasken.fmd%2Fecp%3C%2FA%3E%3CBR%20%2F%3EExternalUrl%20%3A%3CBR%20%2F%3EInternalAuthenticationMethods%20%3A%20%7BBasic%2C%20Fba%7D%3CBR%20%2F%3EBasicAuthentication%20%3A%20True%3CBR%20%2F%3EWindowsAuthentication%20%3A%20False%3CBR%20%2F%3EDigestAuthentication%20%3A%20False%3CBR%20%2F%3EFormsAuthentication%20%3A%20True%3CBR%20%2F%3ELiveIdAuthentication%20%3A%20False%3CBR%20%2F%3EAdfsAuthentication%20%3A%20False%3CBR%20%2F%3EOAuthAuthentication%20%3A%20False%3CBR%20%2F%3EExternalAuthenticationMethods%20%3A%20%7BFba%7D%3C%2FP%3E%3CP%3Exxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20still%20when%20I%20try%20to%20login%20to%20ECP%20it%20sends%20me%20to%20OWA.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ffmdex7%2Fowa%2Fauth%2Flogon.aspx%3FreplaceCurrent%3D1%26amp%3Breason%3D3%26amp%3Burl%3Dhttps%253a%252f%252ffmdex7%252fecp%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Ffmdex7%2Fowa%2Fauth%2Flogon.aspx%3FreplaceCurrent%3D1%26amp%3Breason%3D3%26amp%3Burl%3Dhttps%253a%252f%252ffmdex7%252fecp%3C%2FA%3E%3C%2FP%3E%3CDIV%20class%3D%22errorHeader%22%3E%3A(%3C%2Fimg%3E%3C%2FDIV%3E%3CDIV%20class%3D%22errorSubHeader%22%3ESomething%20went%20wrong%3C%2FDIV%3E%3CDIV%20class%3D%22errorSubHeader2%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22errorDetails%22%3EA%20mailbox%20couldn't%20be%20found%20for%20FASKEN_AD%5CLIOIOPA.%3C%2FDIV%3E%3CPRE%3EX-ClientId%3A%20D255F24E6E3C4530BF51F66DC4E0D330%0Arequest-id%20c025a24c-554c-4d7f-90f6-251127b5bef8%0AX-OWA-Error%20Microsoft.Exchange.Data.Storage.UserHasNoMailboxException%0AX-OWA-Version%2015.1.1913.5%0AX-FEServer%20FMDEX7%0AX-BEServer%20FMDEX7%0ADate%3A7%2F13%2F2020%204%3A45%3A25%20PM%3C%2FPRE%3E%3CP%3EAppreciate%20any%20help%20I%20can%20get!%3C%2FP%3E%3CP%3ECheers%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1519631%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1520329%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20on%20prem%20-%20ECP%20redirects%20to%20OWA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1520329%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F725006%22%20target%3D%22_blank%22%3E%40OzzLioi%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3EIt%20is%20surely%20a%20re-direction%20settings%20take%20effect%20somewhere.%20Check%20your%20antispam%2C%20relay%20software%20or%20firewall%20etc.%20It%20can%20be%20at%20the%20IIS%20too%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1521062%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20on%20prem%20-%20ECP%20redirects%20to%20OWA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1521062%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F669559%22%20target%3D%22_blank%22%3E%40manuphilip%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20reply%2C%20It%20has%20to%20be%20IIS%20as%20this%20also%20happens%20on%20the%20server%20itself.%3CBR%20%2F%3EI%20built%20this%20server%20and%20got%20it%20to%20work%20temporarily%20then%20something%20happened%20that%20caused%20the%20redirect.%3CBR%20%2F%3EI%20tried%20many%20things%20I%20found%20online%20and%20no%20change.%3CBR%20%2F%3EI%20removed%20the%20server%20cleaned%20up%20with%20ADSIEDIT%20and%20reinstalled%20OS%20and%20then%20Exchange...%3CBR%20%2F%3EA%20very%20difficult%20install%20even%20for%20Exchange%20which%20is%20normally%20a%20detailed%20and%20difficult%20install.%3CBR%20%2F%3EAfter%20eliminating%20all%20the%20prereqs%2C%20and%20completing%20the%20install%2C%20I%20wound%20up%20in%20the%20same%20place%2C%20with%20the%20same%20redirect.%3CBR%20%2F%3EIf%20nothing%20else%20comes%20up%20my%20next%20step%20is%20calling%20Microsoft%20support%20again!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1521992%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20on%20prem%20-%20ECP%20redirects%20to%20OWA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1521992%22%20slang%3D%22en-US%22%3E%3CP%3EThanks!%3CBR%20%2F%3EI%20was%20able%20to%20get%20that%20sorted%20out%20by%20going%20to%20IIS%20and%20checking%20all%20the%20Exchange%20Back%20End%20HTTP%20Redirect%2C%20and%20found%20some%20were%20check%20marked%20with%20redirect%20requests%20to%20OWA.%3C%2FP%3E%3CP%3ENo%20idea%20why.%3C%2FP%3E%3CP%3ERemoved%20the%20check%20marks%20after%20clearing%20the%20URL%20in%20the%20destination%20field%20and%20I%20am%20able%20to%20login%20to%20EAC.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1522014%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20on%20prem%20-%20ECP%20redirects%20to%20OWA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1522014%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F725006%22%20target%3D%22_blank%22%3E%40OzzLioi%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGood%20to%20hear%20that%20the%20issue%20has%20been%20resolved.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EPlease%20mark%20as%20**%22Accept%20the%20answer%22**%20if%20my%20comment%20helped%20you.%20Your%20suggestion%20will%20help%20others%20also%20!%3C%2FP%3E%3CP%3ERegards%2C%3CBR%20%2F%3EManu%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1828897%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20on%20prem%20-%20ECP%20redirects%20to%20OWA%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1828897%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20the%20redirect%20issue%2C%20it%E2%80%99s%20recommended%20to%20refer%20to%20the%20workaround%20in%20below%20KB%3A%20Exchange%20Server%202013%20or%20Exchange%20Server%202016%20redirects%20to%20Exchange%202010%20for%20OWA%2C%20Outlook%20on%20the%20Web%2C%20and%20ECP%3C%2FP%3E%3CP%3EIn%20addition%2C%20here's%20a%20article%20to%20get%20in%20detailed%20about%20Client%20Connectivity%20in%20an%20Exchange%202010%20and%20Exchange%202016%20coexistence%2C%20for%20your%20reference%3A%20Client%20Connectivity%20in%20an%20Exchange%202016%20Coexistence%20Environment%20with%20Exchange%202010.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I did search and found similar topics and tried the suggestions but no cigar.

I should say this server is supposed to be a management server to all our mailboxes which are in Exchange Online.

 

I have this:

[PS] C:\Windows\system32>Get-ExchangeServer fmdex7 |Get-owaVirtualDirectory | fl identity, name, *URL*, *auth*


Identity : FMDEX7\owa (Default Web Site)
Name : owa (Default Web Site)
Url : {}
InternalSPMySiteHostURL :
ExternalSPMySiteHostURL :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl : https://fmdex7.ad.fasken.fmd/owa
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

[PS] C:\Windows\system32>Get-ExchangeServer fmdex7 |Get-EcpVirtualDirectory | fl identity, name, *URL*, *auth*


Identity : FMDEX7\ecp (Default Web Site)
Name : ecp (Default Web Site)
InternalUrl : https://fmdex7.ad.fasken.fmd/ecp
ExternalUrl :
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

 

But still when I try to login to ECP it sends me to OWA.

https://fmdex7/owa/auth/logon.aspx?replaceCurrent=1&reason=3&url=https%3a%2f%2ffmdex7%2fecp

:(
Something went wrong
 
A mailbox couldn't be found for FASKEN_AD\LIOIOPA.
X-ClientId: D255F24E6E3C4530BF51F66DC4E0D330
request-id c025a24c-554c-4d7f-90f6-251127b5bef8
X-OWA-Error Microsoft.Exchange.Data.Storage.UserHasNoMailboxException
X-OWA-Version 15.1.1913.5
X-FEServer FMDEX7
X-BEServer FMDEX7
Date:7/13/2020 4:45:25 PM

Appreciate any help I can get!

Cheers,

 

5 Replies

Hi @OzzLioi ,

It is surely a re-direction settings take effect somewhere. Check your antispam, relay software or firewall etc. It can be at the IIS too

@manuphilip 

Thanks for the reply, It has to be IIS as this also happens on the server itself.
I built this server and got it to work temporarily then something happened that caused the redirect.
I tried many things I found online and no change.
I removed the server cleaned up with ADSIEDIT and reinstalled OS and then Exchange...
A very difficult install even for Exchange which is normally a detailed and difficult install.
After eliminating all the prereqs, and completing the install, I wound up in the same place, with the same redirect.
If nothing else comes up my next step is calling Microsoft support again!

Best Response confirmed by OzzLioi (New Contributor)
Solution

Thanks!
I was able to get that sorted out by going to IIS and checking all the Exchange Back End HTTP Redirect, and found some were check marked with redirect requests to OWA.

No idea why.

Removed the check marks after clearing the URL in the destination field and I am able to login to EAC.

 

Hi @OzzLioi ,

 

Good to hear that the issue has been resolved. 


Please mark as **"Accept the answer"** if my comment helped you. Your suggestion will help others also !

Regards,
Manu

For the redirect issue, it’s recommended to refer to the workaround in below KB: Exchange Server 2013 or Exchange Server 2016 redirects to Exchange 2010 for OWA, Outlook on the Web, and ECP

In addition, here's a article to get in detailed about Client Connectivity in an Exchange 2010 and Exchange 2016 coexistence, for your reference: Client Connectivity in an Exchange 2016 Coexistence Environment with Exchange 2010.