While installing SQL Server 2008 R2 RTM in a Windows 7 box, noticed an error message:
SQL Server Setup has encountered the following error:
Version's parameters must be greater than or equal to zero.
This error occurs after Setup Support Files are installed and then setup is trying to gather existing SQL components installation information.
From the error message, it looks more like setup is trying to read Version information about a SQL component and it either finds it as NULL or NAN (Not a number).
SQL 2000 client-network utility was installed in the box but the registry entries that specify the version and the language for SQL Server 2000 Tools are missing or incorrect.
Method 1 (Recommended approach):
Re-install SQL Server 2000 client components.
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\
3. Create new key ClientSetup under above location
4. Create new key CurrentVersion under 80\Tools\ClientSetup\
5. On the Edit menu, point to New, and then click String Value.
6. Type CurrentVersion, and then press ENTER.
7. Double-click CurrentVersion, type 8.00.0194 in the Value data box, and then click OK.
8. On the Edit menu, point to New, and then click DWORD Value.
9. Type Language, and then press ENTER.
10. Double-click Language, type 409 in the Value data box (Make sure that hexadecimal radio button is highlighted), and then click OK.
Note: 409 here corresponds to English – United States which is the locale of SQL Server installation. Locale IDs assigned by MS can be looked up here http://msdn.microsoft.com/en-us/goglobal/bb964664.aspx. The language version of your SQL Server installation can be found by checking the properties of setupsql.exe in your SQL Server installation media
11. Exit Registry Editor.
There is also a similar issue reported at http://support.microsoft.com/kb/973301 and it is about SQL Server 2008 with different error message.
Regards,Sakthivel Chidambaram SE, SQL support
Rakesh Singh & Shamik Ghosh
TL, SQL support
Workstation with XP pro installed, no privious SQL server installed on it.
Got the message:
TITLE: SQL Server Setup failure.
Parameter name: build.
Tryed the solution on this page, didn't work, the parameters didn't exist from the beginning, when there is no SQL things installed.
Read about this fenomen on several different sites with different solutions, none of them worked.
After 4 hours reading and testing I desided to test another thing.
I downloaded SQL server 2005 express and installed it, after that I started the SQL server 2008 r 2 installation.
It went thru without any problem, so my recommendation is to install the express and then install the full version after that, it will go so smoooth.
I'm on XP SP3
Installing the SQl2000 Client Components did not work for me.
Nor did the suggestion above with SQL Express 2005.
The regedit work-around in the original article did work though.
I ran into this on Windows XP. Everything worked fine as soon as I implemented the registry fix as described.
The recommended solution worked for me. Though the regedit solution didnt worked.
I reinstalled the SQL Server 2000 client components and it worked. I am on XP SP3 and was trying to install SQL 2008 R2 Express
Thanks Sakthivel, Rakesh & Shamik
the suggestion work fine for me, but the suggested string must be created on this path.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup\CurrentVersion
Method 2 worked to perfection for Windows XP.
SQL Server 2008 R2 setup100.exe and setuppatch.exe cannot be run in this mode. If you are running setup100.exe, start setup.exe instead. If you are running setuppatch.exe, run it from the command prompt, as the user interface is not supported for this action. For more information about Setup, see SQL Server Books Online.
Error code 0x84B20001.
Option 2 worked for me after using the tip from Patricio Poo V, and creating strings here:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup\CurrentVersion]
Workaround 2 works fine. Thanks!
create a .reg file with the following and add it, also back up the registry just in case!
Windows Registry Editor Version 5.00
If machine is 64 Bits
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup\CurrentVersion]