exchange server 2019安装部署过程邮箱服务出现报错

• 问题

• 

  

  0

  登录进行投票

  报错信息：

  错误:
  运行"$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."
              }  
            }
          "时生成以下错误:"Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: 找不到数据库"qlUsers"。请确保键入的数据库正确。
     在 Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Func`2 notFoundError, Func`2 multipleFoundError, ExchangeErrorCategory errorCategory)
     在 Microsoft.Exchange.Management.RecipientTasks.GetMailboxOrSyncMailbox`1.<>c__DisplayClass68_0.<SetDefaultRetentionValues>b__0()
     在 Microsoft.Exchange.Data.Directory.ProvisioningCache.ProvisioningCache.TryAddAndGetGlobalDictionaryValue[T,K](Guid key, K subKey, CacheObjectGetterDelegate getter)
     在 Microsoft.Exchange.Management.RecipientTasks.GetMailboxOrSyncMailbox`1.SetDefaultRetentionValues(Mailbox mailbox)
     在 Microsoft.Exchange.Management.RecipientTasks.GetMailboxOrSyncMailbox`1.ConvertDataObjectToPresentationObject(IConfigurable dataObject)
     在 Microsoft.Exchange.Management.RecipientTasks.GetMailbox.ConvertDataObjectToPresentationObject(IConfigurable dataObject)
     在 Microsoft.Exchange.Configuration.Tasks.GetRecipientObjectTask`2.WriteResult(IConfigurable dataObject)
     在 Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.WriteResult[T](IEnumerable`1 dataObjects)
     在 Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.InternalProcessRecord()
     在 Microsoft.Exchange.Configuration.Tasks.GetObjectWithIdentityTaskBase`2.InternalProcessRecord()
     在 Microsoft.Exchange.Configuration.Tasks.GetRecipientObjectTask`2.InternalProcessRecord()
     在 Microsoft.Exchange.Management.RecipientTasks.GetRecipientWithAddressListBase`2.InternalProcessRecord()
     在 Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
     在 Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)"。
  
  错误:
  运行"$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."
              }  
            }
          "时生成以下错误:"Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: 找不到数据库"qlUsers"。请确保键入的数据库正确。
     在 Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Func`2 notFoundError, Func`2 multipleFoundError, ExchangeErrorCategory errorCategory)
     在 Microsoft.Exchange.Management.RecipientTasks.GetMailboxOrSyncMailbox`1.<>c__DisplayClass68_0.<SetDefaultRetentionValues>b__0()
     在 Microsoft.Exchange.Data.Directory.ProvisioningCache.ProvisioningCache.TryAddAndGetGlobalDictionaryValue[T,K](Guid key, K subKey, CacheObjectGetterDelegate getter)
     在 Microsoft.Exchange.Management.RecipientTasks.GetMailboxOrSyncMailbox`1.SetDefaultRetentionValues(Mailbox mailbox)
     在 Microsoft.Exchange.Management.RecipientTasks.GetMailboxOrSyncMailbox`1.ConvertDataObjectToPresentationObject(IConfigurable dataObject)
     在 Microsoft.Exchange.Management.RecipientTasks.GetMailbox.ConvertDataObjectToPresentationObject(IConfigurable dataObject)
     在 Microsoft.Exchange.Configuration.Tasks.GetRecipientObjectTask`2.WriteResult(IConfigurable dataObject)
     在 Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.WriteResult[T](IEnumerable`1 dataObjects)
     在 Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.InternalProcessRecord()
     在 Microsoft.Exchange.Configuration.Tasks.GetObjectWithIdentityTaskBase`2.InternalProcessRecord()
     在 Microsoft.Exchange.Configuration.Tasks.GetRecipientObjectTask`2.InternalProcessRecord()
     在 Microsoft.Exchange.Management.RecipientTasks.GetRecipientWithAddressListBase`2.InternalProcessRecord()
     在 Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
     在 Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)"。
  
  错误:
  运行"$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."
              }  
            }
          "时生成以下错误:"Microsoft.Exchange.Management.Tasks.RecipientTaskException: 此任务不支持该类型的收件人。指定的收件人 .com/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} 属于 UserMailbox 类型。请确保此收件人与此任务需要的收件人类型匹配。
     在 Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
     在 Microsoft.Exchange.Management.RecipientTasks.EnableMailbox.PrepareRecipientObject(ADUser& user)
     在 Microsoft.Exchange.Management.RecipientTasks.EnableRecipientObjectTask`2.PrepareDataObject()
     在 Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
     在 Microsoft.Exchange.Configuration.Tasks.RecipientObjectActionTask`2.InternalValidate()
     在 Microsoft.Exchange.Management.RecipientTasks.EnableMailbox.InternalValidate()
     在 Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
     在 Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)"。

  
  

  请问这是怎么回事？改符合解决此报错？谢谢

  2019年7月24日 2:03

  回复

  |

  引用