asked on
Exchange 2016 EAC -- cannot handle the request error 500 for some admin accounts
some admin users cannot access exchange 2016 EAC (/ecp or /owa)
once logged in getting unable to handle the request error 500
it happens only for two admin accounts, also found that for them url /ecp redirects them to https://CAS/owa/auth.owa
once logged in getting unable to handle the request error 500
it happens only for two admin accounts, also found that for them url /ecp redirects them to https://CAS/owa/auth.owa
ExchangeEmail Servers
Last Comment
Michael B. Smith
do they have mailboxes? are permissions inheriting on their AD accounts?
ASKER
I am mot sure if they had mailbox and what was changed to them since it worked before.on my account there is a mailbox and it works for me. Not sure if its related.
About inheritance i dont know
About inheritance i dont know
Yep - its very likely to be inheritance.
Open AD, go to the affected user, Security | advanced - Click "enable inheritance" - ok - then accept the warning message.
Wait approx 15 mins after this has been completed - and try again.
Open AD, go to the affected user, Security | advanced - Click "enable inheritance" - ok - then accept the warning message.
Wait approx 15 mins after this has been completed - and try again.
ASKER
but what if it worked before?
ASKER
Inheritance didnt make any change
did you recently install a patch? the mailbox requirement is not supposed to be present, but it's been on-again/off-again ever since Exchange 2000 was released.
ASKER
Yes the latest april 2021 security patches
Do the account names have a $ in them?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
as i wrote before: the mailbox requirement is not supposed to be present, but it's been on-again/off-again ever since Exchange 2000 was released.