BUG: A separate entry is not created in Add or Remove Programs when you reuse the Windows Installer package with the SQL Server 2000 Desktop Engine (Windows) setup and with the SQL Server 2000 Desktop Engine Service Pack 3 setup (823521)


The information in this article applies to:

  • Microsoft SQL Server 2000 Desktop Engine (Windows)
  • Microsoft SQL Server 2000 Desktop Engine (MSDE) SP3

SYMPTOMS

When you install an instance of Microsoft SQL Server 2000 Desktop Engine (Windows) or you install an instance of Microsoft SQL Server 2000 Desktop Engine (MSDE) Service Pack 3 (also known as MSDE 2000) by using the Windows Installer package (Sqlrunxx.msi) that is already used by an existing instance of SQL Server 2000 Desktop Engine (Windows) or an existing instance of MSDE 2000 SP3, SQL Server 2000 Desktop Engine (Windows) setup and MSDE 2000 SP3 setup do not warn you that the Windows Installer package that you specified has already been used by an existing instance. SQL Server 2000 Desktop Engine (Windows) setup and MSDE 2000 SP3 setup do not fail. You do not receive an error message. You also do not receive errors in the setup log file or in the SQL Server error log file.

The setup process does not create a separate entry in Add or Remove Programs for the newly installed SQL Server 2000 Desktop Engine (Windows) instance or for the newly installed MSDE 2000 SP3 instance. However, the entry for the existing instance of SQL Server 2000 Desktop Engine (Windows) or for the existing instance MSDE 2000 SP3 may be changed, and the instance name may be repeated for the existing instance.

For example, Add or Remove Programs may show the SQL Server Desktop Engine (Windows) instance name as Microsoft SQL Server Desktop Engine (<Instance Name>) (<Instance Name>).

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section of this article.

MORE INFORMATION

SQL Server 2000 Desktop Engine (Windows) and MSDE 2000 SP3 come with a suite of 16 Windows Installer packages (.msi files) that you can use to install new instances of SQL Server 2000 Desktop Engine (Windows) or new instances of MSDE 2000 SP3. Each .msi file is a separate package that permits you to install separate instances of SQL Server 2000 Desktop Engine (Windows) or separate instances of MSDE 2000 SP3.

While installing the SQL Server 2000 Desktop Engine (Windows) instance or the MSDE 2000 SP3 instance, the setup process detects the installed instances and then compares the product code for the Windows Installer package. A new instance of SQL Server 2000 Desktop Engine (Windows) or a new instance of MSDE 2000 SP3 is installed when the product code of the currently used Windows Installer package does not match the product code of the existing instances.

The problem that is mentioned in the "Symptoms" section occurs only when the installed products and the product code of the Windows Installer package are the same.

For example, if SQL Server 2000 Desktop Engine (Windows) version 1.0 is installed by using the Sqlrun02.msi Windows Installer package, and then you try to install SQL Server 2000 Desktop Engine (Windows) version 1.0 again, and you use the same Windows Installer package (Sqlrun02.msi), the problem that is mentioned in the "Symptoms" section occurs. However, if you install SQL Server 2000 Desktop Engine (Windows) version 2.0, and you use the same Windows Installer package (Sqlrun02.msi), SQL Server 2000 Desktop Engine (Windows) setup fails.

Steps to reproduce the problem

  1. Start a command prompt.
  2. Locate the folder where the installation files for SQL Server 2000 Desktop Engine (Windows) exist.
  3. At the command prompt, type the following command, and then press ENTER.

    setup /i <Absolute path of the Windows Installer package file> INSTANCENAME=<instance name> SAPWD=sa /l*v c:\wmsdelog.txt

    Note Replace the <Absolute path of the Windows Installer package file> placeholder and the <instance name> placeholder with their actual values.
  4. Repeat step 3 with the same value for <Absolute path of the Windows Installer package file>.

    Note In this step, if you use different instance names, you can also reproduce the same behavior.
Notice that although the current installation uses the same Windows Installer package that was used by the existing instance, the setup process does not fail. Instead of creating a new entry for the current installation in Add or Remove Programs, the entry for the existing instance is modified.
Modification Type:MajorLast Reviewed:2/23/2004
Keywords:kbSysAdmin kbsetup kbbug KB823521 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.