troubleshooting Question

Hybrid Exchange 2016 update from CU21 to CU22 fails - Arbitration Mailbox error

Avatar of westy rugby
westy rugbyFlag for United Kingdom of Great Britain and Northern Ireland asked on
13 Comments1 Solution17 ViewsLast Modified:

Hybrid Exchange 2016 update from CU21 to CU22 fails on Step 7 Mailbox Role. Passed all pre-requisites during setup and started to install but failed with 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.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__91_1()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Have I a missing arbitration mailbox of some kind? The only option I had was to exit the installation. The exchange services all started but cannot get in to EMC or exch powershell and no mail flow. If I re-run setup it recognises a partial upgrade installation and  resumed the installation but fails on same error. Not sure if I can roll back as I assume it has updated the schema or whether I can recreate the arbitration mailbox if I cannot access the EMC/Powershell. Only 10 mailboxes reside on the server as the rest are in O365 but external mail is routed through this box and is currently not working.

Any help would be gratefully accepted.


Join our community to see this answer!
Unlock 1 Answer and 13 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 13 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros