Cannot Login To Exchange 2013 ECP After New Install
If you have just installed Exchange 2013 on Server 2012, one of the first things you will do is try and log-in into the now ECP to start configuring Exchange 2013. I cam across an iss that when you try to log into the ECP you get the error below.
——————————————————————————–
The Active Directory user wasn’t found.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Exchange.Data.Storage.ObjectNotFoundException: The Active Directory user wasn’t found.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[ObjectNotFoundException: The Active Directory user wasn’t found.]
Microsoft.Exchange.Clients.Owa2.Server.Core.OwaIdentity.CreateExchangePrincipal() +1118
Microsoft.Exchange.Clients.Owa2.Server.Core.UserContext.Load(OwaIdentity logonIdentity, OwaIdentity mailboxIdentity) +590
Microsoft.Exchange.Clients.Owa2.Server.Core.UserContextManager.CreateUserContext(HttpContext httpContext, UserContextKey userContextKey, ClientSecurityContext overrideClientSecurityContext, UserContext& userContext) +776
Microsoft.Exchange.Clients.Owa2.Server.Core.UserContextManager.AquireUserContext(HttpContext httpContext, ClientSecurityContext overrideClientSecurityContext) +229
Microsoft.Exchange.Clients.Owa2.Server.Core.UserContextManager.GetUserContext(HttpContext httpContext, Boolean create) +118
Microsoft.Exchange.Clients.Owa2.Server.Core.RequestDispatcher.InternalDispatchRequest(RequestContext requestContext) +587
Microsoft.Exchange.Clients.Owa2.Server.Core.RequestDispatcher.DispatchRequest(RequestContext requestContext) +297
Microsoft.Exchange.Clients.Owa2.Server.Core.OwaRequestHandler.OnPostAuthorizeRequest(Object sender, EventArgs e) +352
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165——————————————————————————–
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929
After some digging around I worked out that this issue is because the administrator account that you are logging in as did not have a mailbox created and attached to it as it should during the Exchange 2013 installation. To fix this issue we run the commands below to create a mailbox for the administrator.
enable-mailbox -identity administrator
OR the account you were trying to log into the ECP/EAC as.
Then confirm in Active Directory that the account that yuo have attached the mailbox to is a member of the Exchange Organization Managment group.
You may need to reboot the server for these changes to take place, this wil resolve the issueo of not being able to log into the Exchange 2013 EAC.
Tags: ECP
Loading ...
Florian Just
| #
Hi there from Germany,
thanks for these needful Help.
Some additional to your Post:
I made a new Server 2012R2 Std and get over the old AD/DC from a W2K3. There was also an Exchange 2003 on it. So there are some problems when i also install the Exchange 2013 (i know, it is not recommended) on the new 12R2. So i erased with adsi some CNs from the AD. After that the install runs, but i have these creepy issiue, that you describe here.
But oh dear, if i hit the Exchange PS, it speak to me, that my Administrator has allready an mailbox. After installing the CU3, the Problem was the same but in an different look. It tells me in nice blue with a smilie that my Mailbox ist not there for the Admin…
so i droped the old mailbox in the Exchange PS with:
disable-mailbox
-identity administrator
and then i create it new with enable-mailbox
After that i could log on instead on the ECP
So, best regards, thanks for this little help.
Reply
Luis
| #
Thanks for this post, and thanks Florian for the followup; I had the exact same issue, and disable-mailbox then enable-mailbox worked great!!!
Reply
Leslie
| #
You guys rock!!!!! days of pain and no solution.
Followed your brilliant advice and big smiles!!!! Thank you so so much. I hope you get to read this and know how you have helped someone , somehow, somewhere!!!
Reply