Share via

"This service is no longer available" error when deleting messages in OWA

Aleksandr Alekseev 16 Reputation points
2023-01-17T16:21:35.5266667+00:00

Hello,

For a few days users with mailboxes on Exchange Server 2010 in a network with Exchange 2016 are reporting errors when attempting to move or delete messages while in OWA. The error reads: "This service is not available". OWA is proxied by the Exchange 2016 server. What I noticed is that, when you use direct Exchange 2010 URL for OWA, deleting messages works fine. The error is fired whenever users access OWA externally via the Exchange 2016 OWA proxy.

Coincidence or not, this started happening after Exchange 2016 had the CU23 installed last weekend.

There don't appear to be Google search results concerning this issue. Could it be something new in the wild?

Anyone has any ideas how to troubleshoot?

Thank you

Alex

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,197 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,503 questions
Microsoft Exchange
Microsoft Exchange
Microsoft messaging and collaboration software.
461 questions

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amit Singh 4,956 Reputation points
    2023-01-18T06:12:48.9066667+00:00

    Please use the below command to check the authentication methods you have configured for EWS.

    Get-WebServicesVirtualDirectory | fl *auth*

    According to the error message, we can try to recreate EWS and OWA virtual directories to test.

    In addition, I have found a similar thread for your reference: https://social.technet.microsoft.com/Forums/exchange/en-US/1c5758d8-bf2c-4b24-8959-1bdcb9734b75/owa-2010-unable-to-delete-emails?forum=exchange2010

  2. Jame Xu-MSFT 4,176 Reputation points
    2023-01-18T07:02:51.14+00:00

    Hi @Aleksandr Alekseev ,

    You could check the proxy settings after the update, and also check your virtual directory configuration. Here is a similar case you may refer to: https://www.reddit.com/r/exchangeserver/comments/10dawma/exchange_owa_cannot_delete_items/

    Microsoft provides third-party contact information to help you find additional information about this topic. This contact information may change without notice. Microsoft does not guarantee the accuracy of third-party contact information.

    If an Answer is helpful, please click "Accept Answer" and upvote it.

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

  3. Jakub Podsiadło 0 Reputation points
    2023-02-22T08:46:59.87+00:00

    Exactly the same case. I have verified the suggestions described above.

    • TLS 1.2 is enabled.
    • SSL Binding on 127.0.0.1, with valid certificate on Default Web Site

    There are no errors in HTTPProxy logs on Exchange 2016

    There are no errors in the IIS logs on Exchange 2010

    Interestingly, I can delete and move messages in OWA Lite.

    0 comments
  4. Aleksandr Alekseev 16 Reputation points
    2023-05-29T05:57:36.8433333+00:00

    This issue is still at large. Wondering if anyone managed to find a workaround aside from accessing internal URLs of 2010 servers directly via their local FQDN, bypassing the 2016 OWA Proxy?

    In our organization we are still far from moving every mailbox over to the 2016 server although this is the ultimate goal. The fix is required as an interim solution.

    Thank you !

    0 comments
  5. ZacZG 1 Reputation point
    2024-01-04T13:28:59.4233333+00:00

    Hi, I have the same error with a fresh installation of exchange 2016 in coexistence with exchange 2010. Everything works fine except for deleting the e-mails of users who are still on the 2010 version, and the invalid canary error appears in ecp access? When accessing OWA 2010 directly without a proxy, everything works normally. The problem occurs only when the user accesses from the proxy Exchange 2016 to 2010? Has anyone found a solution in the meantime?

    0 comments