2016 Exchange install error

Mikayel Mikayelyan 71 Reputation points

Can you please help me with this error, currently Exchange servers on premise were compromised and after manually cleaning AD data for that servers new server installation giving this error all prereqs has been installed successfully. Please help with this.

The following error was generated when "$error.Clear();
if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
$mailboxId = [Microsoft.Exchange.Management.Migration.MigrationService.Batch.MigrationBatchIdParameter]::MigrationMailboxName;
$dispName = "Microsoft Exchange Migration";
$mbxs = @(Get-Mailbox -Arbitration -DomainController $RoleDomainController -Filter {Name -eq $mailboxId});
$migrationMailbox = $null;

      if ($mbxs.Length -eq 0)
      Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
      $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
      if ($dbs.Length -ne 0)
      Write-ExchangeSetupLog -Info ("Retrieving users with Name=$mailboxId.");
      $arbUsers = @(Get-User -Filter {Name -eq $mailboxId} -IgnoreDefaultScope -ResultSize 1);
      if ($arbUsers.Length -ne 0)
      Write-ExchangeSetupLog -Info ("Enabling mailbox $mailboxId.");
      $migrationMailbox = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
      $migrationMailbox = $mbxs[0];

      # Set the Organization Capabilities and quotas needed for this mailbox
      if ($migrationMailbox -ne $null)
      Set-Mailbox -Arbitration -Identity $migrationMailbox -ProhibitSendReceiveQuota 300MB -ProhibitSendQuota 300MB -IssueWarningQuota 150MB -RecoverableItemsQuota 30GB -RecoverableItemsWarningQuota 20GB -UseDatabaseQuotaDefaults $false -SCLDeleteEnabled $false -SCLJunkEnabled $false -SCLQuarantineEnabled $false -SCLRejectEnabled $false -HiddenFromAddressListsEnabled $true -DisplayName $dispName -Management:$true -Force;
      Write-ExchangeSetupLog -Info ("Cannot find migration mailbox with name=$mailboxId.");
    " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.

at Microsoft.Exchange.Data.Directory.SystemConfiguration.TenantConfigurationCacheableItem1.TryRunADOperation(ADOperation operation, Boolean throwExceptions) at Microsoft.Exchange.Data.Directory.SystemConfiguration.TenantConfigurationCacheableItem1.Initialize(OrganizationId organizationId, CacheNotificationHandler cacheNotificationHandler, Object state)
at Microsoft.Exchange.Data.Directory.SystemConfiguration.TenantConfigurationCache1.InitializeAndAddPerTenantSettings(OrganizationId orgId, Boolean allowExceptions, TSettings& perTenantSettings, Object state) at Microsoft.Exchange.Data.Directory.SystemConfiguration.TenantConfigurationCache1.TryGetValue(OrganizationId orgId, Boolean allowExceptions, TSettings& perTenantSettings, Boolean& hasExpired, Object state)
at Microsoft.Exchange.Management.RecipientTasks.GetMailbox.ConvertDataObjectToPresentationObject(IConfigurable dataObject)
at Microsoft.Exchange.Configuration.Tasks.GetRecipientObjectTask2.WriteResult(IConfigurable dataObject) at Microsoft.Exchange.Configuration.Tasks.GetTaskBase1.WriteResult[T](IEnumerable1 dataObjects) at Microsoft.Exchange.Configuration.Tasks.GetTaskBase1.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.GetObjectWithIdentityTaskBase2.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.GetRecipientObjectTask2.InternalProcessRecord()
at Microsoft.Exchange.Management.RecipientTasks.GetRecipientWithAddressListBase`2.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,488 questions
0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Andy David - MVP 145K Reputation points MVP

    Ok, gotcha,I would still run the prep commands. Has then been done? or it is failing as well?

    1 person found this answer helpful.
    0 comments No comments

  2. Andy David - MVP 145K Reputation points MVP

  3. Xzsssss 8,861 Reputation points Microsoft Vendor

    Hi @Mikayel Mikayelyan ,

    You should do some preparations before installing the new server. By the way, is it a fresh installation after cleaning AD data? I guess some of the Exchange attributes may still exist in your AD.

    Please follow the steps here to prepare Schema/AD/ADdomains: https://learn.microsoft.com/en-us/exchange/plan-and-deploy/prepare-ad-and-domains?view=exchserver-2016

    E:\Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareSchema  
    E:\Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareAD /OrganizationName:"Contoso Corporation"  
    E:\Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareAllDomains  

    Also the prerequisites should be installed :https://learn.microsoft.com/en-us/exchange/plan-and-deploy/prerequisites?view=exchserver-2016

    Then you could install the Exchange server, the newest one was CU22, you could download it here: https://www.microsoft.com/en-us/download/details.aspx?id=103478

    Best regards,

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  4. Mikayel Mikayelyan 71 Reputation points

    Yes you are it is not clean installation, old servers were compromised and we installed new server in current domain and I tried all the links and command you show there it is always giving me this error. So I assume at this moment it is good idea to remove all exchange related data from ad manually it try from the beginning.
    Thanks for the reply and your effort.

  5. Mikayel Mikayelyan 71 Reputation points

    Those are failing as well. Anyway they decided to go from all clean stage. Thanks for all the comments and reply's.

    0 comments No comments