How to resolve “the specified account already exists” error during SQL Server 2008 R2 installation












13















I recently had a problem while installing Visual Studio 2012 and SQL Server 2008 R2 on a new development machine. My installation sequence was Visual Studio 2012 then install SQL Server 2008 R2.



An error occurred during the middle of SQL Server installation:




The specified account already exists.




I have spent my day trying to fix this problem.










share|improve this question

























  • Did you find a solution without uninstalling SQL Native client? I have to install SQL Mng Studio on an ERP application server and I think it would be too dangerous uninstalling the db client.

    – Tobia
    Jan 23 '18 at 6:18


















13















I recently had a problem while installing Visual Studio 2012 and SQL Server 2008 R2 on a new development machine. My installation sequence was Visual Studio 2012 then install SQL Server 2008 R2.



An error occurred during the middle of SQL Server installation:




The specified account already exists.




I have spent my day trying to fix this problem.










share|improve this question

























  • Did you find a solution without uninstalling SQL Native client? I have to install SQL Mng Studio on an ERP application server and I think it would be too dangerous uninstalling the db client.

    – Tobia
    Jan 23 '18 at 6:18
















13












13








13


3






I recently had a problem while installing Visual Studio 2012 and SQL Server 2008 R2 on a new development machine. My installation sequence was Visual Studio 2012 then install SQL Server 2008 R2.



An error occurred during the middle of SQL Server installation:




The specified account already exists.




I have spent my day trying to fix this problem.










share|improve this question
















I recently had a problem while installing Visual Studio 2012 and SQL Server 2008 R2 on a new development machine. My installation sequence was Visual Studio 2012 then install SQL Server 2008 R2.



An error occurred during the middle of SQL Server installation:




The specified account already exists.




I have spent my day trying to fix this problem.







sql-server sql-server-2008-r2 installation






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 8 '15 at 8:19









marc_s

7,03053749




7,03053749










asked Aug 7 '15 at 3:54









RAYRAY

258128




258128













  • Did you find a solution without uninstalling SQL Native client? I have to install SQL Mng Studio on an ERP application server and I think it would be too dangerous uninstalling the db client.

    – Tobia
    Jan 23 '18 at 6:18





















  • Did you find a solution without uninstalling SQL Native client? I have to install SQL Mng Studio on an ERP application server and I think it would be too dangerous uninstalling the db client.

    – Tobia
    Jan 23 '18 at 6:18



















Did you find a solution without uninstalling SQL Native client? I have to install SQL Mng Studio on an ERP application server and I think it would be too dangerous uninstalling the db client.

– Tobia
Jan 23 '18 at 6:18







Did you find a solution without uninstalling SQL Native client? I have to install SQL Mng Studio on an ERP application server and I think it would be too dangerous uninstalling the db client.

– Tobia
Jan 23 '18 at 6:18












5 Answers
5






active

oldest

votes


















6














First, search the installation log. In my instance it was under the following path:



C:Program FilesMicrosoft SQL Server100Setup BootstrapLog*.*


In that log I found the following entries:



2015-08-07 11:16:50 Slp: Sco: Attempting to open registry subkey 
2015-08-07 11:16:50 Slp: Sco: Attempting to open registry subkey SOFTWAREMicrosoftVisualStudio9.0
2015-08-07 11:16:50 Slp: Sco: Attempting to get registry value InstallDir
2015-08-07 11:16:50 Slp: Target package: "D:shared~~~~~sqlncli.msi"
2015-08-07 11:16:51 Slp: MSI Error: 1316 The specified account already exists.


I then located the file sqlncli.msi and opened a command prompt to execute this command:



msiexec /i "d:[Your sqlncli.msi path]


I then uninstalled the SQL Server Native Client and ran the installation for SQL Server again, success.






share|improve this answer


























  • Was there any specific article or process that lead you believe you needed to remove the native client?

    – Shawn Melton
    Aug 7 '15 at 4:01






  • 3





    Just to say that this worked for me when I hit this error with SQL Management Studio 2014. I had to uninstall SQL Native Client 2012 for some reason...

    – x3ja
    Sep 24 '15 at 21:43



















