При установке sql server 2012 ошибка 0x84b10001

Ответы

• can you try the following

  1-un install SQL setup package from addremove programs and try again

  2-decompress express package to local folder run as administrator <package.exe /x:»d:SQLExpress2012Uncompressed»

  the launch setup.exe from command line from d:SQLExpress2012Uncompressed and run 

  setup.exe /action=install, if this doesn’t wrok please see below FAQ on how to share/upload comple SQL Server setup logs

  ---

  FAQ
  
  —-
  Regards,
  Ahmed Ibrahim
  SQL Server Setup Team
  My Blog
  This posting is provided «AS IS» with no warranties, and confers no rights. Please remember to click
  «Mark as Answer» and «Vote as Helpful»
  on posts that help you.
  This can be beneficial to other community members reading the thread.
  
  

  • Помечено в качестве ответа

    7 ноября 2012 г. 9:47

• Hi All,
  Thank you for your advice, this worked.
  This is what I did…..
  I extracted the ‘SQLEXPRADV_x64_ENU’ to its own local directory. I changed to this new directory and right clicked on ‘setup.exe’ and then selected to run this as an administrator.
  It installed without any errors … took about an hour.
  Thanks once again Ahmed.
  Regards.
  Chris van Nispen

  • Помечено в качестве ответа
    Chris van Nispen
    13 ноября 2012 г. 11:59

• • Помечено в качестве ответа
    Shulei Chen
    7 ноября 2012 г. 9:47

• Hello,

  This may be related to an MSDE instance installed on that computer. Please use the following article to remove the instance and try to install SQL Server 2012 again.

  http://support.microsoft.com/kb/320873

  
  Hope this helps.

  Regards,

  Alberto Morillo

  SQLCoffee.com

  • Помечено в качестве ответа
    Shulei Chen
    7 ноября 2012 г. 9:47

• Remove From My Forums

All replies

• Hi, can you try to unpack the Express package and run setup from the command line?  This should get around the issue.  To do so,

  • Uninstall SQL Server setup package from add/remove programs
  • Unpack the Express package to a local folder and run setup as admin.  To do so, run <package.exe> /x:»c:SQLExpressUnpacked»
  • Launch setup.exe from the command line from c:SQLExpressUnpacked using «setup.exe /action=install»

  Thanks,
  Sam Lester (MSFT)

  ---

  http://blogs.msdn.com/b/samlester

  This posting is provided «AS IS» with no warranties, and confers no rights. Please remember to click
  «Mark as Answer» and
  «Vote as Helpful» on posts that help you. This can be beneficial to other community members reading the thread.

  • Proposed as answer by
    Ahmed Ibrahim — MSFTMicrosoft employee
    Monday, September 16, 2013 6:48 PM

• thank you for yor reply!

  there is no sql setup packge or anything like that on the add/remove programs.

  beside that I don’t understand the other two bullets below

  thank you

• No problem.  SQL Server Express edition ships as a downloadable .exe file which unpacks and runs setup.exe when you launch it.  We’re going to «unpack» the shipped .exe to access the folder structure directly, then run the setup.exe file from inside.
   To do so:

  Step 1: uninstall any existing SQL Server Express bits (not needed since you don’t have any in A/R Programs)

  Step 2:   Depending on your package that you downloaded (32-bit, 64-bit, etc.), you’ll run the following from the command line (run as administrator).

  SQLEXPR_x64_ENU.exe /x:»c:SQLExpressUnpacked»
  (where c:SQLExpressUnpacked is a folder that you’ve created to put the temporary install files)

  Step 3:  From the cmd prompt, navigate to c:SQLExpressUnpacked and run «setup.exe
  /action=install»

  This will launch SQL Server Express setup directly and should get you around the issue.

  Thanks,
  Sam Lester (MSFT)

  ---

  http://blogs.msdn.com/b/samlester

  This posting is provided «AS IS» with no warranties, and confers no rights. Please remember to click
  «Mark as Answer» and
  «Vote as Helpful» on posts that help you. This can be beneficial to other community members reading the thread.

• thank you again

  setup.exe is not working.

  the command is not recognized as an internal or external command

• • Proposed as answer by
    David.Garcia.Herrero
    Thursday, April 21, 2016 4:13 PM

• the command is not recognized as an internal or external command

  This error is typically the result of running the command line from the wrong path.  Were you able to unpack the files to a folder somewhere on your machine?  If so, were you able to navigate from the cmd prompt to that folder and run setup.exe? 
  You can also try to navigate to that folder and double click the setup.exe program to install through the UI.  Both should work for you.

  Thanks,
  Sam Lester (MSFT)

  ---

  http://blogs.msdn.com/b/samlester

  This posting is provided «AS IS» with no warranties, and confers no rights. Please remember to click
  «Mark as Answer» and
  «Vote as Helpful» on posts that help you. This can be beneficial to other community members reading the thread.

• thank, I try uninstall MSDE from my PC is succesed.

• the best way to solve it is going into 110 flooder, rename Boostrap floder like Boostrap1, install package SQL 2012 server restart and enjoy!

  C:Program filesMicrosoft SQL Server110Boostrap

  hope this help you, one more thing to make this better just after rename flooder Boopstrap clean registre then install again

  Best Regards

  Nuvatus

I’m trying to install SQL Server Express with Service Pack 1 on my Win8 Pro (x64) development machine and I’m consistently getting an error 0x84b10001 when trying to install it:

Antivirus is disabled during the installation (done as Administrator) and I tried 2 versions of the SQL Server Express package and I’m getting the same issue with both.
I’m getting the same issue whether I’m trying the x86 or x64 packages.

I suspect that the issue comes from the fact that Visual Studio 2013 has already installed some SQL Server packages but I do not see any way to update and modify these to add the Management Studio for istance.

asked Feb 8, 2014 at 7:37

Create a new local user with administative rights and try the installation again. In my case it solves the problem with MSSQL 2008R2.

Create new user with administrative privileges and install using that user. It worked.

In my case, it was because trying to install an x86 package on an x64 windows, installing x64 package worked for me.