Microsoft KB Archive/311762

= How to identify which MSI file was used for an existing MSDE installation =

Article ID: 311762

Article Last Modified on 10/29/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Desktop Engine (Windows)

-



This article was previously published under Q311762



SUMMARY
After you install Microsoft SQL Server 2000 Desktop Engine (also known as MSDE 2000), there are three ways to identify which .msi file the MSDE 2000 setup used. MSDE 2000 includes 16 standard .msi files, and other products may include their own customized MSDE .msi file. Each .msi file is a separate package that allows you to install an instance of the Desktop Engine.

The identification of the correct .msi file is important because you have to use a specific install package to apply service packs to the existing Desktop Engine installation. For example, if you used Sqlrun01.msi to install the original MSDE 2000, then you must use Sqlrun01.msp to upgrade it to Service Pack 2 (SP2). For sqlrun02.msi, you must use Sqlrun02.msp and so forth.



MORE INFORMATION
For an existing MSDE 2000 instance, here are three different ways to identify the .msi file the setup used:   If a verbose installation log was enabled during the MSDE 2000 setup, you can find out which .msi file the MSDE 2000 setup used. The following verbose log content shows that the MSDE 2000 setup used the SqlRun01.msi file:

=== Verbose logging started: 11/15/2001 15:31:42  Build type: SHIP UNICODE 1.11.2405.00  Calling process: E:\WINNT\System32\msiexec.exe === MSI (c) (94:70): Resetting cached policy values MSI (c) (94:70): ******* RunEngine: ******* Product: X:\SQLMSDE2k\Setup\SqlRun01.msi ******* Action: ******* CommandLine: TARGETDIR=&quot;C:\program files\Microsoft SQL Server\MSSQL$MYINSTANCE&quot; DATADIR=&quot;C:\program files\Micros oft SQL Server\MSSQL$MYINSTANCE&quot; INSTANCENAME=MYINSTANCE SECURITYMODE=SQL Note By default, the MSDE 2000 setup does not create a Microsoft Windows Installer Log file. To enable setup verbose logging, you must start the logging from the command line when you execute the Setup.exe file. For example, here is what you type on the command line:

directory:\>setup.exe /L*v c:\msde_install.log

 If you already have MSDE 2000 installed you can check the following registry key to find which .msi file the setup used for the specific MSDE 2000 instance:  Look for the existing MSDE 2000 instance name in the following registry key:

HKEY_CLASSES_ROOT\Installer\Products\ID_Number

The ProductName value displays the instance name. For example, &quot;ProductName&quot; = Microsoft SQL Server Desktop Engine (MYINSTANCE) Locate the following registry subkey:

HKEY_CLASSES_ROOT\Installer\Products\ID_Number\SourceList

The PackageName key value shows the .msi file. For example, &quot;PackageName&quot;=&quot;SqlRun01.msi&quot;

  If MSDE 2000 is already installed, check the MSDE 2000 corresponding instance registry key to find the ProductCode for the MSDE instance. Next, use the ProductCode value to match up the corresponding package file from the table that follows. Please note that the following table information only applies to package files provided with the Microsoft SQL Server Desktop Engine Setup CD and certain other Microsoft products that include a custom install. The table is not exhaustive and does not apply to any third-party developed setup packages. <ul> 'Default Instance'

If the MSDE instance is a default instance, check the following registry key for the ProductCode value:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup

</li> 'Named Instance'