5














Regarding where is the indication that SQL Native Client is the issue – the error actually occurs while trying to install the newer SQL Native Client. The solution seems to be: go to Add/Remove Programs and then remove the older SQL Native Client and then retry. No need to abort the installation.



After the older SQL Native Client has been removed, the installation seems to proceed without any problem.






share|improve this answer





















  • 1





    This works for me by just uninstalling the previously installed SQL Native Client.

    – Jerameel Resco
    Oct 20 '16 at 8:16



















3














For completeness:
This also happens when the original msi package had a different name.



If you installed myproductV1.msi and then tried to update it using



msiexec /fvomus myproductV1.msi


it works as expected. But when using



msiexec /fvomus myproductV3.msi


it fails with the mentioned error. Assuming that only the filename changes. Content (especially all GUIDS) stays the same






share|improve this answer































    0














    I received the same error 1603 while installing Sql server 2014. As per the instructions, I have uninstalled sql server 2012 native client but continued to receive the error.
    You will have to find the product name in the log file that is causing this error and uninstall that application and this error will go away. I had to uninstall MICROSOFT_VCPP2010SP1.






    share|improve this answer
























    • Hello and welcome to the site! It would probably be helpful if you clarified which log you are talking about. I'm presuming you mean the installation log but it's but not to leave room for such guesses. Feel free to edit your post to add useful details. Thank you.

      – Andriy M
      Sep 5 '18 at 6:25



















    0














    A different, simpler solution was to install this tool from Microsoft:
    https://support.microsoft.com/en-ca/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed



    It's a troubleshooter that actually shoots your troubles away. At least, it worked for me.





    share








    New contributor




    Jona is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.




















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "182"
      };
      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: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      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%2fdba.stackexchange.com%2fquestions%2f109306%2fhow-to-resolve-the-specified-account-already-exists-error-during-sql-server-20%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      5 Answers
      5






      active

      oldest

      votes








      5 Answers
      5






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      6














      First, search the installation log. In my instance it was under the following path:



      C:Program FilesMicrosoft SQL Server100Setup BootstrapLog*.*


      In that log I found the following entries:



      2015-08-07 11:16:50 Slp: Sco: Attempting to open registry subkey 
      2015-08-07 11:16:50 Slp: Sco: Attempting to open registry subkey SOFTWAREMicrosoftVisualStudio9.0
      2015-08-07 11:16:50 Slp: Sco: Attempting to get registry value InstallDir
      2015-08-07 11:16:50 Slp: Target package: "D:shared~~~~~sqlncli.msi"
      2015-08-07 11:16:51 Slp: MSI Error: 1316 The specified account already exists.


      I then located the file sqlncli.msi and opened a command prompt to execute this command:



      msiexec /i "d:[Your sqlncli.msi path]


      I then uninstalled the SQL Server Native Client and ran the installation for SQL Server again, success.






      share|improve this answer


























      • Was there any specific article or process that lead you believe you needed to remove the native client?

        – Shawn Melton
        Aug 7 '15 at 4:01






      • 3





        Just to say that this worked for me when I hit this error with SQL Management Studio 2014. I had to uninstall SQL Native Client 2012 for some reason...

        – x3ja
        Sep 24 '15 at 21:43
















      6














      First, search the installation log. In my instance it was under the following path:



      C:Program FilesMicrosoft SQL Server100Setup BootstrapLog*.*


      In that log I found the following entries:



      2015-08-07 11:16:50 Slp: Sco: Attempting to open registry subkey 
      2015-08-07 11:16:50 Slp: Sco: Attempting to open registry subkey SOFTWAREMicrosoftVisualStudio9.0
      2015-08-07 11:16:50 Slp: Sco: Attempting to get registry value InstallDir
      2015-08-07 11:16:50 Slp: Target package: "D:shared~~~~~sqlncli.msi"
      2015-08-07 11:16:51 Slp: MSI Error: 1316 The specified account already exists.


      I then located the file sqlncli.msi and opened a command prompt to execute this command:



      msiexec /i "d:[Your sqlncli.msi path]


      I then uninstalled the SQL Server Native Client and ran the installation for SQL Server again, success.






      share|improve this answer


























      • Was there any specific article or process that lead you believe you needed to remove the native client?

        – Shawn Melton
        Aug 7 '15 at 4:01






      • 3





        Just to say that this worked for me when I hit this error with SQL Management Studio 2014. I had to uninstall SQL Native Client 2012 for some reason...

        – x3ja
        Sep 24 '15 at 21:43














      6












      6








      6







      First, search the installation log. In my instance it was under the following path:



      C:Program FilesMicrosoft SQL Server100Setup BootstrapLog*.*


      In that log I found the following entries:



      2015-08-07 11:16:50 Slp: Sco: Attempting to open registry subkey 
      2015-08-07 11:16:50 Slp: Sco: Attempting to open registry subkey SOFTWAREMicrosoftVisualStudio9.0
      2015-08-07 11:16:50 Slp: Sco: Attempting to get registry value InstallDir
      2015-08-07 11:16:50 Slp: Target package: "D:shared~~~~~sqlncli.msi"
      2015-08-07 11:16:51 Slp: MSI Error: 1316 The specified account already exists.


      I then located the file sqlncli.msi and opened a command prompt to execute this command:



      msiexec /i "d:[Your sqlncli.msi path]


      I then uninstalled the SQL Server Native Client and ran the installation for SQL Server again, success.






      share|improve this answer















      First, search the installation log. In my instance it was under the following path:



      C:Program FilesMicrosoft SQL Server100Setup BootstrapLog*.*


      In that log I found the following entries:



      2015-08-07 11:16:50 Slp: Sco: Attempting to open registry subkey 
      2015-08-07 11:16:50 Slp: Sco: Attempting to open registry subkey SOFTWAREMicrosoftVisualStudio9.0
      2015-08-07 11:16:50 Slp: Sco: Attempting to get registry value InstallDir
      2015-08-07 11:16:50 Slp: Target package: "D:shared~~~~~sqlncli.msi"
      2015-08-07 11:16:51 Slp: MSI Error: 1316 The specified account already exists.


      I then located the file sqlncli.msi and opened a command prompt to execute this command:



      msiexec /i "d:[Your sqlncli.msi path]


      I then uninstalled the SQL Server Native Client and ran the installation for SQL Server again, success.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Aug 7 '15 at 4:05









      Shawn Melton

      14.3k43680




      14.3k43680










      answered Aug 7 '15 at 3:58









      RAYRAY

      258128




      258128













      • Was there any specific article or process that lead you believe you needed to remove the native client?

        – Shawn Melton
        Aug 7 '15 at 4:01






      • 3





        Just to say that this worked for me when I hit this error with SQL Management Studio 2014. I had to uninstall SQL Native Client 2012 for some reason...

        – x3ja
        Sep 24 '15 at 21:43



















      • Was there any specific article or process that lead you believe you needed to remove the native client?

        – Shawn Melton
        Aug 7 '15 at 4:01






      • 3





        Just to say that this worked for me when I hit this error with SQL Management Studio 2014. I had to uninstall SQL Native Client 2012 for some reason...

        – x3ja
        Sep 24 '15 at 21:43

















      Was there any specific article or process that lead you believe you needed to remove the native client?

      – Shawn Melton
      Aug 7 '15 at 4:01





      Was there any specific article or process that lead you believe you needed to remove the native client?

      – Shawn Melton
      Aug 7 '15 at 4:01




      3




      3





      Just to say that this worked for me when I hit this error with SQL Management Studio 2014. I had to uninstall SQL Native Client 2012 for some reason...

      – x3ja
      Sep 24 '15 at 21:43





      Just to say that this worked for me when I hit this error with SQL Management Studio 2014. I had to uninstall SQL Native Client 2012 for some reason...

      – x3ja
      Sep 24 '15 at 21:43













      5














      Regarding where is the indication that SQL Native Client is the issue – the error actually occurs while trying to install the newer SQL Native Client. The solution seems to be: go to Add/Remove Programs and then remove the older SQL Native Client and then retry. No need to abort the installation.



      After the older SQL Native Client has been removed, the installation seems to proceed without any problem.






      share|improve this answer





















      • 1





        This works for me by just uninstalling the previously installed SQL Native Client.

        – Jerameel Resco
        Oct 20 '16 at 8:16
















      5














      Regarding where is the indication that SQL Native Client is the issue – the error actually occurs while trying to install the newer SQL Native Client. The solution seems to be: go to Add/Remove Programs and then remove the older SQL Native Client and then retry. No need to abort the installation.



      After the older SQL Native Client has been removed, the installation seems to proceed without any problem.






      share|improve this answer





















      • 1





        This works for me by just uninstalling the previously installed SQL Native Client.

        – Jerameel Resco
        Oct 20 '16 at 8:16














      5












      5








      5







      Regarding where is the indication that SQL Native Client is the issue – the error actually occurs while trying to install the newer SQL Native Client. The solution seems to be: go to Add/Remove Programs and then remove the older SQL Native Client and then retry. No need to abort the installation.



      After the older SQL Native Client has been removed, the installation seems to proceed without any problem.






      share|improve this answer















      Regarding where is the indication that SQL Native Client is the issue – the error actually occurs while trying to install the newer SQL Native Client. The solution seems to be: go to Add/Remove Programs and then remove the older SQL Native Client and then retry. No need to abort the installation.



      After the older SQL Native Client has been removed, the installation seems to proceed without any problem.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Apr 2 '16 at 7:59









      Paul White

      49.4k14260414




      49.4k14260414










      answered Apr 1 '16 at 17:11









      shivesh sumanshivesh suman

      15111




      15111








      • 1





        This works for me by just uninstalling the previously installed SQL Native Client.

        – Jerameel Resco
        Oct 20 '16 at 8:16














      • 1





        This works for me by just uninstalling the previously installed SQL Native Client.

        – Jerameel Resco
        Oct 20 '16 at 8:16








      1




      1





      This works for me by just uninstalling the previously installed SQL Native Client.

      – Jerameel Resco
      Oct 20 '16 at 8:16





      This works for me by just uninstalling the previously installed SQL Native Client.

      – Jerameel Resco
      Oct 20 '16 at 8:16











      3














      For completeness:
      This also happens when the original msi package had a different name.



      If you installed myproductV1.msi and then tried to update it using



      msiexec /fvomus myproductV1.msi


      it works as expected. But when using



      msiexec /fvomus myproductV3.msi


      it fails with the mentioned error. Assuming that only the filename changes. Content (especially all GUIDS) stays the same






      share|improve this answer




























        3














        For completeness:
        This also happens when the original msi package had a different name.



        If you installed myproductV1.msi and then tried to update it using



        msiexec /fvomus myproductV1.msi


        it works as expected. But when using



        msiexec /fvomus myproductV3.msi


        it fails with the mentioned error. Assuming that only the filename changes. Content (especially all GUIDS) stays the same






        share|improve this answer


























          3












          3








          3







          For completeness:
          This also happens when the original msi package had a different name.



          If you installed myproductV1.msi and then tried to update it using



          msiexec /fvomus myproductV1.msi


          it works as expected. But when using



          msiexec /fvomus myproductV3.msi


          it fails with the mentioned error. Assuming that only the filename changes. Content (especially all GUIDS) stays the same






          share|improve this answer













          For completeness:
          This also happens when the original msi package had a different name.



          If you installed myproductV1.msi and then tried to update it using



          msiexec /fvomus myproductV1.msi


          it works as expected. But when using



          msiexec /fvomus myproductV3.msi


          it fails with the mentioned error. Assuming that only the filename changes. Content (especially all GUIDS) stays the same







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 16 '16 at 15:13









          TomBTomB

          1311




          1311























              0














              I received the same error 1603 while installing Sql server 2014. As per the instructions, I have uninstalled sql server 2012 native client but continued to receive the error.
              You will have to find the product name in the log file that is causing this error and uninstall that application and this error will go away. I had to uninstall MICROSOFT_VCPP2010SP1.






              share|improve this answer
























              • Hello and welcome to the site! It would probably be helpful if you clarified which log you are talking about. I'm presuming you mean the installation log but it's but not to leave room for such guesses. Feel free to edit your post to add useful details. Thank you.

                – Andriy M
                Sep 5 '18 at 6:25
















              0














              I received the same error 1603 while installing Sql server 2014. As per the instructions, I have uninstalled sql server 2012 native client but continued to receive the error.
              You will have to find the product name in the log file that is causing this error and uninstall that application and this error will go away. I had to uninstall MICROSOFT_VCPP2010SP1.






              share|improve this answer
























              • Hello and welcome to the site! It would probably be helpful if you clarified which log you are talking about. I'm presuming you mean the installation log but it's but not to leave room for such guesses. Feel free to edit your post to add useful details. Thank you.

                – Andriy M
                Sep 5 '18 at 6:25














              0












              0








              0







              I received the same error 1603 while installing Sql server 2014. As per the instructions, I have uninstalled sql server 2012 native client but continued to receive the error.
              You will have to find the product name in the log file that is causing this error and uninstall that application and this error will go away. I had to uninstall MICROSOFT_VCPP2010SP1.






              share|improve this answer













              I received the same error 1603 while installing Sql server 2014. As per the instructions, I have uninstalled sql server 2012 native client but continued to receive the error.
              You will have to find the product name in the log file that is causing this error and uninstall that application and this error will go away. I had to uninstall MICROSOFT_VCPP2010SP1.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Sep 5 '18 at 0:52









              Nikhil TejNikhil Tej

              1




              1













              • Hello and welcome to the site! It would probably be helpful if you clarified which log you are talking about. I'm presuming you mean the installation log but it's but not to leave room for such guesses. Feel free to edit your post to add useful details. Thank you.

                – Andriy M
                Sep 5 '18 at 6:25



















              • Hello and welcome to the site! It would probably be helpful if you clarified which log you are talking about. I'm presuming you mean the installation log but it's but not to leave room for such guesses. Feel free to edit your post to add useful details. Thank you.

                – Andriy M
                Sep 5 '18 at 6:25

















              Hello and welcome to the site! It would probably be helpful if you clarified which log you are talking about. I'm presuming you mean the installation log but it's but not to leave room for such guesses. Feel free to edit your post to add useful details. Thank you.

              – Andriy M
              Sep 5 '18 at 6:25





              Hello and welcome to the site! It would probably be helpful if you clarified which log you are talking about. I'm presuming you mean the installation log but it's but not to leave room for such guesses. Feel free to edit your post to add useful details. Thank you.

              – Andriy M
              Sep 5 '18 at 6:25











              0














              A different, simpler solution was to install this tool from Microsoft:
              https://support.microsoft.com/en-ca/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed



              It's a troubleshooter that actually shoots your troubles away. At least, it worked for me.





              share








              New contributor




              Jona is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.

























                0














                A different, simpler solution was to install this tool from Microsoft:
                https://support.microsoft.com/en-ca/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed



                It's a troubleshooter that actually shoots your troubles away. At least, it worked for me.





                share








                New contributor




                Jona is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.























                  0












                  0








                  0







                  A different, simpler solution was to install this tool from Microsoft:
                  https://support.microsoft.com/en-ca/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed



                  It's a troubleshooter that actually shoots your troubles away. At least, it worked for me.





                  share








                  New contributor




                  Jona is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  A different, simpler solution was to install this tool from Microsoft:
                  https://support.microsoft.com/en-ca/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed



                  It's a troubleshooter that actually shoots your troubles away. At least, it worked for me.






                  share








                  New contributor




                  Jona is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.








                  share


                  share






                  New contributor




                  Jona is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 6 mins ago









                  JonaJona

                  1011




                  1011




                  New contributor




                  Jona is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Jona is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Jona is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Database Administrators Stack Exchange!


                      • 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%2fdba.stackexchange.com%2fquestions%2f109306%2fhow-to-resolve-the-specified-account-already-exists-error-during-sql-server-20%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

                      Liste der Baudenkmale in Friedland (Mecklenburg)

                      Single-Malt-Whisky

                      Czorneboh