Microsoft Developer Network > Forums Home > SQL Server Forums > SQL Server Setup & Upgrade > install sql server 2005 express on 64 bit windows

Answered install sql server 2005 express on 64 bit windows

  • Friday, June 02, 2006 9:58 PM
     
     

    I am trying to install sql server 2005 express on 64 bit windows but i get a error message saying SQLncli_x64.msi file is missing and asks me to download it.

    How can i fix this problem to install the SQL server on my Windows XP x64 Edition?

Answers

All Replies

  • Tuesday, June 20, 2006 7:47 PM
     
     

    Make sure you are installing either SQLEXPR.EXE or SQLEXPR_ADV.EXE, which are the full installers that support x64 systems. To be clear, we only support installing in WoW mode and we only support x64. You will not be able to install on I64 computers.

    Regards,

    Mike Wachal
    SQL Express team

  • Monday, July 10, 2006 6:48 PM
     
     

    I tried both of installers SQLEXPR.EXE and SQLEXPR_ADV.EXE and im still getting the same error msg:

    "And installation package for the product Microsoft Native Client cannot be found. Try the installation again using a  valid copy of the installation package 'sqlncli_x64.msi"

  • Monday, July 10, 2006 7:21 PM
     
     Proposed Answer

    Any other installations of SQL Server 2005 on the computer?

    If not, you should check Add/Remove Programs to see if SQL Native Client is listed and if it is, remove it and try again. If that doesn't work, you could try unpacking the Express package and installing the native client manually:

    1. Run: SQLEXPR.EXE /x
    2. Specify a directory to unpack to files to when asked
    3. Find sqlncli_x64.msi in the Setup folder where you unpacked and run it

    For good measure I'm going to move this over to the Setup forum to see if they have any better ideas.

    Mike

    • Proposed As Answer by Jorge Villamil Tuesday, May 22, 2012 11:46 PM
    •  
  • Tuesday, July 11, 2006 2:08 PM
    Moderator
     
     Answered

    If SQL Native Client is not installed, you can obtain from http://www.microsoft.com/downloads/details.aspx?familyid=DF0BA5AA-B4BD-4705-AA0A-B477BA72A9CB&displaylang=en

    *** Look for the "X64 Package (sqlncli_x64.msi) - 6403 KB" one.

     

    Thanks,

    Peter Saddow

     

  • Tuesday, July 11, 2006 2:54 PM
     
     Proposed Answer

    Finally i solved the problem following the next steps:

    1. Uninstall native client  using add/remove programs on control panel.
    2.Try to install SQL Server Again.

    I tried al least 3 times but at the end it works.

    Thank you for the support.

    About the other solutions none worked

     

     

     

  • Monday, June 25, 2007 9:18 AM
     
     
    I found that disabling Kapersky Anti-virus during the installation solved the problem on my vista 64 machine.
  • Friday, October 19, 2007 10:14 PM
     
     Proposed Answer
    Of all the stupid.... The "Installing Prerequisites" stage of the installer installs the incorrect version of the SQL Native Client. Immediately after the "Installing Prerequisites" stage (but before the rest of the installation process), follow any of the above advice to download/extract the sqlncli_x64.msi file, go to the control panel and remove the "Microsoft SQL Native Client", and then install the newly downloaded/extracted msi instead. When that's done, you should be able to go through the end of the installtion process without too much more difficulty.

     

    (running Vista x64, installing SQL 2005 Express Edition x64 with SP2)

  • Wednesday, January 02, 2008 6:21 PM
     
     

    Hi Eric -- you are the man. I just made the switch to x64 Vista Ultimate on my recently acquired laptop and your reply got me going while trying to install the SQL2005EE SP2 Adv Services (SQLEXPR_ADV) and Toolkit (SQLEXPR_TOOLKIT) downloads.

     

    For the SQLEXPR_ADV segment, I just did an Add/Remove on the SQL Server Native Client prior to hitting the "Next" button displayed right after completing the prerequisites install phase. After that, everything was as smooth as one would expect.

     

    For SQLEXPR_TOOLKIT install, the only event to note was that I allowed the package to re-upgrade the workstation components. When prompted about VS2005 compatability issues, I just picked "Run Program" since this will be addressed by SP1 updates, etc. Finally, this install was only the initial step in getting my laptop set up for work/development so I will not be concerned about compatibility issues until I am done installing stuff and then begin to download updates and service packs/patches.

     

    Thanks again to all,

    Ron Larson (who usually just lurks on these forums to look for answers, otherwise "Howdy y'all")

  • Sunday, February 10, 2008 8:38 PM
     
     
    Thanks a million, Eric!  Finally a solution on this damn ting!
    I tried to install SQL Server 2005 Enterprise Edition 64-bit Extended from the MSDN Subscription DVD (Disk 3545 May 2006), and also I downloaded the iso-file for SQL Server 2005 Enterprise Edition 64-bit Extended from the MSDN download site - none of them worked.
    After reading your post I tried the SQL Server 2005 Developer Edition 64-bit Extended (which is Enterprise ed. + some developer tools) instead - it has the right Native Client and worked perfectly.  Great!
  • Wednesday, May 14, 2008 11:35 PM
     
     

     

    And... SEVEN MONTHS after Eric posted the solution AND described the problem...

     

    Has MS corrected it? NOOO!

     

    Has MS the intention of correcting it? DON'T THINK SO

     

    This is unacceptable, even more being aware that this is not happening on a forgotten blog from the very most remote place on Earth, WE ARE AT MSDN OFFICIAL FORUMS! Hello! Is anybody at home???

     

     

    * sigh *

  • Wednesday, June 04, 2008 11:06 AM
     
     
    Thanks a lot Eric, very helpful...

     

  • Monday, June 16, 2008 7:54 PM
     
     

    Thanks Eric.

     

    That was all that was needed. Just install the client first and then the rest of the install works.

     

  • Monday, August 25, 2008 10:01 PM
     
     

     

    And... SEVEN MONTHS after Eric posted the solution AND described the problem...

     

    Has MS corrected it? NOOO!

     

    Has MS the intention of correcting it? DON'T THINK SO

     

    You were right. Not only are they not going to fix this bad installation. They now have Express 2008 that is broke even worse. It relies on a SP that isn't even relased yet. Further, if you follow the Terrible work around they have for it and unistall it, you can never install it again. Typical, it seem=s they have forgotten about why IBM went down the toilet. Sienfeld can't pull them out of the mess they are making.

     

     

  • Friday, May 29, 2009 5:18 PM
     
     
    It's now the end of May 2009 and the answers here have helped greatly!
  • Friday, February 05, 2010 6:31 PM
     
     
    .... and it is Feb 2010 and this problem still exists, and Eric's help was still necessary!!!!!!!
  • Monday, February 15, 2010 4:58 AM
     
     

    Valentine's day 2010 -- same problem.  Eric's solution saved the day!  Thanks Eric!

  • Thursday, February 18, 2010 5:13 PM
     
     

    I'm running Windows7 Home Edition - 64 bit

    When I create a Default.aspx page in Visual Web Developer 2008 Express Edition and try to
    "add new item" in the form of an SQL Server Database, it first advises me that the database
    must be located in the "App_Data file and, once acknowledged, the following error messsaGE appears:

    Error Message As Follows:
    Visual Web Developer 2008 Express Edition
    Connection to SQL Server files (*.mdf) require SQL Server Express 2005 to function properly. 
    Please verify the intsallation of the component or download from the URL:
    http://go.microsoft.com/fwlink/?LinkId=49251

    I have gone to the link dozens of times, reloaded SQL Server, I've performed Eric's advice dozens
    of time ......the problem remains unresolved.

    Does anyone have any suggestions.

  • Thursday, March 25, 2010 7:40 PM
     
     
    Money ERIC! Listen to Eric
  • Thursday, March 25, 2010 7:57 PM
     
     

    Good man Eric

     

  • Wednesday, April 07, 2010 7:29 PM
     
     

    Similar situation with sqlwriter_x64.msi, i.e. uninstall "Microsoft SQL Server VSS Writer" immediately after "Installing Prerequisites." If this is not done, you'll see an error regarding "sqlwriter_x64.msi" not valid or not found when installing onto an x64 edition of Windows.

    Props to Eric. Nearly three years later his advice is still very helpful.

  • Friday, May 21, 2010 9:36 PM
     
     
    Here here! Thanks Eric!
  • Tuesday, August 03, 2010 6:20 PM
     
     
    Yep - that did it, thanks Eric. - still an issue with product version 9.00.4043.0
    Software Techie
  • Wednesday, October 20, 2010 8:30 AM
     
     
    20th of Oct, 2010, same problem, same solution! Cheers guys, cheers Microsoft....
  • Tuesday, March 29, 2011 5:16 PM
     
     

    Same issue and solution from Eric helped.

    However in my case I had some really funky install issues. I installed the native client first. Then the sql server removes it and add's it's own built in install. After this was installed and after the prereq screen, I went into add/remove programs - no native client listed. Attempted to install the 64bit client and it said a newer version was installed - remove this first. Checked add/remove programs (new launch) and still nothing listed. Switched to show windows patches. Switched back to uninstall a program - native client now listed. Removed. Installed 64bit client and finally able to go back to the sql install and continue through to the end successfully.

     

    Thanks once again Eric.


    http://absoblogginlutely.net
  • Tuesday, June 07, 2011 11:37 AM
     
     
    And... 

    FOUR YEARS

     after Eric posted the solution AND described the problem...
     
    Has MS corrected it? NOOO!
     
    Has MS the intention of correcting it? DON'T THINK SO


  • Friday, October 28, 2011 3:54 PM
     
     
    Worked like a charm after a week of experimenting.  Thank you thank you
  • Thursday, December 01, 2011 10:26 AM
     
     

    ya, it sucks that Ms hasnt done anything on this.

    Eric's solutions, is not working for me.

    Im trying to install on windows server 2008