Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
pb
Starting Member
13 Posts |
Posted - 2009-08-11 : 18:05:02
|
Hi,It's urgent and your earliest response is greatly appreciated.I need answer for the question. In details, we failed to install and create instance of SQL2005Express on a system that already has MSDE (SQL2000) installed. I got the following error: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.msi'.What's the problem here? Is it because I missed something in my SQL2005 installer, or because MSDE and SQL2005 can't be installed on the same system? The OS we plan to support include Win2000, XP, Win2003, and Vista.I also need help on the following: if the two versions of SQL are compatible on the same system, then we need to allow creation of a new instance of MSDE. To do so, do we need to include the MSDE install package in our installer, or can we use the installed MSDE to create a new instance? And most importantly, what's the command line to create a new MSDE instance with given instance name?Thanks,PB |
|
pb
Starting Member
13 Posts |
Posted - 2009-08-11 : 18:56:30
|
After a bit research, I think I am positive that MSDE and SQL2005 can sit on the same system.Then we need to solve the 'Native Client' error. Now here are my questions:1) What is 'Native Client'? 2) Is it used by the existing databases? I.e. can I remove it safely without affecting existing databases? If so, can anybody provide a commandline to do so? The procedure should be a) determine existance of 'Native Client'; b) run command to uninstal it.3) If it's used/referred by existing databases, .i.e it can't be removed without affecting existing databases, then what commandline option to use to not install it when SQL2005 install (command) is triggered? Here is the current command I am using to install SQL2005: SQLEXPR.exe -q /norebootchk /qb reboot=ReallySuppress addlocal=" +"all instancename=" + my_instance + " SCCCHECKLEVEL=IncompatibleComponents:1;MDAC25Version:0 " + "ERRORREPORTING=1 SQLAUTOSTART=1 SAPWD=" + my_password + " SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0";I prefer 2) if both 2) and 3) are doable, because I just simply install 'ALL' SQL2005 needs.Thanks,PB |
 |
|
pb
Starting Member
13 Posts |
Posted - 2009-08-11 : 19:19:29
|
Sorry I think there might be a 3rd option (I just realized that 'VSS Writer' also has the same issue as 'Native Client'):3) when installing SQL2005, if 'Natvie Client' and/or 'VSS Writer' are installed, don't try to instll them.If so, what the commandline should be?Thanks,PB |
 |
|
pb
Starting Member
13 Posts |
Posted - 2009-08-11 : 21:00:41
|
I think I can use registry (HKLM\Software\Microsoft\Microsoft SQL Native Clietn)to determine existance of 'Native Client'. If the registry key exists, I will remove 'Client_Components' option for my SQL200Express install. The BIG question is: is 'Client_Components' option for 'Native Client'? If not, how to avoid includsion of 'Native Client' from the new SQL2005Express install (with commandline)?Is there similar registry that is for 'VSS Writer'? Same question for it (how to avoid inclusion of it from the new SQL2005Express install with commandline).Thanks,PB |
 |
|
|
|
|
|
|