Please Try Again in 15 Minutes 132

Problem

You lot've just completed installing Exchange Server 2019 into an existing organisation and then proceed to create mailbox databases on the servers only find that y'all receive the following error when you attempt to browse the mailbox databases:

fault

Your request couldn't be completed. Please attempt again in a few minutes.

Continuing to click effectually would display the following symptoms:

The correct hand pane volition display the Delight look… message, which will never complete:

The following error would likewise be displayed at times:

500

Unexpected Error :(

An error occurred and your request couldn't be completed. Please try once more.

Browsing the event logs may does not reveal whatsoever useful errors such as the one below (this lead me down an unrelated path of checking attributes which did non 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 so I opened a call with Microsoft support. The engineer did not announced to take seen this before so she spent 2 full hours making changes to my account such equally adding it to the Exchange Servers and Exchange Trusted Subsystem Groups (I questioned why these groups with computer accounts are even relevant), granting various accounts Total Control in the security tab of my account, request to modify the Default Domain Policy setting Manage auditing and security logs to include the Exchange computer object groups (I had to stop her equally 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 memory (argued with her that information technology was recommended, not required), and all sorts of actions I felt were not relevant.

Long story brusk, how she ended upward 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 Commutation 2019 server. After moving the mailbox over and waiting for Agile Directory to replicate, the mailbox databases displayed properly. It was a frustrating 2 hours just I'thousand glad she was able to get to the bottom of this and I hope she'll write a KB nigh this and so all the previous actions she made aren't replicated with other engineers considering anyone who has worked with Exchange for many years would go just as annoyed equally I was.

Update – March 15, 2019

I started noticing the EAC / ECP displaying the same fault at various times throughout the twenty-four hour period even though my mailbox was moved over to the new server merely what appears to consistently piece of work is what a Hyili pointed out in this post:

Commutation 2019 - Consequence with EAC (ECP) - error - your request couldn't be completed. Delight effort again in a few minutes
https://social.technet.microsoft.com/Forums/office/en-US/68a9d447-df76-4d2a-bddc-6ead33a6c044/substitution-2019-issue-with-eac-ecp-error-your-request-couldnt-be-completed-please-try-again?forum=Exch2019

I just institute the solution to solve my problem. That is because the incorrect ExchClientVer is used by EAC. EAC used to take ExchClientVer=15 in Exchange 2013, merely information technology is currently using ExchClientVer=xv.2 in Exchange 2019.

A quick solution is that we tin can just appending "ExchClientVer=15.2" straight 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=xv.2". In my case, everything looks FINE.

According to some manufactures about 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=15. So everything we need is to move our admin mailbox to the server with Exchange 2019. Just like terenceluk0925 take tried.

But unfortunately, moving the admin mailbox to the newer server did not piece of work for me... I currently utilise the first tricky 1.

I gave the URL format: https://<exchange_server_domain>/ecp/?ExchClientVer=xv.ii

… and go by navigating directly onto the server and using: https://localhost/ecp/?ExchClientVer=15.2 and tin can confirm that this workaround does indeed correct the issue.

hartsellmorsitens.blogspot.com

Source: https://terenceluk.blogspot.com/2019/03/attempting-to-click-on-exchange-2019.html

Share this post