Exchange2013-x64-SP1 Extending Active Directory schema FAILED












0















I have problem with Exchange Server 2013, I want to install Exchange 2013 to Windows Server 2012R2.



Extending Active Directory schema                         FAILED

C:Sw>setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.

Performing Microsoft Exchange Server Prerequisite Check

Prerequisite Analysis COMPLETED

Configuring Microsoft Exchange Server

Extending Active Directory schema FAILED
The following error was generated when "$error.Clear();
install-ExchangeSchema -LdapFileName ($roleInstallPath + "SetupData"+$
RoleSchemaPrefix + "schema0.ldf")

" was run: "There was an error while running 'ldifde.exe' to import the schema f
ile 'C:WindowsTempExchangeSetupSetupDataPostWindows2003_schema0.ldf'. The
error code is: 8224. More details can be found in the error file: 'C:UsersAdmi
nistratorAppDataLocalTemp1ldif.err'".


The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:ExchangeSetupLogs folder.


info from file:ldif.err

Entry DN: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=woodgrove,DC=local
Add error on entry starting on line 1: Operations Error
The server side error is: 0x21a2 The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.
The extended server error is:
000021A2: SvcErr: DSID-030A0B6B, problem 5012 (DIR_ERROR), data 8610

An error has occurred in the program









share|improve this question





























    0















    I have problem with Exchange Server 2013, I want to install Exchange 2013 to Windows Server 2012R2.



    Extending Active Directory schema                         FAILED

    C:Sw>setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

    Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for
    installation.

    Performing Microsoft Exchange Server Prerequisite Check

    Prerequisite Analysis COMPLETED

    Configuring Microsoft Exchange Server

    Extending Active Directory schema FAILED
    The following error was generated when "$error.Clear();
    install-ExchangeSchema -LdapFileName ($roleInstallPath + "SetupData"+$
    RoleSchemaPrefix + "schema0.ldf")

    " was run: "There was an error while running 'ldifde.exe' to import the schema f
    ile 'C:WindowsTempExchangeSetupSetupDataPostWindows2003_schema0.ldf'. The
    error code is: 8224. More details can be found in the error file: 'C:UsersAdmi
    nistratorAppDataLocalTemp1ldif.err'".


    The Exchange Server setup operation didn't complete. More details can be found
    in ExchangeSetup.log located in the <SystemDrive>:ExchangeSetupLogs folder.


    info from file:ldif.err

    Entry DN: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=woodgrove,DC=local
    Add error on entry starting on line 1: Operations Error
    The server side error is: 0x21a2 The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.
    The extended server error is:
    000021A2: SvcErr: DSID-030A0B6B, problem 5012 (DIR_ERROR), data 8610

    An error has occurred in the program









    share|improve this question



























      0












      0








      0








      I have problem with Exchange Server 2013, I want to install Exchange 2013 to Windows Server 2012R2.



      Extending Active Directory schema                         FAILED

      C:Sw>setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

      Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup
      Copying Files...
      File copy complete. Setup will now collect additional information needed for
      installation.

      Performing Microsoft Exchange Server Prerequisite Check

      Prerequisite Analysis COMPLETED

      Configuring Microsoft Exchange Server

      Extending Active Directory schema FAILED
      The following error was generated when "$error.Clear();
      install-ExchangeSchema -LdapFileName ($roleInstallPath + "SetupData"+$
      RoleSchemaPrefix + "schema0.ldf")

      " was run: "There was an error while running 'ldifde.exe' to import the schema f
      ile 'C:WindowsTempExchangeSetupSetupDataPostWindows2003_schema0.ldf'. The
      error code is: 8224. More details can be found in the error file: 'C:UsersAdmi
      nistratorAppDataLocalTemp1ldif.err'".


      The Exchange Server setup operation didn't complete. More details can be found
      in ExchangeSetup.log located in the <SystemDrive>:ExchangeSetupLogs folder.


      info from file:ldif.err

      Entry DN: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=woodgrove,DC=local
      Add error on entry starting on line 1: Operations Error
      The server side error is: 0x21a2 The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.
      The extended server error is:
      000021A2: SvcErr: DSID-030A0B6B, problem 5012 (DIR_ERROR), data 8610

      An error has occurred in the program









      share|improve this question
















      I have problem with Exchange Server 2013, I want to install Exchange 2013 to Windows Server 2012R2.



      Extending Active Directory schema                         FAILED

      C:Sw>setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

      Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup
      Copying Files...
      File copy complete. Setup will now collect additional information needed for
      installation.

      Performing Microsoft Exchange Server Prerequisite Check

      Prerequisite Analysis COMPLETED

      Configuring Microsoft Exchange Server

      Extending Active Directory schema FAILED
      The following error was generated when "$error.Clear();
      install-ExchangeSchema -LdapFileName ($roleInstallPath + "SetupData"+$
      RoleSchemaPrefix + "schema0.ldf")

      " was run: "There was an error while running 'ldifde.exe' to import the schema f
      ile 'C:WindowsTempExchangeSetupSetupDataPostWindows2003_schema0.ldf'. The
      error code is: 8224. More details can be found in the error file: 'C:UsersAdmi
      nistratorAppDataLocalTemp1ldif.err'".


      The Exchange Server setup operation didn't complete. More details can be found
      in ExchangeSetup.log located in the <SystemDrive>:ExchangeSetupLogs folder.


      info from file:ldif.err

      Entry DN: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=woodgrove,DC=local
      Add error on entry starting on line 1: Operations Error
      The server side error is: 0x21a2 The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.
      The extended server error is:
      000021A2: SvcErr: DSID-030A0B6B, problem 5012 (DIR_ERROR), data 8610

      An error has occurred in the program






      windows-server-2012-r2 exchange-2013






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 17 '15 at 5:01









      JakeGould

      31.3k1096138




      31.3k1096138










      asked Dec 16 '15 at 13:05









      tony123tony123

      62




      62






















          2 Answers
          2






          active

          oldest

          votes


















          -1














          Do you have another DC somewhere? Maybe a RODC in a DMZ where schema update is prohibited because of a firewall issue.
          You can check for replication issues with this tool: https://www.microsoft.com/en-us/download/details.aspx?id=30005






          share|improve this answer


























          • If there is no RODC have a look at this: support.microsoft.com/en-us/kb/326262

            – The Dude
            Dec 16 '15 at 13:57



















          -1














          This error occur when you have a backup dc on your server just remove the second server run rendom /upload



          your problem will resolve.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1014162%2fexchange2013-x64-sp1-extending-active-directory-schema-failed%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            -1














            Do you have another DC somewhere? Maybe a RODC in a DMZ where schema update is prohibited because of a firewall issue.
            You can check for replication issues with this tool: https://www.microsoft.com/en-us/download/details.aspx?id=30005






            share|improve this answer


























            • If there is no RODC have a look at this: support.microsoft.com/en-us/kb/326262

              – The Dude
              Dec 16 '15 at 13:57
















            -1














            Do you have another DC somewhere? Maybe a RODC in a DMZ where schema update is prohibited because of a firewall issue.
            You can check for replication issues with this tool: https://www.microsoft.com/en-us/download/details.aspx?id=30005






            share|improve this answer


























            • If there is no RODC have a look at this: support.microsoft.com/en-us/kb/326262

              – The Dude
              Dec 16 '15 at 13:57














            -1












            -1








            -1







            Do you have another DC somewhere? Maybe a RODC in a DMZ where schema update is prohibited because of a firewall issue.
            You can check for replication issues with this tool: https://www.microsoft.com/en-us/download/details.aspx?id=30005






            share|improve this answer















            Do you have another DC somewhere? Maybe a RODC in a DMZ where schema update is prohibited because of a firewall issue.
            You can check for replication issues with this tool: https://www.microsoft.com/en-us/download/details.aspx?id=30005







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 16 '15 at 14:01

























            answered Dec 16 '15 at 13:55









            The DudeThe Dude

            12




            12













            • If there is no RODC have a look at this: support.microsoft.com/en-us/kb/326262

              – The Dude
              Dec 16 '15 at 13:57



















            • If there is no RODC have a look at this: support.microsoft.com/en-us/kb/326262

              – The Dude
              Dec 16 '15 at 13:57

















            If there is no RODC have a look at this: support.microsoft.com/en-us/kb/326262

            – The Dude
            Dec 16 '15 at 13:57





            If there is no RODC have a look at this: support.microsoft.com/en-us/kb/326262

            – The Dude
            Dec 16 '15 at 13:57













            -1














            This error occur when you have a backup dc on your server just remove the second server run rendom /upload



            your problem will resolve.






            share|improve this answer




























              -1














              This error occur when you have a backup dc on your server just remove the second server run rendom /upload



              your problem will resolve.






              share|improve this answer


























                -1












                -1








                -1







                This error occur when you have a backup dc on your server just remove the second server run rendom /upload



                your problem will resolve.






                share|improve this answer













                This error occur when you have a backup dc on your server just remove the second server run rendom /upload



                your problem will resolve.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 2 at 15:11









                Manoj MalviyaManoj Malviya

                1




                1






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1014162%2fexchange2013-x64-sp1-extending-active-directory-schema-failed%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Сан-Квентин

                    Алькесар

                    8-я гвардейская общевойсковая армия