Solved

Exchange Install Mailbox Role Error

Posted on 2013-11-04
4
932 Views
Last Modified: 2014-01-27
I have a windows server 2012 machine. I am trying to integrate Exchange 2010 from scratch on a brand new Domain. This is the only server. The install gets all the way to the mailbox role and I get this error. I have ensured the TCP port sharing is automatic and running. And I even did a prepare schema and preparead and reran the install and I still get this error:

Mailbox Role
Failed

Error:
The following error was generated when "$error.Clear();
          if ($RoleIsDatacenter -ne $true)
          {
            if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
            {
              # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
              get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
              $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
              $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
              $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0)
              {
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if($dbs.Length -ne 0)
                {
                  $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                  if ($mbxUser.Length -ne 0)
                  {
                    enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
                  }
                }
              }
            }
            else
            {
              write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
            }  
          }
        " was run: "The object is read-only because it was created in a version of Exchange later than Exchange 1.1 (15.0.0.0). Current supported version is 1.0 (14.0.0.0).".

The object is read-only because it was created in a version of Exchange later than Exchange 1.1 (15.0.0.0). Current supported version is 1.0 (14.0.0.0).
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp


Help! Also, I've done some research about how there should be some data in a homeDBD file in the schema? No data in any of my users that I can copy to.
0
Comment
Question by:joe_edmond
  • 2
4 Comments
 
LVL 4

Expert Comment

by:XCONBLR
ID: 39623916
Do you already have a Exchange 2013 in the environment in the environment which was either installed previously and not probably uninstalled or still existing Exchange 2013.

It looks like is complaining about existing of Exchange 2013 already without ever having a Exchange 2010 version in the org.
0
 
LVL 38

Expert Comment

by:Hypercat (Deb)
ID: 39624328
Are you using a distro of Exchange 2010 with SP3?  I believe SP3 is required to install Exchange 2010 on Server 2012.  Did you try running the Exchange BPA to see if it indicates what's causing this problem?
0
 

Accepted Solution

by:
joe_edmond earned 0 total points
ID: 39800482
The problem was a corruption in the Active Directory database. We ended up rebuilding a new domain and exchange worked perfectly.
0
 

Author Closing Comment

by:joe_edmond
ID: 39811499
I went through possible solutions provided by me, and the problem was solved by a team member of mine.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now