ECP login gives error X-OWA-Error Microsoft.Exchange.Data.Storage.UserHasNoMailboxException

%3CLINGO-SUB%20id%3D%22lingo-sub-309390%22%20slang%3D%22en-US%22%3EECP%20login%20gives%20error%20X-OWA-Error%20Microsoft.Exchange.Data.Storage.UserHasNoMailboxException%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309390%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3EWe%20are%20in%20the%20process%20of%20replacing%20Exchange%202013%20servers%20with%20Exchange%202016.%20The%20Exchange%202013%20and%202016%20servers%20reside%20in%20different%20AD%20sites%20and%20all%20mailboxes%20(user%2Farbitration%2Fpublic-folder)%20are%20moved%20over%20to%20the%202016%20site%20and%20are%20accessible%20just%20fine.%20Exchange%20powershell%20administration%20also%20just%20works%20fine.%20Also%20when%20I%20logon%20to%20the%20desktop%20of%20the%20Exchange%202016%20server%20and%20open%20the%20https%3A%2F%2Flocalhost%2Fecp%20web%20console%20it%20works%20just%20fine%20and%20I%20use%20that%20admin%20console.%20However%2C%20when%20I%20try%20to%20open%20the%20ECP%20using%20the%20URL%20%3CA%20href%3D%22https%3A%2F%2Fwebmail.domain.com%2Fecp%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwebmail.domain.com%2Fecp%3C%2FA%3E%20it%20always%20fails%20with%20the%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3EX-ClientId%3A%2004463CD88C344F8E90C9CEF2B472E378%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3Erequest-id%20dc8f8f2a-3972-4ba6-a071-b72b6e9c9a09%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3EX-OWA-Error%20Microsoft.Exchange.Data.Storage.UserHasNoMailboxException%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3EX-OWA-Version%2015.1.1591.10%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3EX-FEServer%20SERVER1%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3EX-BEServer%20SERVER2%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3EDate%3A1%2F4%2F2019%201%3A03%3A37%20PM%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3EThe%20Admin%20accounts%20that%20we%20use%20don%E2%80%99t%20have%20a%20mailbox%20and%20never%20had%2C%20and%20this%20issue%20did%20not%20occur%20when%20we%20had%20just%20Exchange%202013%20servers.%20The%20Exchange%202016%20version%20is%20CU11.%20The%20Exchange%202013%20servers%20are%20not%20the%20latest%20CU%20but%20right%20now%20I%20don%3Bt%20have%20that%20detail%20with%20me.%20If%20it%20is%20important%20I%20will%20look%20it%20up.%20I%E2%80%99ll%20see%20if%20enabling%20a%20mailbox%20for%20my%20admin%20account%20helps%20but%20I%E2%80%99d%20rather%20be%20able%20to%20run%20the%20ECP%20without%20that%20just%20like%20it%20used%20to%20work.%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3EAny%20help%20to%20solve%20this%20is%20appreciated.%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3EThanks%2C%3C%2FP%3E%3CP%20class%3D%22x_MsoNormal%22%3EEric%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-309390%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-320747%22%20slang%3D%22en-US%22%3ERe%3A%20ECP%20login%20gives%20error%20X-OWA-Error%20Microsoft.Exchange.Data.Storage.UserHasNoMailboxException%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-320747%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20isue%20is%20solved%20now.%20It%20was%20caused%20by%20an%20invalid%20redirect%20behavior%20of%20the%20L7%20Azure%20Application%20Gateway%20that%20is%20configured%20in%20front%20of%20the%20CAS%20servers.%20The%20L7%20paths%20and%20default%20redirect%20rule%20is%20now%20reconfigured%20and%20%2Fecp%20is%20reachable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi all,

We are in the process of replacing Exchange 2013 servers with Exchange 2016. The Exchange 2013 and 2016 servers reside in different AD sites and all mailboxes (user/arbitration/public-folder) are moved over to the 2016 site and are accessible just fine. Exchange powershell administration also just works fine. Also when I logon to the desktop of the Exchange 2016 server and open the https://localhost/ecp web console it works just fine and I use that admin console. However, when I try to open the ECP using the URL https://webmail.domain.com/ecp it always fails with the error:

 

X-ClientId: 04463CD88C344F8E90C9CEF2B472E378

request-id dc8f8f2a-3972-4ba6-a071-b72b6e9c9a09

X-OWA-Error Microsoft.Exchange.Data.Storage.UserHasNoMailboxException

X-OWA-Version 15.1.1591.10

X-FEServer SERVER1

X-BEServer SERVER2

Date:1/4/2019 1:03:37 PM

 

The Admin accounts that we use don’t have a mailbox and never had, and this issue did not occur when we had just Exchange 2013 servers. The Exchange 2016 version is CU11. The Exchange 2013 servers are not the latest CU but right now I don;t have that detail with me. If it is important I will look it up. I’ll see if enabling a mailbox for my admin account helps but I’d rather be able to run the ECP without that just like it used to work.

 

Any help to solve this is appreciated.

 

Thanks,

Eric

1 Reply
Highlighted

This isue is solved now. It was caused by an invalid redirect behavior of the L7 Azure Application Gateway that is configured in front of the CAS servers. The L7 paths and default redirect rule is now reconfigured and /ecp is reachable.