DiscoverySearchMailbox has been corrupted and it is in an inconsistent state

DiscoverSearchMailbox {Guid} has been corrupted and it is in an inconsistent state. The following validation errors have occurred:

Warning:
The value of the property ‘RecipientTypeDetails’,536870912, is not defined in the Enum type ‘RecipientTypeDetails’.

==========================================

We will see the above two warnings while we plan for Migration from Exchange Server 2007 SP3 RU10 to Exchange Server 2013. This is a Common warning and it appears while opening EMC as shown  below.

Figure 1: Warning Message
Warning while opening EMC in 2007 server.

Figure 2: Warnings
No action is required since the mailbox is of higher version and the warning can be safely ignored.

Figure 3: Mailbox Details in 2013 EMS

In figure 3 the Mailbox is accessible and it is able to perform Discovery Search from Exchange Server 2013 for 2013 Mailboxes.

Conclusion : The above warnings can be safely ignored.

==========================================

Note:-

In my experience , I have seen that this issue occurs a clobber reinstallation where the administrator has manually removed the mail databases and the binary files. post which a ndw mbx server is clobbered on . This error happens because the homemdb attribute is not set on the mailbox.
This issue can be resolved by adding a DN of a mailbox on the homeMdb attribute. restart the msexchangeis service on the homemdb filed in adsiedit > domain> users > discovertsearchXXX.XXXX…..rt click on it . on the home mdb tab , you might get anSID value instead of the new mailboxes.
Change the homeMdb attribute to the DN of any active mailbox. restart the IS service.

Worst case scenario you might or reboot the server . ideally this should resolve the issue .

RCA tool .This generally happens when ,lets say 2ek10 is installed on top of the legacy mailbox server , in the org and the customer has done a manual uninstall all of exchange and has forgotten to mention the DN of the discoverysearchmailbox > please try to check the homeMDB attribute.If its a points to a SID, for the database.

Ideally it should show the DN of the any of the mailbox database..

restart the msexchangeIS svc and try to check if the discovery search mailbox shows up or not.

It should ideally work , but as an extreme alternative , delete the existing discoverysearchmailbox and run a setup.com /ps && setup.com /p ,

How to Move Exchange Server 2007 from Windows Server 2008 SP2 to Windows Server 2008 R2 SP1

In this Blog post we will be exploring on how to move Exchange Server 2007 from Windows Server 2008 SP2 to Windows Server 2008 R2 SP1.

Note : This scenario may or may not work for you. Please perform a thorough test before implementing it into production environment.

Below are some of the few points which will help us to understand when and why this scenario will help us.

• Windows Server 2008 SP2 had some performance issues.
• Company had planned to Upgrade from Windows Server 2008 to 2008 R2.
• Existing Server had a blue screen of death. Non reliable.
• Server is completely compromised due to Virus.
• Server crashed due to power outage..etc. etc..

===============================================

Permission Prerequisites

The account should be a member of Domain Admins and Enterprise Admins Groups. Full Exchange Administrators permission.

===============================================

Data Prerequisites

Full Exchange Database Backup is mandatory. If not, then blank database can be mounted, however no old emails will be accessible.

===============================================

Scenario

Exchange Server : Exchange Server 2007 SP3 (MBX)

Windows Server 2008 SP2 which will be replaced with Windows Server 2008 R2 SP1

Domain Name : MSEXCHANGETEAM.IN

DC Name : DC1

===============================================

How to check the previous version and SP using Active Directory Users and Computers.

Figure 1.1 : Server Properties

Using ADUC we can easily understand what operating system the server was running before crashing or replacing. This will help us to plan whether we will bring the same operating system or different.

Figure 1.2 ; Using ADSIEDIT.msc. Connecting to Domain Partition and the properties of server object.

Figure 1.3 : Exchange Server Version.

In figure 1.3 the Exchange Server version will remain same.

Figure 1.4 : Number of Test Users.

Figure 1.5 : Test Emails Before moving to 2008 R2

===============================================

So far we have checked basic requirements. We also have proper exchange database for recovery. Now its time to recover the server as follows.

