none
Установка Exchange Server 2016 выдает ошибку RRS feed

  • Общие обсуждения

  • Добрый день!

    При установке Exchange Server 2016 CU4 на шаге 6 - Mailbox Role: Transport Service выдается следующая ошибка:

    Error: The following error was generated when "$error.Clear();            if (($RoleIsDatacenter -or $RoleIsDatacenterDedicated) -and ($RoleRoleName -ieq 'FrontendTransportRole' -or $RoleRoleName -ieq 'CafeRole') -and ($RoleDatacenterCafeRoleInETS -eq $false))           {             $exsSid = add-ExchangeServerGroupMember -DomainController $RoleDomainController -ServerName $RoleNetBIOSName -SkipEtsGroup           }           else           {             $exsSid = add-ExchangeServerGroupMember -DomainController $RoleDomainController -ServerName $RoleNetBIOSName           }         " was run: "Microsoft.Exchange.Data.DataValidationException: Property "Database" can only be set for group with type "NonUniversalGroup".    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.Tasks.SetupTaskBase.Save(ADRecipient o, IRecipientSession recipientSession)    at Microsoft.Exchange.Management.Tasks.AddExchangeServerGroupMember.AddServerToGroup(ADGroup group, IRecipientSession session)    at Microsoft.Exchange.Management.Tasks.AddExchangeServerGroupMember.InternalProcessRecord()    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__c()    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Инфраструктура следующая:

    Устанавливается на Windows Server 2016 (все апдейты и необходимые компоненты установлены).

    Устанавливается в "смешанную" организацию - присутствуют Exchange 2010, Exchange 2013, Exchange 2016.

    Несколько сайтов Active Directory, один домен на всю организацию. Устанавливается в сайте где присутствует контроллер домена с ролью глобальной каталога.

    Вывод dcdiag с локального контроллера домена:

     Directory Server Diagnosis

     

    Performing initial setup:

       * Identified AD Forest.

       Done gathering initial info.

     

    Doing initial required tests

      

       Testing server: RnD\RND-DC

          Starting test: Connectivity

             ......................... RND-DC passed test Connectivity

     

     

    Doing primary tests

      

       Testing server: RnD\RND-DC

          Starting test: Advertising

             ......................... RND-DC passed test Advertising

          Starting test: FrsEvent

             There are warning or error events within the last 24 hours after the

             SYSVOL has been shared.  Failing SYSVOL replication problems may cause

             Group Policy problems.

             ......................... RND-DC passed test FrsEvent

          Starting test: DFSREvent

             ......................... RND-DC passed test DFSREvent

          Starting test: SysVolCheck

             ......................... RND-DC passed test SysVolCheck

          Starting test: KccEvent

             ......................... RND-DC passed test KccEvent

          Starting test: KnowsOfRoleHolders

             ......................... RND-DC passed test KnowsOfRoleHolders

          Starting test: MachineAccount

             ......................... RND-DC passed test MachineAccount

          Starting test: NCSecDesc

             ......................... RND-DC passed test NCSecDesc

          Starting test: NetLogons

             ......................... RND-DC passed test NetLogons

          Starting test: ObjectsReplicated

             ......................... RND-DC passed test ObjectsReplicated

          Starting test: Replications

             ......................... RND-DC passed test Replications

          Starting test: RidManager

             ......................... RND-DC passed test RidManager

          Starting test: Services

                IsmServ Service is stopped on [RND-DC]

             ......................... RND-DC failed test Services

          Starting test: SystemLog

             ......................... RND-DC passed test SystemLog

          Starting test: VerifyReferences

             ......................... RND-DC passed test VerifyReferences

      

      

       Running partition tests on : ForestDnsZones

          Starting test: CheckSDRefDom

             ......................... ForestDnsZones passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... ForestDnsZones passed test

             CrossRefValidation

      

       Running partition tests on : DomainDnsZones

          Starting test: CheckSDRefDom

             ......................... DomainDnsZones passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... DomainDnsZones passed test

             CrossRefValidation

      

       Running partition tests on : Schema

          Starting test: CheckSDRefDom

             ......................... Schema passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... Schema passed test CrossRefValidation

      

       Running partition tests on : Configuration

          Starting test: CheckSDRefDom

             ......................... Configuration passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... Configuration passed test CrossRefValidation

      

       Running partition tests on : office

          Starting test: CheckSDRefDom

             ......................... office passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... office passed test CrossRefValidation

      

       Running enterprise tests on : office.---.msk

          Starting test: LocatorCheck

             ......................... office.---.msk passed test LocatorCheck

          Starting test: Intersite

             ......................... office.---.msk passed test Intersite

     

    2 февраля 2017 г. 8:28

