Google Login an Error Occurred Please Try Again in Few Minutes
Trouble
You've just completed installing Commutation Server 2019 into an existing arrangement then proceed to create mailbox databases on the servers simply notice that you receive the following mistake when you endeavour to browse the mailbox databases:
error
Your request couldn't be completed. Please try again in a few minutes.
Standing to click around would display the post-obit symptoms:
The right hand pane will display the Please look… bulletin, which will never consummate:
The following error would also be displayed at times:
500
Unexpected Error :(
An mistake occurred and your request couldn't be completed. Please try over again.
Browsing the event logs may does not reveal any useful errors such as the one below (this lead me down an unrelated path of checking attributes which did not contribute to the error):
The MaxActiveDatabases attribute on the Information Shop object in Active Directory has not been configured.
Solution
I spent a whole evening troubleshooting this issue without getting closer to the solution and then I opened a call with Microsoft support. The engineer did not announced to have seen this earlier then she spent 2 total hours making changes to my account such equally calculation information technology to the Exchange Servers and Substitution Trusted Subsystem Groups (I questioned why these groups with computer accounts are even relevant), granting diverse accounts Full Command in the security tab of my account, asking to modify the Default Domain Policy setting Manage auditing and security logs to include the Exchange reckoner object groups (I had to stop her as I told her this would overwrite all of the computer objects in the directory), telling me I did not configure the Exchange server with 128GB of retentivity (argued with her that it was recommended, not required), and all sorts of actions I felt were not relevant.
Long story curt, how she ended up getting to the resolution was something I can't believe I did not try, and that is to move my admin mailbox to a mailbox database on the Substitution 2019 server. Later moving the mailbox over and waiting for Active Directory to replicate, the mailbox databases displayed properly. It was a frustrating 2 hours but I'm glad she was able to go to the bottom of this and I hope she'll write a KB about this so all the previous actions she made aren't replicated with other engineers because anyone who has worked with Exchange for many years would become just as annoyed as I was.
Update – March 15, 2019
I started noticing the EAC / ECP displaying the same error at various times throughout the day fifty-fifty though my mailbox was moved over to the new server but what appears to consistently work is what a Hyili pointed out in this post:
Exchange 2019 - Issue with EAC (ECP) - mistake - your asking couldn't be completed. Please try again in a few minutes
https://social.technet.microsoft.com/Forums/office/en-The states/68a9d447-df76-4d2a-bddc-6ead33a6c044/exchange-2019-issue-with-eac-ecp-error-your-request-couldnt-be-completed-please-try-again?forum=Exch2019
I just found the solution to solve my problem. That is because the wrong ExchClientVer is used past EAC. EAC used to have ExchClientVer=xv in Exchange 2013, but it is currently using ExchClientVer=15.2 in Substitution 2019.
A quick solution is that we tin can just appending "ExchClientVer=15.2" directly to the EAC URL parameter. For example, the original url might be "https://<exchange_server_domain>/ecp/". Subsequently modification, new URL would be "https://<exchange_server_domain>/ecp/?ExchClientVer=15.2". In my example, everything looks FINE.
Co-ordinate to some articles near ExchClientVer, seems like it is decided by the location server of the admin mailbox. If the admin mailbox is located on the server with Exchange 2013, EAC would use ExchClientVer=fifteen. And so everything we demand is to motility our admin mailbox to the server with Exchange 2019. Just similar terenceluk0925 accept tried.
Simply unfortunately, moving the admin mailbox to the newer server did not work for me... I currently use the first tricky ane.
I gave the URL format: https://<exchange_server_domain>/ecp/?ExchClientVer=15.2
… and become by navigating directly onto the server and using: https://localhost/ecp/?ExchClientVer=15.2 and can confirm that this workaround does indeed correct the outcome.
Source: https://terenceluk.blogspot.com/2019/03/attempting-to-click-on-exchange-2019.html
0 Response to "Google Login an Error Occurred Please Try Again in Few Minutes"
Post a Comment