May 21 2020 06:25 AM
I am trying to install additional exchange server 2013 CU 15 as mailbox server. I face the following error:
Error:
The following error was generated when "$error.Clear();
if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -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: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.".
Error:
The following error was generated when "$error.Clear();
if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -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: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
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, Boolean reThrow)
at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.Validate(TDataObject dataObject)
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()
at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()
at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
May 21 2020 02:09 PM
@salahsami2002Are you certain that the user running this had the correct permissions? Can you tell us more about the forest/domain and the group membership of the user who is attempting the install?
May 21 2020 02:15 PM
Just I have one domain in the forest without child domain.
I use administrator @domian
May 21 2020 02:24 PM
OK - Can you ensure that that account is a member of Schema Admins, Domain Admins, and Enterprise Admins permissions as well as Organization Management?
May 21 2020 02:35 PM
May 21 2020 04:02 PM
OK that sounds correct - the other error I see in your initial post is:
was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
There might be a user/resource/shared mailbox that doesn't have database nulled (happens when you delete a DB forcefully or lose and not restore it)
But the combination of the database and the discovery search mailbox makes me think that perhaps you lost your arbitration mailboxes at some point.
Perform a:
get-mailbox -arbitration
in your environment and see in you have them still? If not, you can recreate them:
May 21 2020 05:50 PM
May 21 2020 06:15 PM
When i run the command Enable-Mailbox -Identity "FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042" -Arbitration
here is the error:
This task does not support recipients of this type. The specified recipient
smartlink.com.sa/Users/FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 is of type UserMailbox. Please make sure
that this recipient matches the required recipient type for this task.
+ CategoryInfo : InvalidArgument: (domainname....bf-00a95fa1e042:RecipientIdParameter) [Enable-Mailbo
x], RecipientTaskException
+ FullyQualifiedErrorId : [Server=xxxxxxxxxxxxx,RequestId=48a79458-38b5-4851-bd48-03b65f4c129c,TimeStamp=5/22/2020
1:12:57 AM] [FailureCategory=Cmdlet-RecipientTaskException] 15D064D0,Microsoft.Exchange.Management.RecipientTasks
.EnableMailbox
+ PSComputerName : xxxxxxxxxxxxxxxxxx
May 21 2020 06:32 PM
Same error for the commands
Enable-Mailbox -Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration
Enable-Mailbox -Identity "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}" -Arbitration
Enable-Mailbox -Identity "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}" -Arbitration
Enable-Mailbox -Identity "SystemMailbox{D0E409A0-AF9B-4720-92FE-AAC869B0D201}" -Arbitration
Enable-Mailbox -Identity "SystemMailbox{2CE34405-31BE-455D-89D7-A7C7DA7A0DAA}" -Arbitration
This task does not support recipients of this type. The specified recipient
domain.com/Users/SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} is of type UserMailbox. Please make sure
that this recipient matches the required recipient type for this task.
May 21 2020 11:59 PM
Hi @salahsami2002,
If you later update the roles of the admin once the setup returned the errors, you may face this issue.
You can try following:
Right click on the admin account and select copy
create another account with same set of permissions (schema and enterprise must be there)
and login with this account.
Try installation again.
May 22 2020 12:43 AM
May 25 2020 07:59 PM
Solution
Thank you for response.
Lets fall back to previous suggestions. You can get the arbitration mailbox details as
[PS] C:\Windows\system32>get-Mailbox -Arbitration | ?{$_.Name -eq "SystemMailbox{1f05a927-bdc1-42a4-a08c-605fbc697a92}"
}
Name Alias ServerName ProhibitSendQuota
---- ----- ---------- -----------------
SystemMailbox{1f05a927... SystemMailbox{1f0... exch1 Unlimited
May 25 2020 11:34 PM
@salahsami2002 Please share the resolution.
May 27 2020 02:14 PM
May 29 2020 10:27 PM
May 25 2020 07:59 PM
Solution
Thank you for response.
Lets fall back to previous suggestions. You can get the arbitration mailbox details as
[PS] C:\Windows\system32>get-Mailbox -Arbitration | ?{$_.Name -eq "SystemMailbox{1f05a927-bdc1-42a4-a08c-605fbc697a92}"
}
Name Alias ServerName ProhibitSendQuota
---- ----- ---------- -----------------
SystemMailbox{1f05a927... SystemMailbox{1f0... exch1 Unlimited