Reinstalling Exchange server 2019 getting error on Step 7

Rob Flynn 0

Hello Gurus! I have been tasked with setting up a test Exchange server and running in to an issue. A little back story. I did have a working Exchange 2019 server running last year, but we were hit with a Ransomware attack and decided not to restore that server. Fast forward to earlier this month. I created a new Exchange 2019 server and was working perfectly UNTIL the last patch Tuesday updates which broke Secure Boot with the VM and Server 2022. I did not know about the bug until after I had deleted the VM. Now I am trying to set everything up again, and when the Setup get's to step 7 I see this error.

Error: The following error was generated when "$error.Clear(); if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) ) { Update-RmsSharedIdentity -ServerName $RoleNetBIOSName } " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox. at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation) at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave, String callerFilePath, Int32 callerFileLine, String memberName) at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link() at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)"

Can someone shed some light on how to resolve this? Many many thanks in advance!!

EDIT:

Did an uninstall, rebooted and when through the setup process aain (prepare schema etc). Now getting this error.

Error:
The following error was generated when "$error.Clear(); 
          $feVdirName = "PowerShell (Default Web Site)";
          $beVdirName = "PowerShell (Exchange Back End)";
          $vdirName = "PowerShell";
          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

          $vdir = get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName };
          if ($vdir -eq $null)
          {
            new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");
          }
          else
          {
            update-PowerShellVirtualDirectoryVersion -DomainController $RoleDomainController;
          }

          $vdir2 = get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $feVdirName };
          if ($vdir2 -eq $null)
          {
            new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";
          }
          else
          {
            update-PowerShellVirtualDirectoryVersion -DomainController $RoleDomainController;
          }
        " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'xxx.xxx.com/Default Web Site'.
Parameter name: VirtualDirectoryName
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Rob Flynn 0

A quick update. I did an uninstall, rebooted, went through the setup process again (prepare schema etc) and getting this error message.

Error:
The following error was generated when "$error.Clear(); 
          $feVdirName = "PowerShell (Default Web Site)";
          $beVdirName = "PowerShell (Exchange Back End)";
          $vdirName = "PowerShell";
          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

          $vdir = get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName };
          if ($vdir -eq $null)
          {
            new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");
          }
          else
          {
            update-PowerShellVirtualDirectoryVersion -DomainController $RoleDomainController;
          }

          $vdir2 = get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $feVdirName };
          if ($vdir2 -eq $null)
          {
            new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";
          }
          else
          {
            update-PowerShellVirtualDirectoryVersion -DomainController $RoleDomainController;
          }
        " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'xxx.xxx.com/Default Web Site'.
Parameter name: VirtualDirectoryName
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

1 answer

Jarvis Sun-MSFT 10,181 Microsoft Vendor

Hi @Rob Flynn ,

Since this forum is public, I have modified the question to cover the FQDN of your Exchange server.
For security reasons, please don't forget to hide your personal information in the post.

Thanks for your understanding!

According to the log, the error messages are:

The virtual directory 'PowerShell' already exists under 'xxx.xxx.com/Default Web Site'

You can try the following steps to resolve the issues:

Please try to remove the PowerShell Virtual Directory under Default Website and Exchange Back End Website through IIS Manager.
Please open ADSIEdit and connect to Configuration. Locate CN=Configuration, DC=domain, DC=[your domain]/CN=Services/CN=Microsoft Exchange/CN=[your domain]/CN=Administrative Groups/CN=Exchange Administrative Groups/CN=Servers/CN=[your server]/CN=Protocols/CN=HTTP. Delete the PowerShell items like the below. Then have a reinstallation again.

Please note that: Using ADSIEdit is dangerous and can cause serious problems to your environment if not performed correctly. Please make sure to have a full backup of your AD and Exchange servers in case something goes wrong.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

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.

Rob Flynn 0

Thank you for the reply and apologies for not removing the FQDN. Did as you instructed, re-ran the setup and now seeing this error.

I did have this server running and working a few weeks ago but an issue popped up and I needed to start fresh. I was not able to do a clean uninstall of the previous working Exchange server. I'm sure this has something to do with my issues, just not seeing how to get passed this.

Thank you again!

