Error 500 when logging into ECP using Domain & Exchange Administrator account. OWA works fine.
I consistently get '500 Unexpected Error :(' when I log into the ECP as DOMAIN\Administrator account. If I then switch to OWA it loads and works perfectly fine. It is a completely fresh install (both server and exchange) so I have no configured
anything other than the default 'out of the box' settings.
Steps I have tried so far:
- Remove/Rebuild ECP VirtualDirectory
- Confirm RemoteDomains.xaml has both the correct file type and doesn't contain duplicate values.
- Delete the CanaryData using ADSIEdit, recycle OWA/ECP App Pools then Restart IIS
None of the above made a slight difference and anything I can find whilst searching is just a repeat of what I have already tried. Any help would be greatly appreciated.
-
Edited by
Wardy195
Friday, August 21, 2015 11:06 AM
Formatting
August 21st, 2015 11:04am
I can only assume it does, would the OWA login still work if I had no mailbox for that account?
Forgive me as I am a completely new to Exchange 2013 but how do I check if a mailbox is present?
The Mailbox and CAS are on the same machine.
August 24th, 2015 4:27am
I can only assume it does, would the OWA login still work if I had no mailbox for that account?
Forgive me as I am a completely new to Exchange 2013 but how do I check if a mailbox is present?
The Mailbox and CAS are on the same machine.
August 24th, 2015 4:27am
Hi Wardy,
I recommend you check if there is any corrupt health mailbox, it will cause the issue also.
Run the following command via Exchange management shell :
Get-Mailbox -Monitoring
If there is any corrupt health mailbox, you can
recreate it and log in ECP again.
Hope this helps,
Best regards,
August 24th, 2015 4:54am
Hi Wardy,
I recommend you check if there is any corrupt health mailbox, it will cause the issue also.
Run the following command via Exchange management shell :
Get-Mailbox -Monitoring
If there is any corrupt health mailbox, you can
recreate it and log in ECP again.
Hope this helps,
Best regards,
August 24th, 2015 4:54am
Hi Niko,
I have ran that command and got back the following:
Name
Alias ServerName
ProhibitS
----
----- ----------
---------
HealthMailbox9XXXXXX... HealthMailbox9XXX... SERVER NAME
Unlimited
HealthMailbox9XXXXXX... HealthMailbox9XXX... SERVER NAME
Unlimited
I assume all is well?
Thanks
August 24th, 2015 7:22am
Hi Niko,
I have ran that command and got back the following:
Name
Alias ServerName
ProhibitS
----
----- ----------
---------
HealthMailbox9XXXXXX... HealthMailbox9XXX... SERVER NAME
Unlimited
HealthMailbox9XXXXXX... HealthMailbox9XXX... SERVER NAME
Unlimited
I assume all is well?
Thanks
August 24th, 2015 7:22am
Hi the account you are using - is it member of any Exchange administrative groups? i.e. organisation management, recipient management etc.? Also try using Exchange Power Shell and see whether that connects or fails?
If it if fails - what errors do you get?
Thanks,
Abhi
August 24th, 2015 9:28am
Hi the account you are using - is it member of any Exchange administrative groups? i.e. organisation management, recipient management etc.? Also try using Exchange Power Shell and see whether that connects or fails?
If it if fails - what errors do you get?
Thanks,
Abhi
August 24th, 2015 9:28am
Hi, the only Exchange group the account is part of is Organisation Management. Other than that it is the Domain admin account so has the usual groups you would expect.
The only error message I get is the 500 - Unexpected Error. I can see no other messages at any point. I have previously used The Exchange Management Shell to rebuild virtual directories and other things so I can connect to that perfectly fine.
-
Edited by
Wardy195
17 hours 17 minutes ago
Additional details
August 24th, 2015 9:54am
Hi, the only Exchange group the account is part of is Organisation Management. Other than that it is the Domain admin account so has the usual groups you would expect.
The only error message I get is the 500 - Unexpected Error. I can see no other messages at any point. I have previously used The Exchange Management Shell to rebuild virtual directories and other things so I can connect to that perfectly fine.
-
Edited by
Wardy195
17 hours 17 minutes ago
Additional details
August 24th, 2015 9:54am
If you have just one Exchange 2013 server:
Get-Mailbox -Server SERVER_NAME
August 24th, 2015 12:06pm
If you have just one Exchange 2013 server:
Get-Mailbox -Server SERVER_NAME
August 24th, 2015 12:06pm