Все ответы

  • Сообщение

    Starting test: Services

                IsmServ Service is stopped on [RND-DC]

             ......................... RND-DC failed test Services

    вас не смущает?

    В логах установки Exchange что-то смотрели?
    • Изменено Egor Vasilev 2 февраля 2017 г. 8:43
    2 февраля 2017 г. 8:42
  • Спасибо за ответ!

    Да служба была остановлена, запустил ее на локальном КД.

    В логах установки - та же самая ошибка, что и выдается в мастере установки.

    Сейчас при запуске repadmin /showrepl на локальном КД вижу следующее:

    Repadmin: running command /showrepl against full DC localhost
    RnD\RND-DC
    DSA Options: IS_GC
    Site Options: (none)
    DSA object GUID: b90082f5-a4cd-4ed7-a391-4c8505ad6122
    DSA invocationID: d3ea2726-fbd5-450f-b5e6-2630258a1185

    ==== INBOUND NEIGHBORS ======================================

    DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    CN=Configuration,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was delayed for a normal reason, resu
    lt 8418 (0x20e2):
        The replication operation failed because of a schema mismatch between the se
    rvers involved.
            Last success @ 2017-02-02 12:22:29.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.
        Moscow-MHQ\HQ-DC1 via RPC
            DSA object GUID: cfa515b6-105b-4676-b1af-4b741418498c
            Last attempt @ 2017-02-02 12:46:51 was successful.

    CN=Schema,CN=Configuration,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    DC=DomainDnsZones,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    DC=ForestDnsZones,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    Апдейт схемы был сделан давно под Exchange 2016.

    После этого было установлено 2 севера Exchange 2016 в других сайтах.

    2 февраля 2017 г. 9:53
  • Спасибо за ответ!

    Да служба была остановлена, запустил ее на локальном КД.

    В логах установки - та же самая ошибка, что и выдается в мастере установки.

    Сейчас при запуске repadmin /showrepl на локальном КД вижу следующее:

    Repadmin: running command /showrepl against full DC localhost
    RnD\RND-DC
    DSA Options: IS_GC
    Site Options: (none)
    DSA object GUID: b90082f5-a4cd-4ed7-a391-4c8505ad6122
    DSA invocationID: d3ea2726-fbd5-450f-b5e6-2630258a1185

    ==== INBOUND NEIGHBORS ======================================

    DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    CN=Configuration,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was delayed for a normal reason, resu
    lt 8418 (0x20e2):
        The replication operation failed because of a schema mismatch between the se
    rvers involved.
            Last success @ 2017-02-02 12:22:29.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.
        Moscow-MHQ\HQ-DC1 via RPC
            DSA object GUID: cfa515b6-105b-4676-b1af-4b741418498c
            Last attempt @ 2017-02-02 12:46:51 was successful.

    CN=Schema,CN=Configuration,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    DC=DomainDnsZones,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    DC=ForestDnsZones,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    Апдейт схемы был сделан давно под Exchange 2016.

    После этого было установлено 2 севера Exchange 2016 в других сайтах.

    Сравнил версии схемы на всех КД - везде одинаковая версия.

    Форсировал репликацию с локального КД и теперь repadmin /showrepl не выдает ошибок.

    И теперь repadmin /showrepl не выдает подобной ошибки.

    Но при попытке возобновить установку Exchange 2016 - получается такая же ошибка.

    2 февраля 2017 г. 10:15
  • Спасибо за ответ!

    Да служба была остановлена, запустил ее на локальном КД.

    В логах установки - та же самая ошибка, что и выдается в мастере установки.

    Сейчас при запуске repadmin /showrepl на локальном КД вижу следующее:

    Repadmin: running command /showrepl against full DC localhost
    RnD\RND-DC
    DSA Options: IS_GC
    Site Options: (none)
    DSA object GUID: b90082f5-a4cd-4ed7-a391-4c8505ad6122
    DSA invocationID: d3ea2726-fbd5-450f-b5e6-2630258a1185

    ==== INBOUND NEIGHBORS ======================================

    DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    CN=Configuration,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was delayed for a normal reason, resu
    lt 8418 (0x20e2):
        The replication operation failed because of a schema mismatch between the se
    rvers involved.
            Last success @ 2017-02-02 12:22:29.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.
        Moscow-MHQ\HQ-DC1 via RPC
            DSA object GUID: cfa515b6-105b-4676-b1af-4b741418498c
            Last attempt @ 2017-02-02 12:46:51 was successful.

    CN=Schema,CN=Configuration,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    DC=DomainDnsZones,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    DC=ForestDnsZones,DC=office,DC=auriga,DC=msk
        Moscow-MHQ\HQ-DC2 via RPC
            DSA object GUID: fa805b4e-81d8-403e-8320-cd4f09ff0b3c
            Last attempt @ 2017-02-02 12:45:43 was successful.
        LT\LT-DC via RPC
            DSA object GUID: 49cc1819-26da-476d-bcee-731e9b8a24e9
            Last attempt @ 2017-02-02 12:45:46 was successful.
        Moscow-NIVC\NIVC-DC2 via RPC
            DSA object GUID: 738be7ec-d8d2-40af-966e-c14f10108049
            Last attempt @ 2017-02-02 12:45:48 was successful.
        NNovgorod\NN-DC1 via RPC
            DSA object GUID: a96a3c5a-6e53-4f6d-b7e9-e2dc61afe1bc
            Last attempt @ 2017-02-02 12:45:53 was successful.

    Апдейт схемы был сделан давно под Exchange 2016.

    После этого было установлено 2 севера Exchange 2016 в других сайтах.

    Сравнил версии схемы на всех КД - везде одинаковая версия.

    Форсировал репликацию с локального КД и теперь repadmin /showrepl не выдает ошибок.

    И теперь repadmin /showrepl не выдает подобной ошибки.

    Но при попытке возобновить установку Exchange 2016 - получается такая же ошибка.

    Вот еще кусок лога установки. Судя по всему ошибка происходит на этапе добавления нового сервера в группы безопасности Exchange. Пробовал руками добавлять сервер в группы - не помогает:

    [01/26/2017 19:04:28.0919] [2] Active Directory session settings for 'add-ExchangeServerGroupMember' are: View Entire Forest: 'True', Configuration Domain Controller: 'RND-DC.office.auriga.msk', Preferred Global Catalog: 'RND-DC.office.auriga.msk', Preferred Domain Controllers: '{ RND-DC.office.auriga.msk }'
    [01/26/2017 19:04:28.0919] [2] User specified parameters:  -DomainController:'RND-DC.office.auriga.msk' -ServerName:'RND-MS'
    [01/26/2017 19:04:28.0919] [2] Beginning processing add-ExchangeServerGroupMember
    [01/26/2017 19:04:28.0935] [2] Used domain controller RND-DC.office.auriga.msk to read object DC=office,DC=auriga,DC=msk.
    [01/26/2017 19:04:28.0951] [2] Used domain controller RND-DC.office.auriga.msk to read object CN=RND-MS,OU=Servers,OU=Computers,OU=Rostov,OU=Offices,DC=office,DC=auriga,DC=msk.
    [01/26/2017 19:04:28.0951] [2] Used domain controller RND-DC.office.auriga.msk to read object DC=office,DC=auriga,DC=msk.
    [01/26/2017 19:04:28.0951] [2] Used domain controller RND-DC.office.auriga.msk to read object CN=Microsoft Exchange System Objects,DC=office,DC=auriga,DC=msk.
    [01/26/2017 19:04:28.0951] [2] Used domain controller RND-DC.office.auriga.msk to read object CN=Exchange Install Domain Servers,CN=Microsoft Exchange System Objects,DC=office,DC=auriga,DC=msk.
    [01/26/2017 19:04:28.0966] [2] Used domain controller RND-DC.office.auriga.msk to read object CN=Exchange Servers,OU=Microsoft Exchange Security Groups,DC=office,DC=auriga,DC=msk.
    [01/26/2017 19:04:28.0966] [2] Used domain controller RND-DC.office.auriga.msk to read object CN=Exchange Trusted Subsystem,OU=Microsoft Exchange Security Groups,DC=office,DC=auriga,DC=msk.
    [01/26/2017 19:04:29.0076] [2] [ERROR] Property "Database" can only be set for group with type "NonUniversalGroup".
    [01/26/2017 19:04:29.0076] [2] Ending processing add-ExchangeServerGroupMember
    [01/26/2017 19:04:29.0076] [1] The following 1 error(s) occurred during task execution:
    [01/26/2017 19:04:29.0076] [1] 0.  ErrorRecord: Property "Database" can only be set for group with type "NonUniversalGroup".
    [01/26/2017 19:04:29.0076] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Property "Database" can only be set for group with type "NonUniversalGroup".
       at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
       at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
       at Microsoft.Exchange.Management.Tasks.AddExchangeServerGroupMember.AddServerToGroup(ADGroup group, IRecipientSession session)
       at Microsoft.Exchange.Management.Tasks.AddExchangeServerGroupMember.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    [01/26/2017 19:04:29.0076] [1] [ERROR] The following error was generated when "$error.Clear(); 
              if (($RoleIsDatacenter -or $RoleIsDatacenterDedicated) -and ($RoleRoleName -ieq 'FrontendTransportRole' -or $RoleRoleName -ieq 'CafeRole') -and ($RoleDatacenterCafeRoleInETS -eq $false))
              {
                $exsSid = add-ExchangeServerGroupMember -DomainController $RoleDomainController -ServerName $RoleNetBIOSName -SkipEtsGroup
              }
              else
              {
                $exsSid = add-ExchangeServerGroupMember -DomainController $RoleDomainController -ServerName $RoleNetBIOSName
              }
            " was run: "Microsoft.Exchange.Data.DataValidationException: Property "Database" can only be set for group with type "NonUniversalGroup".
       at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
       at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
       at Microsoft.Exchange.Management.Tasks.AddExchangeServerGroupMember.AddServerToGroup(ADGroup group, IRecipientSession session)
       at Microsoft.Exchange.Management.Tasks.AddExchangeServerGroupMember.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    [01/26/2017 19:04:29.0076] [1] [ERROR] Property "Database" can only be set for group with type "NonUniversalGroup".
    [01/26/2017 19:04:29.0076] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___18976b00b7534ec0a1067e71b5af495b Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [01/26/2017 19:04:29.0076] [1] Setup is stopping now because of one or more critical errors.
    [01/26/2017 19:04:29.0076] [1] Finished executing component tasks.
    [01/26/2017 19:04:29.0107] [1] Ending processing Install-BridgeheadRole
    [01/26/2017 19:07:50.0973] [0] CurrentResult setupbase.maincore:396: 0
    [01/26/2017 19:07:50.0988] [0] End of Setup

    2 февраля 2017 г. 12:41
  • Добрый день,

    сервер под эксч перезагружали после исправления репликации?

    Это виртуалка? Рассинхрона по времени случаем нет между ним и PDC?

    2 февраля 2017 г. 15:00
  • Да, перезагружали.

    Время там верное.

    После установки, которая заканчивается ошибкой видно, что сервер добавлен во все необходимые группы, но не добавлен в группу Exchange Trusted Subsystem. Видимо, как раз на шаге добавления туда сервера и возникает ошибка.

    Проверяли права на все эти группы - все ок.

    Вот эта строка из ошибки не дает покоя:

    [01/26/2017 19:04:29.0076] [2] [ERROR] Property "Database" can only be set for group with type "NonUniversalGroup".

    Как может у группы быть свойство "Database"?

    3 февраля 2017 г. 8:54
  • Да, перезагружали.

    Время там верное.

    После установки, которая заканчивается ошибкой видно, что сервер добавлен во все необходимые группы, но не добавлен в группу Exchange Trusted Subsystem. Видимо, как раз на шаге добавления туда сервера и возникает ошибка.

    Проверяли права на все эти группы - все ок.

    Вот эта строка из ошибки не дает покоя:

    [01/26/2017 19:04:29.0076] [2] [ERROR] Property "Database" can only be set for group with type "NonUniversalGroup".

    Как может у группы быть свойство "Database"?

    Установил.

    Удалил все группы в OU Microsoft Exchange Security Groups и создал их заново путем запуска setup /p (prepare ad).

    Но теперь возникает проблема с новым сервером

    Если пытаться им управлять через ecp - получаю разнообразные ошибки.

    Если  открыть св-ва сервера:

    Warning
    An error occurred while accessing the registry on the server "rnd-ms". The error that occurred is: "Requested registry access is not allowed.".

    Если открыть св-ва сертификатов на сервере:

    error
    The Exchange Certificate operation has failed with an exception on server RND-MS. The error message is: Access is denied


    6 февраля 2017 г. 9:27