Redistributing MSDE and the .NET Framework
2003-05-19 15:41 Mon
Visual Studio .NET 2003 does not include Microsoft SQL Server Desktop Engine (MSDE). To download MSDE, go to http://go.microsoft.com/fwlink/?linkid=13962.
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR SA PASSWORD>
Modified the setup.ini file for a vanilla VSDOTNET install, zipped and put on web site as msde.exe.
Tested on KIRA (Windows XP) works. Unzips to an odd folder that you have to go track down…
Tested on Virtual PC Windows 98. Works. Install has some warts.
2003-05-12 11:57 Mon
Copied from MSDN’s “Installing MSDE”:
Installing the SQL Server Desktop Engine (MSDE)
During setup, you can choose to copy the installation files for MSDE to your computer; this gives you the option of manually installing MSDE at a later time.
Installing MSDE involves three steps:
- Setting a custom MSDE instance name. This step is optional.
- Running setup for MSDE.
- Starting the MSDE service.
You can skip the following procedure if you intend to use the default instance name, "VsdotNet2003".
To create a custom MSDE instance name
- On the Start menu, choose Run.
- In the Open box, type
c:\Program Files\Microsoft Visual Studio .NET 2003\Setup\MSDE\and then click OK. - Double-click the file
setup.inito edit the file in Notepad. - Replace
VSdotNET2003inINSTANCENAME=VSdotNETwith the instance name of your choice. - On the File menu, choose Save and then choose Exit.
You can install MSDE simply by running the appropriate setup file from the location where Setup copied the file.
To install MSDE
- On the Start menu, choose Run.
- In the Open box, type
c:\Program Files\Microsoft Visual Studio .NET 2003\Setup\MSDE\and click OK. - Double-click the file
setup.exe.
After you have installed MSDE, you must then start the MSDE service.
To start the MSDE service
- On the Start menu, choose Run.
- In the Open box, type
NET START MSSQL$<instance name> and click OK.
For example, if you chose to use the default instance name, you would enter NET START MSSQL$VSdotNET2003.
2003-01-10 16:27
After upgrading to the MSDE SP3 .msm files:
1. These changes are still need.
After building a MSDE installer (.msi), you must edit the file with orca.exe (right click menu) to make the following changes:
InstallExecuteSequence table: 104->105,103->104,205->103,1525->6601
InstallUISequence table: 104->105,103->104,205->103
Property table:
Add Row SqlInstanceName = JobQuake
Add Row SqlProgramDir = c:\Program Files\JobQuake\
Add Row SqlSaPwd = KzSqlMsde
2. Don’t add these changes.
// Add Row SqlSecurityMode = SQL
// Add Row SqlDataDir = c:\Program Files\JobQuake Database\Data
Deploying .NET Applications: Lifecycle Guide
dotnetfx.exe requires
HOW TO: Obtain and Install SQL Server 2000 Desktop Engine (MSDE 2000) (includes requirements)
HOW TO: Connect to Microsoft Desktop Engine (for 98, must use SQL. sa initially blank)
Choosing and Using MSDE 2000 as the Database Engine for Your Application (links to using OSQL & backups using T-SQL)
Embedding MSDE 2000 Setup into the Setup of Custom Applications
Cannot Specify Instance Name Using SQL Server 2000 Merge Modules
HOW TO: Author MSDE 2000 Setup Packages by Using Visual Studio .NET
Run Setup.exe with /L*v [filename] for installation details logging. (*v is verbose logging, 10x the size. Try just /L first.)
HOWTO: Use the Orca Database Editor to Edit Windows Installer Files
This downloaded the Installer SDK 1.2 into c:\Program Files\MsiIntel.SDK, then ran the orca.msi in the tools directory.
To avoid 126 problem, modified the InstallExecuteSequence sequence numbers: 104->105, GetSqlState 103->104, StreamSupportFiles 206->103.
Didn’t see anything to fix in InstallUISequence.
Got new MSM files…..now the Setup project builds cleanly and the dependencies prior to the 1033 folder are complete. But it still fails….looks like the 126 bug.
InstallExecuteSequence InstallUISequence
GetSqlState 103 103
StreamSupportFiles 205 205
104->105, 103->104, 205->103
Now it complains about an invalid instance name…. so let’s try using Orca to add the guys below:
SqlInstanceName = JQ
Man it was looking so good! Then error code 2613….. turn on logging and look it up.
Called Dwayne Lanclos @ SQL Server Support…469-775-8400 he had an other persons case notes which said:
InstallExecuteSequence: Move RemoveExistingProducts (1525->6601) after InstallFinalize (6600) Note that this doubles up 6601, but it seems okay.
Putting the external properties below under an [Options] section in a Setup.ini file works when running setup.exe and also via Orca as internal property table entries.
It appends MSSQL$[SqlInstanceName] to the paths specified for SqlDataDir and SqlProgramDir.
The setup author could add an entry to the Property table by using a Windows Installer database editing tool such as Orca.exe to assign the specific internal properties used in the SQL Server 2000 MSDE merge modules to a specific value. For example, to set the instance name to be used, you would add an entry to the Property table and assign the SqlInstanceName property a specific value.
The following internal properties are used by the SQL Server 2000 MSDE merge modules and can be set in this manner. The corresponding external properties are listed for reference; however, they are available only in the SQL Server 2000 Desktop Engine install package, not the SQL Server 2000 MSDE merge modules.
External Property Internal Property
CALLBACK SqlCallback
COLLATION SqlCollation
DATADIR SqlDataDir [TargetDir]\Data
TARGETDIR SqlProgramDir [TargetDir]\Sql
INSTANCENAME SqlInstanceName JobQuake
SECURITYMODE SqlSecurityMode Sql
UPGRADE SqlUpgrade
UPGRADEUSER SqlUpgradeUser
Some of the above properties must be specific values. The value of SECURITYMODE or SqlSecurityMode should be SQL in order to allow SQL Server authentication. For upgrading, UPGRADE or SqlUpgrade should be 1, and UPGRADEUSER or SqlUpgradeUser should be SA.
STATUS
This behavior is by design.
REFERENCES
255905 HOWTO: Use Orca to Edit Windows Installer Files