Hi.

I have been restoring the entire Windows after a bigger problem in the past. However, there were data for Exchange server at a completely different disk which was not affected.

But now I can not load up OWA and when you look in the ECP so says the following under databases "Content index state: Failed"

I have tried to repair it but without any success.

The operation couldn't be performed because object '0747478411\MAIL-SERVER01' couldn't be found on 'server'.
    + CategoryInfo          : NotSpecified: (:) [Update-MailboxDatabaseCopy], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : DD4CF704,Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateDatabaseCopy

    + PSComputerName        : mail-server01

Update-MailboxDatabaseCopy "0747478411\MAIL-SERVER01" -CatalogOnly

All i have in owa now is

something went wrong Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.

How did you perform the task "restoring the entire Windows"?

I had to take an image of a disk and restore this. This is a virutel server.

In the case of non-DAG configuration:

* http://blogs.technet.com/b/exchangesearch/archive/2013/10/28/rebuild-an-index-on-exchange-2013-for-specific-databases.aspx

• Manual rebuild kickoff
1. Stop the Microsoft Exchange Search service as
   well as the Microsoft Exchange Host Controller.
2. Delete the Existing CI catalog folder or move it
   to a new location.
3. Start the Microsoft Exchange Search service as
   well as the Microsoft Exchange Host Controller services.

*

"Update-MailboxDatabaseCopy -CatalogOnly" is applicable for DAG-configurations.

Hi Jesper,

Thank you for your question.

By my understanding, we should not simply recover window system, we should performance a disaster recover for Exchange by the following link:

https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

You can fix the content index by:

• Stop the Exchange search indexer service.
• Delete the content index files (the GUID directory where the mailbox database EDB file is).
• Start the search indexer service.

I have tried this but with no success. It created a new catalog, but OWA and Outlook remains unreachable :(

I provided that as an answer to part of your question.  The search index doesn't have any effect on client connectivity.

I recommend you open a new thread with a post on your client connectivity problem and leave the search index out of it.