Login to domain controller and open Active Directory Users and Computers > Navigate to the Computer Object and right click > Select Reset Account as shown below.

Figure 1.6 : Reset Account

Figure 1.7 : Account Reset successfully

Now join the server to Domain. The server is now Windows Server 2008 R2 SP1.

Figure 1.8 : Post joining the Server the Properties have changed.

In figure 1.8  we can now see that the operating system has changed.

Install Exchange Server 2007 Prerequisites by running the following command.

ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-ISAPI-Ext
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Digest-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Web-Dyn-Compression
ServerManagerCmd -i RPC-Over-HTTP-Proxy

===============================================

Reboot the server post installing the above features.

Its time to run Recover Server with Exchange Server 2007 SP3 media as follows.

Figure 1.9 : Recover Server Completed

In figure 1.9 we have used /DoNotStarTransport. This is to avoid failure of recovery process. Once recovery is finished start the service manually.

Figure 1.10 : This database can be overwritten by a restore

In figure 1.10 post recover server go to the properties of database and select the above option to restore the database.

Figure 1.11 : Database path

By looking at figure 1.11 ensure that Exact set of folders are created and the database is restored to its location. By default recover server would not create this folders.

Figure 1.12 : Database Health check

Post restoring the database health check is mandatory before bringing the database into production.

Figure 1.13 : Mount database

Now since we have confirmed database location and database health. Its safe to go ahead and “Mount Database”

Figure 1.14 : Mounted

Figure 1.15 : Mailboxes as seen before recovery

Figure 1.16 : Same Exchange Server Recovered

Figure 1.17 : OWA Test

Figure 1.18 : User able to login

Figure 1.19 : I am Back….

Exchange Server is back on a brand new operating system Windows Server 2008 R2. No settings have been modified.

This article illustrates as to what “Recover Server” can do. There are many scenario under which recover server can be performed.

===============================================

H

Recovering a Failed CCR Passive Node in Exchange Server 2007

Although Exchange Server 2007 is pretty old now and on top of that recovering failed CCR Passive Node is also quite familiar. However the idea behind sharing the steps is to help people who are having confusion between Setup.com /recoverserver and Setup.com /recoverCMS.

Short Story
Unfortunately I got the opportunity while working on a different issue and in the course of troubleshooting Passive Node crashed and there is no way we can bring it back (Hardware failure).

I was working on Exchange Server 2007 SP1 RU10 (Not supported scenario). But there is no option rather getting the server back online.

Mandatory Requisites Checks

Step 1) Check Active Node and make a note of Hardware and Software already installed.
Step 2) Get the IP address for both Public and Private Network.
How to Get the network address
Open Failover Cluster Manager from active node and make a note of the Failed Machine Name and IP address.
Step 3) Ensure that new hardware is similar.

Offline prerequisites checks finished.

How to Add the Node Back

Step 1) Open Failover Cluster Manager from the Active Node. Evict the Failed Node. This will permanently remove the Failed node from cluster.
Step 2) Rename the new Computer Name with the Exact Name of the Crashed Node (Other names will also work)
Step 3) Assign both Private and Public Network address. Ensure that Public Network is on top. And also uncheck the option from Private network Advance option which says Register this connections addresses with DNS
Step 4) Login to any DC and Open Active Directory Users and Computers.
Step 5) Reset the Computer Account (Server Name)
Step 6) Add the machine to Domain.
Step 7) Login to the machine with same Administrator account which is used in Active node.
Step 8) Install Failover Cluster Manager Feature on the server.
Step 9) Open Failover Cluster Manager and add the Node.
Step 10) Install Exchange Server 2007 prerequisites.
Step 11) Install Exchange Server 2007 in GUI mode. And in the wizard select Custom and Select “Passive Clustered Mailbox Server”.
Step 12) Install RU if any as per the active node.
Step 13) Setup completed.
Step 14) Get the storage group copy status. Based on the status you can perform seeding from active node.
Step 15) Check failover and failback by moving the clustered mailbox server.

The above steps will work with Exchange Server 2007 SP1, Exchange Server 2007 SP2 and Exchange Server 2007 SP3.

I hope it was helpful.

Happy Recovery