I was setting up a new cluster this week.
I am not a technical writer so I won’t go into all the screen shots and steps up to the point of failure. If you want more details, just leave a comment, or send me a message.
It is an Exchange 2007 Cluster Continuos Replication (CCR) with a Majority Node Set (MNS) Quorum. This will be the second Exchange cluster in our Exchange Organization, and we plan to move everything off out Exchange 2003 cluster and retire it.
At some point, don’t ask me when, something got messed up and I had to uninstall Exchange and the Microsoft Cluster Server (MSCS) and start over. This is where all the fun started.
The MSCS portion would complete wonderfully and I had no problems. I could install the Exchange 2007 management tools and the Mailbox Role without problems as well. As soon as I tried to install the Active Clustered Mailbox Server it would just choke. I searched high and low for a solution and could not find one. I tried all the normal trouble shooting items to no avail.
Here is the command I was running to install:
Setup.com /m:install /roles:mailbox /newcms /cmsname:EXCH07MBX1 /cmsipaddress:192.168.11.108 /CMSDataPath:E:\Exchange\Mailbox
Here is the error I was getting:
Storage group “EXCH07MBX1\First Storage Group” was not found. Please make sure you have typed it correctly.
Long story short this site led me to solving the problem — ExchangeInbox.com
I had been making sure the database and log files were deleted when I uninstalled Exchange and started over, but did not bother checking the registry.
HKEY_Local_Machine\SOFTWARE\Microsoft\Exchange
The information does not get deleted automatically. The keys related to the clustering, if they exist, prevent the CLUSTER_SERVER.INS from being processed. This is the part that sets up the cluster resources, which includes the First and Second Storage Groups.
Everything is up and running now and I thank God for leading me to that page.
If any one is getting the error mentioned above, and you to not see the Resource Group in the cluster management console named after your Active CMS, give it a shot, after you have backed up your registry, delete the Exchange key shown above. It worked like a champ for me.
This solution worked for me, your mileage may vary. Doing the things mentioned here could render your Exchange server unusable. This server was in the process of being set up and was not yet in production and the prospect of wiping these machines to bare metal and starting over from a fresh format of the drives would not pose any production downtime. Proceed at your own risk, I am not responsible for your actions, or inaction, as the case may be with taking the appropriate backups.