Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
HOW TO: Troubleshoot a SQL Server Desktop Engine 2000 Installation and Upgrade
Article ID: 317328 - View products that this article applies to.
This article was previously published under Q317328
SQL Server 2000 Desktop Engine (also known as MSDE 2000) is a data engine that is built and based on core SQL Server technology. With support for single and dual-processor desktop computers, MSDE 2000 is a reliable storage engine and query processor, for desktop extensions of enterprise applications. With the common technology base that SQL Server and MSDE 2000 share, developers can build applications that can scale seamlessly from portable computers to multiprocessor clusters.
This article includes general information for the following parts of MSDE 2000:
How to Install MSDE 2000There are multiple ways to install MSDE 2000. Generally, you can separate the installations into either:
Here are three stand-alone MSDE 2000 installation methods:
To troubleshoot an MSDE 2000 installation, you can turn on logging during the MSDE 2000 setup.
If the setup fails, locate the log file, and then search for any existence of "return value 3". A "return value 3" is the fatal error value that returns for an action. Based on the failed action, you can continue to determine the reason why your MSDE 2000 setup failed.
This table lists the command return code that is in the MSDE 2000 Setup log file.
Here is a list of custom actions that might fail when you install MSDE:
Collapse this tableExpand this table
Troubleshoot an Installation That is Embedded with MSDE 2000 as Merge ModulesMSDE 2000 is available as a set of Windows Installer merge modules, which can be used by independent software vendors (ISVs) to install an instance of the SQL Server 2000 Desktop Engine during their own setup process. These merge modules can be merged into the ISV setup program by using available Windows Installer setup development tools. MSDE 2000 merge modules are located in the Msm folder of your copy of the MSDE 2000 CD.
You can embed MSDE 2000 merge modules (.msm files) into a Windows Installer based setup application by creating your own .msi file. You can reduce the disk footprint of your application by customizing the MSDE 2000 Setup so that it does not install SQL Server 2000 components that are not used by your application. You can leave out the DMO*.msm files, Repl*.msm files, or both. These are merge modules for SQL-DMO and replication, respectively. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
299795For information about consuming MSDE into a custom application, read the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/299795/EN-US/ )INF: How to Author MSDE 2.0 Setup Packages with Microsoft Visual Studio Installer 1.1
325004For more information, visit the following Microsoft Web sites:
(http://support.microsoft.com/kb/325004/EN-US/ )HOW TO: Author MSDE 2000 Setup Packages by Using Visual Studio .NET
Embedding MSDE 2000 Setup Into Custom Applications SetupYou must add some internal properties in the Property table for the MSDE 2000 merged module. For example, you can add an entry in the Property table for INSTANCENAME, and then specify a name. You can add an entry for SECURITYMODE the same way. However, you must make these changes in the main installation package, and not in the SQL Server 2000 MSDE merge modules. You can map each of these properties to an internal property in the merge module by creating custom actions in the main MSI file. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
Embedding MSDE 2000 Setup into the Setup of Custom Applications
Integrating MSDE 2000 with your Applications
281983If you experience any technical issues when you create the setup package by using any third party software or authoring tools, please contact the third party software company for technical support.
(http://support.microsoft.com/kb/281983/EN-US/ )PRB: Cannot Specify Instance Name Using SQL Server 2000 Merge Modules
Upgrade MSDE 2000 to a Service Pack Level with a Microsoft Provided MSP Patch PackageIf you installed MSDE 2000 by using the original .msi file from Microsoft, you can upgrade the existing MSDE 2000 to a service pack level by applying the .msp patch file. You must first identify which .msi file the MSDE 2000 setup used. This is important because you must use a specific patch package (.msp) to apply service packs to the existing MSDE 2000 installation. For example, if you used Sqlrun01.msi to install the original MSDE 2000 files, you must use Sqlrun01.msp to upgrade it to Service Pack 2 (SP2). For Sqlrun02.msi, you must use Sqlrun02.msp and so forth.
NOTE: In SQL Server 2000 SP3, the file name is SqlRun01P.msp.
For more information, see the following article in the Microsoft Knowledge Base:
311762For example, you can run this command to upgrade MSDE 2000 to MSDE 2000 SP2 by using the parameters in a Setup.ini file, and enabling the verbose log that is named MSDE_upgrade.log:
(http://support.microsoft.com/kb/311762/EN-US/ )INF: How to Identify Which MSI File Was Used for an Existing MSDE Installation
D:\MSDE2KSP2\>setup.exe /settings D:\MSDE2KSP2\setup.ini /p SQLRUN /L*v C:\MSDE_upgrade.log
To specify a .msp file, you can use this:
D:\MSDE2KSP2\>setup.exe /settings D:\MSDE2KSP2\setup.ini /p D:\MSDE2KSP2\setup\sqlrun01.msp /L*v C:\MSDE_upgrade.log
NOTE: This example assumes that MSDE 2000 SP2 is installed on drive D.
NOTE: In SQL Server 2000 SP3, the file name is SqlRun01P.msp.
You can also disable rollback or enable the reinstall mode for troubleshooting the MSDE 2000 upgrade to a service pack level. For more information about ROLLBACK, REINSTALL and REINSTALLMODE, read the section of this article.
To avoid this error message when you try to upgrade MSDE 2000 to a service pack level on a computer that is running Microsoft Windows 98
Unable to run script files.
make sure that you use the UPGRADEUSER=sa parameter. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/303680/EN-US/ )PRB: SQL Srv. 2000 MSDE Service Pack 1 Setup on Windows 98 Fails
Upgrade MSDE 2000 Merge Modules to a Service Pack LevelYou can consider a minor upgrade in which you upgrade the MSDE 2000 merged modules to a service pack level. The upgrade changes the package code and the product version for a package that ships as a full product installation package or as a patch package. In a minor upgrade, the product code does not change. However, a minor upgrade cannot use a different volume label for the new version.
A change in the product version indicates that there is an order to the different updates for the same product. For example, if a patch exists to update version 9.0 to version 9.1, and another patch exists to patch version 9.1 to version 9.2, the installer can enforce the correct order by checking the product version before it applies the patch. This also prevents the version 9.2 patch from being applied to version 9.0. For patches, this ordering is enforced through the product version validation bits set in the transforms that are included in the patch package.
For additional information about how to create a patch file for theMicrosoft SQL Server 2000 Desktop Engine (MSDE 2000) sample.msi., click the article number below to view the article in the Microsoft Knowledge Base:
314131If you installed MSDE 2000 as merged modules with another custom application setup such as the Microsoft Application Center 2000 product, you must contact Microsoft Application Center 2000 for the availability of an upgrade package to upgrade your existing MSDE 2000 installation to a service pack level. For third-party custom applications that consume MSDE 2000 as merged modules, contact the custom application vendor for support.
(http://support.microsoft.com/kb/314131/EN-US/ )HOW TO: *Create Patch Files (Service Packs) For MSDE 2000 Sample
Article ID: 317328 - Last Review: March 29, 2007 - Revision: 2.2