« Update Java on Citrix XenApp server or not? | Home | AdminStudio Benchmark: Accelerating App-V Package Creation Up to 88% Faster than Traditional Methods »
sqlncli_x64.msi cannot be found while installing SQL Server 2005 64bit on Windows Server 2003
August 13, 2009
While installing SQL Server 2005 64bit on a Windows Server 2003 64bit an error message displays that “An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package ‘sqlncli_x64.msi’.” as shown below.
After that, the Microsoft SQL Server 2005 Setup Progress will display some errors with a status “Setup Failed. Refer to the Setup log for details”.
When trying to install the Microsoft SQL Server Native Client Setup by hand it displays a similar error message that the file ‘sqlcli_x64.msi’ cannot be found. Looking at the installation files there is copy of ‘sqlcli.msi’ but without the _x64.
Solution for this problem is that someone started the installation with a wrong bit (32 vs. 64) edition and left the components there. Go to Add/Remove Programs and remove the existing SQL components, and then reinstall.
Topics: Microsoft | 6 Comments »







September 30th, 2009 at 8:13 pm
Thanks Eric. Saved me some time. I was handed this clustered server supposedly “cold-iron” with the same environment, W2K3_x64-R2, SQL9Ent. I was installing SQL in a cluster when I hit this error. You were right – and “no one knows” where the 32-bit binary muddy footprints came from. Hmmm.
February 18th, 2010 at 5:55 pm
I’m also very grateful. In my case, the server was engaged before to Microsoft Virtual Server. Maybe the corrupt file came from that service?
March 10th, 2010 at 1:25 pm
Thanks a lottt !!!!!
It worked.
April 27th, 2010 at 4:20 pm
Thanx !!!
Helped me !!!
June 5th, 2010 at 6:55 pm
Many thanks for the useful piece of information. I had this error crop up on a couple of servers and was starting to feel very frustrated until I decided to look for help on the web. Your post saved me some time.
July 23rd, 2010 at 7:34 pm
Thanks a lot, man!
Who would know.. I installed SQL Server so many times before and this thing never happened.
Cheers,
Ivo Pereira