Error:
The following error was generated when "$error.Clear(); 
          if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
          {
            $createNewOab = $false;
            $oabName = $null;
            $oabAddressList = $null;
            $oabVdirs = $null;
            $oabGlobalWebDistribution = $false;
            $oabConfiguredAttributes = $null;

            Write-ExchangeSetupLog -Info ("Looking for an existing default OAB");
            $defaultOab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.IsDefault};
            if ($defaultOab -ne $null)
            {
              Write-ExchangeSetupLog -Info ("Found a default OAB: " + $defaultOab.Name + "; checking its version");
              if ($defaultOab.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -lt 0)
              {
                $e15Oab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -eq 0};
                if ($e15Oab -eq $null)
                {
                  Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2010 or older; will create a new OAB");
                  $createNewOab = $true;
                  $oabName = $defaultOab.Name + " (Ex2013)";
                  $oabAddressList = $defaultOab.AddressLists;
                  $oabGlobalWebDistribution = $defaultOab.GlobalWebDistributionEnabled;
                  $oabConfiguredAttributes = $defaultOab.ConfiguredAttributes;
                }
                else
                {
                  Write-ExchangeSetupLog -Info ("Already has an existing Exchange 2013 OAB:" + $e15Oab.Name + "; will not create a new OAB");
                }
              }
              else
              {
                Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2013 or newer; will not create a new OAB");
              }
            }
            else
            {
              Write-ExchangeSetupLog -Info ("Did not find a default OAB; will create one");
              $createNewOab = $true;
              
              $oabName = [Microsoft.Exchange.Data.Directory.SystemConfiguration.OfflineAddressBook]::DefaultName;
              $nonDefaultOabWithDefaultName = Get-OfflineAddressBook $oabName -DomainController:$RoleDomainController -ErrorAction SilentlyContinue | where {$_.IsDefault -eq $false};
              if ($nonDefaultOabWithDefaultName -ne $null)
              {
                $createNewOab = $false;
                Write-ExchangeSetupLog -Warning `
                  ("Offline address book " + `
                  $nonDefaultOabWithDefaultName.Name + `
                  " already exists: " + `
                  $nonDefaultOabWithDefaultName.DistinguishedName + `
                  ". Use administrative tools to change it to default OAB.");
              }

              $allGals = @(Get-GlobalAddressList -DomainController:$RoleDomainController | where {$_.IsDefaultGlobalAddressList});
              if ($allGals -eq $null -or $allGals.Count -eq 0)
              {
                $createNewOab = $false;
                Write-ExchangeSetupLog -Warning `
                  ("Couldn't find the default global address list. The default offline address book can't be created.");
              }
              elseif ($allGals.Count -gt 1)
              {
                $createNewOab = $false;
                Write-ExchangeSetupLog -Warning `
                  ("Found " + $allGals.Count + " default global address lists. You can have only one default global address list in your organization. The default offline address book will not be created.");
              }
              else
              {
                $oabAddressList = $allGals[0];
                Write-ExchangeSetupLog -Info ("OAB will be based on default GAL: " + $oabAddressList.Name);
              }
            }

            if ($createNewOab)
            {
              if ($oabGlobalWebDistribution -eq $false)
              {
                $currentAdSiteDn = (Get-ExchangeServer $RoleFqdnOrName -DomainController:$RoleDomainController).Site.DistinguishedName;
                $allOabVdirs = @(Get-OabVirtualDirectory -ADPropertiesOnly -DomainController:$RoleDomainController);
                $e15MinimumServerVersion = New-Object Microsoft.Exchange.Data.ServerVersion([Microsoft.Exchange.Data.Directory.SystemConfiguration.Server]::E15MinVersion);
                if ($allOabVdirs -ne $null -and $allOabVdirs.Count -gt 0)
                {
                  foreach ($oabVdir in $allOabVdirs)
                  {
                    if ([Microsoft.Exchange.Data.ServerVersion]::Compare($oabVdir.AdminDisplayVersion, $e15MinimumServerVersion) -gt 0)
                    {
                      $oabVdirSiteDn = (Get-ExchangeServer $oabVdir.Server -DomainController:$RoleDomainController).Site.DistinguishedName;
                      if ($oabVdirSiteDn -eq $currentAdSiteDn)
                      {
                        $oabVdirs = $oabVdir;
                        break;
                      }
                      elseif ($oabVdirs -eq $null)
                      {
                        $oabVdirs = $oabVdir;
                      }
                    }
                  }
                }

                if ($oabVdirs -ne $null)
                {
                  Write-ExchangeSetupLog -Info ("OAB will be distributed to OAB virtual directory " + $oabVdirs.Name);
                }
                else
                {
                  Write-ExchangeSetupLog -Info ("Could not find any OAB virtual directories; OAB will be configured without distribution.");
                }
              }

              try
              {
                Write-ExchangeSetupLog -Info ("Creating new default OAB.");
                $newOab = New-OfflineAddressBook `
                  -Name $oabName `
                  -AddressLists $oabAddressList `
                  -VirtualDirectories $oabVdirs `
                  -GlobalWebDistributionEnabled $oabGlobalWebDistribution `
                  -IsDefault $true `
                  -DomainController:$RoleDomainController;
              }
              catch [Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException]
              {
                Write-ExchangeSetupLog -Warning ("Tried to create new default OAB but the object already exists; it may have been created by another instance of setup.");
              }

              if ($oabConfiguredAttributes -ne $null)
              {
                Write-ExchangeSetupLog -Info ("Setting OAB ConfiguredAttributes to: " + $oabConfiguredAttributes);
                Set-OfflineAddressBook $newOab -ConfiguredAttributes $oabConfiguredAttributes -DomainController:$RoleDomainController;
              }
            }
          }
        " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
   at Microsoft.Exchange.Data.Directory.ADDataSession.ObjectsFromEntries[TResult](SearchResultEntryCollection entries, String originatingServerName, IEnumerable`1 properties, ADRawEntry dummyInstance, String callerFilePath, Int32 callerFileLine, String memberName)
   at Microsoft.Exchange.Data.Directory.ADGenericPagedReader`1.GetNextPage()
   at Microsoft.Exchange.Data.Directory.ADGenericPagedReader`1.<GetEnumerator>d__29.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.FindOrganizationMailboxByCapability(OrganizationCapability capability, QueryFilter optionalFilter, String callerFilePath, Int32 callerFileLine, String memberName)
   at Microsoft.Exchange.Data.Directory.OrganizationMailboxHelper.InternalGetOrganizationMailboxesByCapability(IRecipientSession session, OrganizationCapability capability, QueryFilter optionalFilter)
   at Microsoft.Exchange.ProvisioningAgent.NewOfflineAddressbookProvisioningHandler.FindGeneratingMailbox(String domainController, OrganizationId orgId)
   at Microsoft.Exchange.ProvisioningAgent.NewOfflineAddressbookProvisioningHandler.ProvisionDefaultProperties(IConfigurable readOnlyIConfigurable)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.ProvisionDefaultPropertiesImpl(Task task, IConfigurable temporaryObject, IConfigurable dataObject, Boolean checkProvisioningLayerAvailability)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.ProvisionDefaultProperties(Task task, IConfigurable temporaryObject, IConfigurable dataObject, Boolean checkProvisioningLayerAvailability)
   at Microsoft.Exchange.Configuration.Tasks.NewTaskBase`1.InternalStateReset()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Jarvis Sun-MSFT 10,181 Reputation points Microsoft Vendor

2023-02-28T07:55:10.22+00:00

@Rob Flynn Thanks for your reply. The log information you provided shows that it seems to be an OAB problem, please try deleting the relevant OAB record and then reinstalling. If that doesn't work, we recommend that you do a clean uninstall Exchange Server from AD via ADSIEdit before trying again. Please refer to: https://social.technet.microsoft.com/Forums/exchange/en-US/7ad33f2c-b34c-44d0-93bb-b71b2019f932/uninstallremove-exchange-2010-from-ad
Rob Flynn 0 Reputation points

2023-02-28T13:10:46.8566667+00:00

Thank you Jarvis. Is the OAB record local to my exchange server and where is that located? I actually have done a clean uninstall on AD several times but will attempt once more.

Thank you again!
Jarvis Sun-MSFT 10,181 Reputation points Microsoft Vendor

2023-03-01T07:45:48.31+00:00

@Rob Flynn Thank you for your patience. There are OAB directories in the screenshot shown in my reply, which are in the same path as Powershell and you can try to remove them. If possible, it's better to have a completely new system environment.
Rob Flynn 0 Reputation points

2023-03-01T16:04:13.4333333+00:00

I appreciate your help but unfortunately I still get the same error. I created a new VM with a different name etc but creating a new DC is not an option. I am assuming that is where the fault is.

Based on the error log is there any other spot there could be a rogue entry on our DC? After I deleted the CN=OAB entry using ADSIedit and then re-running setup, it didn't recreate the OAB entry. Any other spots to check or any other suggestions?
Jarvis Sun-MSFT 10,181 Reputation points Microsoft Vendor

2023-03-02T08:43:10.06+00:00

@Rob Flynn To clarify, did you install Exchange Server with your DC server?
Rob Flynn 0 Reputation points

2023-03-02T13:17:20.2666667+00:00

You will have to excuse my ignorance as I am a junior level tech that was thrown in to this. We do have a DC in our infrastructure and did install Exchange using our domain name in the AD setup phase.
Jarvis Sun-MSFT 10,181 Reputation points Microsoft Vendor

2023-03-03T06:19:19.06+00:00

Hi @Rob Flynn ,

After I deleted the CN=OAB entry using ADSIedit and then re-running setup

CN=Configuration,DC=Domain,DC=Com -> CN=Services -> CN=Microsoft Exchange

CN=Configuration,DC=Domain,DC=Com -> CN=Services -> CN=Microsoft Exchange Autodiscover

And you have already tried removing the above two entries using ADSIEdit but still no luck, right? If this is the case, I am afraid you would have to start from scratch given the fact that installing Exchange server on DC is not recommended and could lead to some unexpected issues. Here's a clarification from Microsoft: For security and performance reasons, we don't recommend installing Exchange 2019 on Active Directory directory servers. Only install Exchange 2019 on member servers.

Please refer to: Installing Exchange 2019 on directory servers
Rob Flynn 0 Reputation points

2023-03-03T12:58:22.5733333+00:00

Sorry I misunderstood your question. It is NOT installed on a DC rather it is installed on it's own VM, Server 2022. I have deleted and created several new VM's for the Exchange server more times than I can count. All with the same error message.

Share via

Reinstalling Exchange server 2019 getting error on Step 7

1 answer