We have an Windows Server 2012 Exchange 2013 server with OWA. 

All users can login fine, but when I open another mailbox with my Admin account, having enabled access to that user's mailbox, the URL redirects to /owa/auth/errorfe.aspx?httpCode=500 and shows: 

:-( something went wrong Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk

Google won't help me in this instance. Where in the eventlog are OWA events logged?

• Edited by Thijs Hakkenberg Thursday, September 12, 2013 3:43 PM

Hi

How long are you waiting for replication to complete? Normally i wait about 15-30 min and then i can open the mailbox after that. If i try access a mailbox immediately i get the error above.

What do you mean by replication? I now waited more then an hour and still a 500 error.. 

AD replication.

How did you allow access to the mailbox?  When I allow a user access to a mailbox I add them into the Full access under mailbox delegation in the ECP or via powershell.

• Edited by BraVad0 Thursday, September 12, 2013 7:49 PM

In the ECP -> Edit user -> Mailbox delegation -> Full Access

@DareDevel57: But the delegation was set through the ECP, does it still need to replicate?

• Edited by Thijs Hakkenberg Friday, September 13, 2013 9:20 AM

Yeah, It still replicates those changes through Active Directory.

Hi,

From your posting, a httpcode 500 error occurs when logging in OWA and the URL redirects to owa/auth

Generally, the error was 500 which indicates some kind of authentication errors. To resolve the issue, please try the following checks:

1.  Checked IIS, ensure that all of the authentication is set correctly and "Require SSL" is checked on the root of the default website.

2.  Restart IIS service by running IISReset /NoForce.

3.  If it fails, please try to start the Microsoft Exchange Forms-Based Authentication service on Exchange server.

If all fails, please view Please collect related IIS logs or the OWA event logs which event ID is 4625 on the CAS server with detail logon failure information. You can post the details here and I would like to help you.

Thanks,

Winnie

• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Sunday, September 22, 2013 6:34 PM

Hello,

I am joining to the thread opener, however, we do not use exchange server. we are using the Cloud services through Microsoft and as far as I know, the version is 2013 wave 15 (again, through Microsoft's cloud).

when I open the outlook, I can see the shared mailbox just fine.

when I open the office web access, and I search the mailbox through the 'add another mailbox..' It finds it however when I press the add button I get the HTTP 500 error.

when I tried to open a different mailbox (another shared mailbox I gave myself permissions for), it opens just fine.

it seems (from what I can tell) it is this specific shared mailbox that I cannot open through OWA while others I can.

when I try to open the mailbox in question through a different internet browser (Chrome) I get this Error: NegotiateSecurityContext failed with for host 'db3pr04mb138.eurprd04.prod.outlook.com' with status'LogonDenied'

the error seems to be persistent on this specific mailbox only regardless to what browser I am trying to access with.

I can only assume that the solutions you (Winnie) offered isn't relevant in my case.

thanks in advance for any attempt to help me with this issue.

• Edited by Roy Bouhadana Sunday, October 06, 2013 7:16 AM typos

Hi,

Since the Exchange version is 2013 wave 15, the issue is related to Exchange Online and this forum focuses on Exchange Server 2013, I suggest we post the issue to the Exchange Online forums to get more professional answers.

Microsoft Online: Exchange Online Forums

http://social.technet.microsoft.com/Forums/en-US/home?forum=onlineservicesexchange

Hope we can find the solution soon.

Thanks,

Winnie

Thank you Winnie!

Thanks Winnie, restarting IIS is what did it for me. Though, it wouldn't take the /noforce parameter for some reason.

Hi

I'm running a new install on a windows 2012 R2 server. I have the same problem but its only the build in domain admin that gets the error 500 when he logs into owa or ecp. I can make a new admin and give him exchange right and he has no probelm at all login in. 

Running Exchange 2013 SP1, have redirect from http to https so I have turned off SSL on the root default domain site which is by MS the "correct" way of doing redirect from http to https. When I turn on the SSL and restart IIS the build in admin can login again.

This is really a weird problem and I cen't really see whats causing it

 in my case , I found exchange front end service is downshow start not  started , reboot  server everything is alright