Exchange 2016 cu 19 failing because OWA (Exchange Back End) couldn't be found - ON WRONG SERVER

Natalie Bennett 96 Reputation points
2021-03-09T03:20:04.63+00:00

Trying to install CU 19, and getting [ERROR] The operation couldn't be performed because object 'XXX\OWA (Exchange Back End)' couldn't be found on 'YYY.ZZZ.local' YYY is the domain controller, and XXX is the Exchange server. I have no idea why it is looking for the OWA (Exchange Back End) directory on the domain controller. It is definitely on the Exchange server. this server is down until I can fix this, or restore from backup, and lose a day.

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,345 questions
0 comments
Accepted answer
  1. Natalie Bennett 96 Reputation points
    2021-03-09T16:58:12.757+00:00

    I fixed the problem myself - went into ADSIEdit, and realized the entry for "owa (Exchange Back End)" was missing entirely. Not sure how that happened, since this was a working server in production. I created it from scratch, setting most of the attributes I could based on a working server (another client) and the settings that were in this server for owa (Default Web Site). If anyone is having the same problem, the location is CN=owa (Exchange Back End),CN=HTTP,CN=Protocols,CN=SERVER,CN=Servers,CN=Admin Group Name, CN=Administrative Groups,CNDOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com or local, or whatever.

    Before I did this, I tried the /prepareAD switch, but didn't do the terms acceptance, so maybe that and prepareschema would have worked Not sure. The OWA virtual directory did exist, but recreating wouldn't have worked, since the CU19 install failed at a point that rendered the Exchange Management Shell not working.

    Still having some problems with EAC and http 404 errors after login, and I've recreated the directories, and reset the authentication to Windows, which is supposed to be the fix, but so far no dice. I will figure that out. The main thing is that email is flowing again!

    0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ashok M 6,506 Reputation points
    2021-03-09T08:16:04.32+00:00

    Hi @Natalie Bennett ,

    Exchange virtual directory information will be stored in AD.

    Any issues with AD replication or commuication issues between Exchange & AD?

    Is this is a new install or upgrade. Incase of upgrade from previous CU, based on the current CU, Exchange may need schema update, so try running the below commands before the CU install

    Setup /PrepareSchema /IAcceptExchangeServerLicenseTerms
    Setup /PrepareAD /IAcceptExchangeServerLicenseTerms

    Also, check if the OWA virtual directory exist in the Exchange server. If not try re-creating it once. If still errors occurs, please share the error message from Exchange setup log by covering personal information.

    https://theitbros.com/recreate-owa-ecp-virtual-directories-exchange-server-2016/

    If the above suggestion helps, please click on "Accept Answer" and upvote it.

    0 comments
  2. Chadd Blanchard 1 Reputation point
    2021-09-12T22:20:33.827+00:00

    Running into a similar issue installing Exchange 2016 CU21. The upgrade fails on the Client Access Front End Service.

    [Error] The operation couldn't be performed because object '[ExchangeServer]\owa (Default Web Site)' couldn't be found on '[DC].domain.com'.

    Our OWA isn't in the Default Web Site it's in a custom site. And it's not on the domain controller it's on the Exchange Server. The error makes it look like it's looking on a DC for it. ADSI lists the correct location for OWA in the custom site on the Exchange Server.

    Any ideas?

    0 comments
  3. Mark Watson 1 Reputation point
    2021-09-22T08:34:25.78+00:00

    Did you manage to fix this?