Exchange Recover server fail need to reinstall fresh

Would it be worth just removing the Exchange 2013 entries in ADSI and reinstalling.  I know it is not supported by Microsoft but from the error above I cannot seem to find any other possibility.  Can someone at least help with what I should remove to force a new installation of Exchange and not have to do a recover.

This server has no physical use in current Exchange 2007 environment it is meant to be setup as Exchange 2013 on-premise Hybrid server so that we can maintain 2007 and move students from the school into Exchange online, but leave staff in 2007.

After rebuild of server and Recover Server I keep getting this error message:

Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
          new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController;
          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
        " was run: "The operation couldn't be performed because object 'EXCH-SRV-HYBRID\OWA (Exchange Back End)' couldn't be found on 'bhs-srv-acc-dc.balwynhs.vic.edu.au'.".
ITSystemSolAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ITSystemSolAuthor Commented:
The resolution involve removing the server from the schema and reinstalling it was the only way in the end.  It is not something that should be taken lightly and for that reason I am not going to put the steps on how to do this.  Seek advice from others on how to do it before attempting this.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
marpanetCommented:
I would like to contribute on this question... I got this error when I was updating my Exchange 2013 to the CU3, at first I was scared and Exchange will not complete the update and will not work, after some hours and one angry client, I manage to fix it and the update completed and everything when back to normal.

If you got here is because you are trying to delete and recreate the virtual directories and you get the error that they cannot be deleted because they does not exists, and you cannot recreate them because you get an error that they already exists.

I followed this post and manage to delete both entries and recreate the virtual directories, once they have been created, you can reinstall the update and no more errors during the update.

Post: https://exchangemaster.wordpress.com/category/iis/
Autor: Andrew S Higginbotham  (Thank you very much)
Tools used: https://www.microsoft.com/en-us/download/details.aspx?id=17275 

I am going to post the important things in this post just to have a backup of it.

The solution was to install the IIS 6 Resource Kit and use Metabase Explorer to delete the ghosted vDir. When installing the Resource Kit, select Custom Install and then uncheck all features except for Metabase Explorer 1.6 and proceed with the installation. Once it finishes, it may require you add the .NET Framework 3.5 Feature.
When you open the tool on the Exchange Server in question, navigate to the below tree structure and delete the old OWA Virtual Directory by right-clicking it and selecting Delete. When completed, the OWA vDir should no longer be present (see picture attached).

You should now be able to successfully execute the New-OwaVirtualDirectory Cmdlet. It’s always a bit nostalgic seeing a tool of days gone by still able to save the day. I’d like to thank my co-worker John Dixon for help with this post. When I can’t figure something out in Exchange/IIS (or anything really) he’s who I lean on for help.

Hope this helps someone.
4.png
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.