HRESULT:80070005 in ECP after install KB5023697 (windows server 2016)

Ardan Zaki 236 Reputation points

Hi, I just installed the latest CU for windows server 2016 (KB5023697) on my exchange server. But after I installed the CU. I cannot access the server through ECP external URL.

Screenshot 2023-03-31 142308

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,099 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,379 questions
{count} votes

Accepted answer
  1. Aholic Liang-MSFT 13,821 Reputation points Microsoft Vendor

    Hi @ Ardan Zaki 

    I have resolved the issue

    Great to know that you've already got of a solution and really appreciate it for your sharing!

    By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others.". and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:

    [HRESULT:80070005 in ECP after install KB5023697 (windows server 2016)]

    Issue Symptom:

    After installing the latest CU for Windows Server 2016 (KB5023697) on the Exchange server,  cannot access the server through the ECP external URL.

    The solution:

    1.Check that TLS 1.2 is enabled on all servers, and disable TLS 1.0 and 1.1 .
    2.Check whether the certificate binding in IIS is correct and check the authentication of each site.

      You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Aholic Liang-MSFT 13,821 Reputation points Microsoft Vendor

    Hi Ardan Zaki ,

    Sorry for the late reply, I tested as follows:

    1.Deploy three Windows Server 2016 and install two Exchange Server 2016 CU23(16A/16B) in a test environment.

    2.Use 16A and 16B to open DNS lookups on both servers, and the operation is successful. 3.Install Windows Update (KB5023697) in 16B and restart the server.

    4.Open the DNS lookups of the two servers with 16A and 16B respectively again, and the operation is successful.

    And I did a related search for this issue and there is no article stating that this KB has this known issue.

    For further troubleshooting, I would like to confirm the following with you:

    1.Have there been any recent changes to the permissions on the AD side?

    2.Whether running the following command in EMS gives any results:

    get-TransportService -Identity "16A" |fl

    In addition, we recommend that you try creating a new administrator account to see if you can open this page.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our [documentation ] ( enable e-mail notifications if you want to receive the related email notification for this thread.