Microsoft Exchange Installation Error  at step 14 out of 18 Mailbox Role: Mailbox Service

Posted on 2014-08-30
Medium Priority
Last Modified: 2014-09-21
Migrating from a SBS 2008 Exchange physical Server to Hyper-V Win Server 2012 R2 with Exchange 2013.

 AD Prep completed.

 Initially I used the Exchange 2013 Download link from Volume Licensing, Had multiple issues. Destroyed the VM and created new VM, same setup but using CU5. Then Encountered Certificate issues resulting in ECP blank screen after login. To resolve this Microsoft recommended CU6 http://support.microsoft.com/kb/2971270 release date 26/8.

 Now at installation point 14 out of 18 Mailbox Role: Mailbox Service I have the following error:

 The following error was generated when "$error.Clear();
           if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
           $arbUsers = @(get-user -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"} -IgnoreDefaultScope -ResultSize 1);
           if ($arbUsers.Length -ne 0)
           $mbxname = $arbUsers[0].name;
           $mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname} -IgnoreDefaultScope -resultSize 1 );
           if ( $mbxs.length -eq 0)
           $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
           if ($dbs.Length -ne 0)
           enable-mailbox -Arbitration -identity $arbUsers[0] -database $dbs[0].Identity;
         " was run: "Microsoft.Exchange.Management.Tasks.RecipientTaskException: The user's Active Directory account must be logon-disabled for linked, shared, or resource mailbox.
    at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.RecipientTasks.EnableMailbox.PrepareRecipientObject(ADUser& user)
    at Microsoft.Exchange.Management.RecipientTasks.EnableRecipientObjectTask`2.PrepareDataObject()
    at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.RecipientObjectActionTask`2.InternalValidate()
    at Microsoft.Exchange.Management.RecipientTasks.EnableMailbox.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

 I have a feeling that the initial failed and destroyed Exchange box may be a contributing factor but that might be a red herring as have removed all evidence via ADSIEdit.

 Does anyone have any thoughts?
Question by:saphireneil
  • 3
  • 3
LVL 37

Expert Comment

by:Jian An Lim
ID: 40295848
my wild guess is the arbiration mailbox has not been deleted.

goto adsiedit.msc and search for


Author Comment

ID: 40295851
Sorry, are you saying that I should delete them?
LVL 37

Expert Comment

by:Jian An Lim
ID: 40295917
can you find them?
if my memory serve me right, arbitration mailbox is only available after exchange 2010
exchange 2007 do not have such concept.
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Accepted Solution

saphireneil earned 0 total points
ID: 40325054
Solved my Microsoft support
LVL 37

Expert Comment

by:Jian An Lim
ID: 40326855
do you mind to share how this been solved?

Author Closing Comment

ID: 40335110

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
Last month Marc Laliberte, WatchGuard’s Senior Threat Analyst, contributed reviewed the three major email authentication anti-phishing technology standards: SPF, DKIM, and DMARC. Learn more in part 2 of the series originally posted in Cyber Defense …
This video discusses moving either the default database or any database to a new volume.
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…
Suggested Courses
Course of the Month17 days, 3 hours left to enroll

864 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