If the MSDE instance is a named instance, check the following registry key for the ProductCode value: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\INSTANCENAME\Setup</li></ul> </li> {| ! ProductCode ! Original Package Name ! Instance Name </li></ul>
 * E09B48B5-E141-427A-AB0C-D3605127224A
 * SqlRun01.msi
 * 689404D2-1C94-44B3-9203-BEC5594FDA7A
 * SqlRun02.msi
 * EFB70B01-B1F3-4960-AB69-4A280084A60C
 * SqlRun03.msi
 * C2736CA7-76E1-4D0C-B590-483A7FFD18DA
 * SqlRun04.msi
 * <any
 * FE7E950B-220A-4182-B5CA-19397244DCFD
 * SqlRun05.msi
 * 7E5C338B-E77E-4CB4-9C1D-FB67B56B3B19
 * SqlRun06.msi
 * F07E35BF-8B03-4777-9B5E-AE90E4FF0932
 * SqlRun07.msi
 * C5B59406-E985-4187-84E8-68E2D9F89A47
 * SqlRun08.msi
 * D7CE240C-0F3B-4C40-9278-C0B90E533652
 * SqlRun09.msi
 * A519AE9C-7C79-4C5B-9127-8F46D648D5A4
 * SqlRun10.msi
 * 4541DA32-2108-43E9-9915-C71B9DE77048
 * SqlRun11.msi
 * A5C1C914-4EF7-40ED-9BCE-FCEB4BB0C19D
 * SqlRun12.msi
 * 9FCE5BBD-D85F-4905-8A0C-12A3A86C2434
 * SqlRun13.msi
 * F4E46404-2578-4955-B748-547957F08AB1
 * SqlRun14.msi
 * B7300824-E68F-45F1-BAC1-5F15636C346F
 * SqlRun15.msi
 * CD59EA85-6CBF-4C08-BE59-6C628B3D8F54
 * SqlRun16.msi
 * 400BEE1A-0B83-44CA-800C-50FCF44C7707
 * Sample.MSI
 * 2678FAA9-9E98-48F2-8C4F-A75B6CF36B86
 * SampleUpg.MSI
 * 5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE
 * .NET SDK English (1033)
 * NetSDK
 * 9E77BDCE-1C37-4A41-AD2A-A515D850F8D0
 * .NET SDK Traditional Chinese (1028)
 * NETSDK
 * 32E07634-0735-4E62-A6DA-594AE069F59F
 * .NET SDK French (1036)
 * NETSDK
 * 4914DDEB-837D-454F-A002-74FF34F996E0
 * .NET SDK Italian (1040)
 * NETSDK
 * 2428ED11-E7F3-41C4-A199-8456E07B2018
 * .NET SDK Japanese (1041)
 * NETSDK
 * 0ED75FF4-1EB6-4C8D-9B46-59D7918E5815
 * .NET SDK Korean (1042)
 * NETSDK
 * 348E0E91-FF67-470B-8191-9D8B82D280A6
 * .NET SDK Spanish (1034)
 * NETSDK
 * 1A585AEE-7D37-45B0-BB0D-68A68EF0CEAB
 * .NET SDK German (1031)
 * NET SDK
 * E18E7A2E-4B5F-4088-812F-220237C70EC3
 * .NET SDK Simplified Chinese (2052)
 * NETSDK
 * 20F95200-47D6-4CAC-92FF-5F6B29C78F88
 * Application Center
 * MSAC
 * 90320409-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 English (1033)
 * ProjectServer
 * 90320411-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Japanese (1041)
 * ProjectServer
 * 9032040D-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Hebrew (1037)
 * ProjectServer
 * 90320404-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Traditional Chinese (1028)
 * ProjectServer
 * 90320412-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Korean (1042)
 * ProjectServer
 * 90320804-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Simplified Chinese (2052)
 * ProjectServer
 * 90320407-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Herman (1031)
 * ProjectServer
 * 90320405-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Czech (1029)
 * ProjectServer
 * 90320406-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Danish (1030)
 * ProjectServer
 * 90320413-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Dutch (1043)
 * ProjectServer
 * 9032040B-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Finnish (1035)
 * ProjectServer
 * 9032040C-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 French (1036)
 * ProjectServer
 * 90320410-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Italian (1040)
 * ProjectServer
 * 90320414-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Norwegian (1044)
 * ProjectServer
 * 90320415-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Polish (1045)
 * ProjectServer
 * 90320416-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Brazilian Portuguese (1046)
 * ProjectServer
 * 90320C0A-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Spanish (3082)
 * ProjectServer
 * 9032041D-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Swedish (1053)
 * ProjectServer
 * 90320419-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Russian (1049)
 * ProjectServer
 * }
 * 90320404-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Traditional Chinese (1028)
 * ProjectServer
 * 90320412-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Korean (1042)
 * ProjectServer
 * 90320804-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Simplified Chinese (2052)
 * ProjectServer
 * 90320407-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Herman (1031)
 * ProjectServer
 * 90320405-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Czech (1029)
 * ProjectServer
 * 90320406-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Danish (1030)
 * ProjectServer
 * 90320413-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Dutch (1043)
 * ProjectServer
 * 9032040B-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Finnish (1035)
 * ProjectServer
 * 9032040C-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 French (1036)
 * ProjectServer
 * 90320410-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Italian (1040)
 * ProjectServer
 * 90320414-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Norwegian (1044)
 * ProjectServer
 * 90320415-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Polish (1045)
 * ProjectServer
 * 90320416-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Brazilian Portuguese (1046)
 * ProjectServer
 * 90320C0A-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Spanish (3082)
 * ProjectServer
 * 9032041D-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Swedish (1053)
 * ProjectServer
 * 90320419-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Russian (1049)
 * ProjectServer
 * }
 * Project Server 2002 Brazilian Portuguese (1046)
 * ProjectServer
 * 90320C0A-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Spanish (3082)
 * ProjectServer
 * 9032041D-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Swedish (1053)
 * ProjectServer
 * 90320419-6000-11D3-8CFE-0050048383C9
 * Project Server 2002 Russian (1049)
 * ProjectServer
 * }
 * Project Server 2002 Russian (1049)
 * ProjectServer
 * }

For MSDE installations where the same ProductCode is used for different localized versions of a service pack (this includes those that are included on the Microsoft SQL Server Desktop Engine Setup CD and the Application Center version of MSDE), it is important to install the correct localized version of a service pack. To identify the language that was used to install a particular instance of MSDE, check the following registry value for a default instance:

or this registry value for a named instance:

This registry value stores a locale ID. Below is a list of the possible locale IDs for MSDE 2000:

<div class="references_section">