MSDE instance setup question

I needed to distribute the MSDE components to the computers that use my
software so I decided to build a setup program using InstallShield that
included the MSDE files.
After I ran the installation, I noticed that the setup created a folder on
my computer using the MSDE instance name I told the setup program to used
prefixed by a "$" character. So the folder created for an instance named
such as MACHOGRANDE was "C:\Program Files\Microsoft SQL
Server\MSSQL$MACHOGRANDE"
After noticing that, I went on to explore this folder and notice that it had
a bunch of files in it, I was surprised to see that one of the files was
named sqlservr.exe! It almost looked like the installation of my MSDE
instance was like a totally independent sql server installation! Like if it
had nothing to do with the other MSDE instance I had running. I doubt this
is the case since I am pretty sure there must be a gazzilion other files
installed on the computer that are sheared by all the database that use the
MSDE engine.
So my question is,
1. Why did the instance of MSDE crated all of this extra files (such as
sqlservr.exe)? Instead of simply created the ldf and mdf files like a
regular SQL server database? Aren't the MSDE and SQL server supposed to be
the same thing?
2. Also is there a special reason for the "$" character"?
Thanks
Hi Rene,
Welcome to use MSDN Managed Newsgroup!
[vbcol=seagreen]
be[vbcol=seagreen]
The SQL Server 2000 Desktop Engine (MSDE 2000) is a redistributable version
of the SQL Server relational database engine. MSDE 2000 is designed to be
distributed as a part of applications that require a local data store.
Software developers can code the setup of their application to install an
instance of MSDE 2000 and build a database to be used by the application.
The application is then coded to perform any needed administration of that
database and instance of MSDE 2000, and to use the data in the database to
store application data.
The main component in MSDE 2000, the database engine, provides for the
storage of data. MSDE 2000 includes a version of the SQL Server 2000
database engine tailored to run on a notebook or desktop client computer,
operating as the local data store for an application supporting one user or
a small workgroup of users. The database engine included in MSDE 2000
includes most of the functionality of the database engine included in the
other editions of SQL Server 2000. But it does not include some features
used in large production databases, such as parallel queries and indexed
views. For more information about the database engine features supported by
MSDE 2000
For more information, you are encouraged to check following topic in the
Books Online / MSDN Online
Understanding SQL Server 2000 Desktop Engine (MSDE 2000)
http://msdn.microsoft.com/library/de...us/architec/8_
ar_ts_67ax.asp
What are the limitations of MSDE?
http://www.aspfaq.com/show.asp?id=2343
[vbcol=seagreen]
For all named instances, it will be identified as MSSQL$<instance name>.
SQL Server 2000 supports multiple instances of the SQL Server database
engine running concurrently on the same computer.
All instances of the database engine other than the default instance are
identified by an instance name specified during installation of the
instance. Applications must provide both the computer name and the instance
name of any named instance to which they are attempting to connect. The
computer name and instance name are specified in the format
computer_name\instance_name.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

MSDE Installation Error on Win9x

I am installing MSDE on win 9x machines and am having a problem. The installation aborts and the installshield unattend.iss script rolls back the installation. It seems the failure is in the cnfgsvr.exe program (based on the sqlstp.log file).

the command line that I use is:
msdex86 -s -a -f1 "c:\unattend.iss"

The log files sqlstp.log and cnfgsvr.out are included below.

I have seen some postings similar to this, but never a resolution. Any help would be appreciated...

Here are the log files...

Sqlstp.log file
~~~~~~~~~~~~~~~~~~~sqlstp.log~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~
13:53:56 Begin Setup
13:53:56 7.00.623
13:53:56 Mode=Silent
13:53:56 ModeType=NORMAL
13:53:57 ValueFTS returned: 0
13:53:57 ValuePID returned: 0
13:53:57 ValueLic returned: 0
13:53:57 GetDefinitionEx returned: 0, Extended: 0x0
13:53:57 System: Windows 95
13:53:57 SQL Server ProductType: MSDE [0x4]
13:53:57 Begin Action: SetupInitialize
13:53:57 End Action SetupInitialize
13:53:57 Fixed install: 0
13:53:57 Begin Action: CheckRequirements
13:53:57 Platform ID: 0xf0000
13:53:57 Version: 4.0.67109975
13:53:57 DCOM95 has been detected.
13:53:57 File Version - C:\WINDOWS\SYSTEM\shdocvw.dll: 5.50.4134.600
13:53:57 ComputerName: JMCGUIRE1
13:53:57 User Name: cbauerle
13:53:57 Domain: JMCGUIRE1
13:53:57 OS Language: 0x409
13:53:57 End Action CheckRequirements
13:53:57 Begin Action: Detection
13:53:57 End Action Detection
13:53:57 Begin Action: ODBCLocked
13:53:57 C:\WINDOWS\TEMP\_ISTMP0.DIR\odbcinst.exe -IsLocked -Silent 1 -SourceDir C:\WINDOWS\TEMP\PFT234~1\X86\ODBC -LogFile C:\WINDOWS\sqlodbci.log
13:53:58 Process Exit Code: (-1)
13:53:58 End Action ODBCLocked
13:53:58 This combination of Package and Operating System allows a full product install.
13:53:58 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
13:53:58 CommonFilesDir=C:\Program Files\Common Files
13:53:58 Windows Directory=C:\WINDOWS\
13:53:58 Begin Action: ShowDialogs
13:53:58 Begin Action: DialogShowSdWelcome
13:53:58 End Action DialogShowSdWelcome
13:53:58 Begin Action: DialogShowSdLicense
13:53:58 End Action DialogShowSdLicense
13:53:58 Begin Action: DialogShowSdRegisterUserEx
13:53:58 End Action DialogShowSdRegisterUserEx
13:53:58 Begin Action: DialogShowSdSetupType
13:53:58 [SetupTypeSQL]
13:53:58 Result=302
13:53:58 szDir=C:\MSSQL7
13:53:58 final szDir=C:\MSSQL7
13:53:58 szDataDir=C:\MSSQL7
13:53:58 final szDataDir=C:\MSSQL7
13:53:58 End Action DialogShowSdSetupType
13:53:58 Begin Action: DialogShowSdComponentMult
13:53:58 End Action DialogShowSdComponentMult
13:53:58 Begin Action: DlgCpSortUnicode
13:53:58 Result=1
13:53:58 [DlgCpSortUnicode]
13:53:58 SortId=52
13:53:58 LCID=1033
13:53:58 CompStyle=196609
13:53:58 End Action DlgCpSortUnicode
13:53:58 Begin Action: DlgNetwork
13:53:58 Result=1
13:53:58 [DlgServerNetwork]
13:53:58 NetworkLibs=4095
13:53:58 TCPPort=1433
13:53:58 TCPPrxy=
13:53:58 NMPPipeName=\\.\pipe\sql\query
13:53:58 End Action DlgNetwork
13:53:58 Begin Action: DlgServices
13:53:58 [DlgServices]
13:53:58 Result=1
13:53:58 Local-Domain=3855
13:53:58 AutoStart=61455
13:53:58 End Action DlgServices
13:53:58 Begin Action: DialogShowSdStartCopy
13:53:58 End Action DialogShowSdStartCopy
13:53:58 Begin Action: DlgCPLLicense
13:53:58 End Action DlgCPLLicense
13:53:58 End Action ShowDialogs
13:53:58 Begin Action ProcessBeforeDataMove:
13:53:58 DeinstallStart returned (C:\MSSQL7): 0
13:53:58 End Action ProcessBeforeDataMove:
13:53:58 Begin Action ProcessComponentSelection:
13:53:58 End Action ProcessComponentSelection
13:53:58 Begin Action LogSelectedComponents:
13:53:58 SQLProg
13:53:58 SQLProg\SQLServr
13:53:58 SQLProg\SQLServr\Help
13:53:58 SQLProg\SQLServr\SCMDev
13:53:58 SQLProg\SQLServr\SCMDev\SCMh
13:53:58 SQLProg\SQLServr\SCMDev\SCMX86Lb
13:53:58 SQLProg\SQLServr\SCMDev\SCMALb
13:53:59 SQLProg\ReplSupp
13:53:59 SQLProg\ReplSupp\ReplSys
13:53:59 SQLProg\ReplSupp\ReplSys1
13:53:59 SQLProg\ReplSupp\RepComm
13:53:59 SQLProg\Dat
13:53:59 SQLProg\BaseSys
13:53:59 SQLProg\BaseBinn
13:53:59 Core
13:53:59 CoreSys
13:53:59 ODBC
13:53:59 OLEDB
13:53:59 CoreMisc
13:53:59 Jet
13:53:59 NetCore
13:53:59 CoreInst
13:53:59 Core1033
13:53:59 CoreIntl
13:53:59 CrMi1033
13:53:59 CrMiIntl
13:53:59 SysCore
13:53:59 VOLEDB
13:53:59 VODBC
13:53:59 CrRepCom
13:53:59 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
13:53:59 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
13:53:59 End Action LogSelectedComponents
13:54:00 SQL program folder: C:\MSSQL7
13:54:00 SQL data folder: C:\MSSQL7
13:54:00 Windows system folder: C:\WINDOWS\SYSTEM\
13:54:00 Prog req: 15751, Data req: 20447, Sys req: 4433
13:54:00 Prog avail: 792068, Data avail: 792068, Sys avail: 792068
13:54:00 Prog req vs. avail, 40631, 792068
13:54:00 Data req vs. avail, 20447, 792068
13:54:00 Sys req vs. avail, 24880, 792068
13:54:00 DisplaySystemPreReq
13:54:00 Begin Action MoveFileData:
13:54:32 End Action MoveFileData
13:54:32 Begin Action ProcessAfterDataMove:
13:54:32 DeinstallSetReference (C:\MSSQL7\sqlservr.exe) returned: 0
13:54:32 End Action ProcessAfterDataMove
13:54:32 Begin Action InstallPkgs:
13:54:32 Setup is installing Microsoft Data Access Components (MDAC) ...
13:54:32 C:\WINDOWS\TEMP\pft2344~TMP\x86\Other\mdac_typ.exe /q:a /c:"setup.exe /qtn"
13:55:44 Process Exit Code: (3010)
13:55:44 Setup is installing Microsoft Distributed Transaction Coordinator (MSDTC) ...
13:55:44 C:\WINDOWS\TEMP\pft2344~TMP\x86\Other\dtcsetup.exe /q:a /r:n
13:56:04 Process Exit Code: (0)
13:56:04 End Action InstallPkgs
13:56:04 Begin Action BuildServer:
13:56:04 SetNewPath returned: 3010
13:56:04 Path successfully updated.
13:56:04 C:\MSSQL7\binn\cnfgsvr.exe -Silent 1 -NoSampleDB 1 -SQLPath "C:\MSSQL7\" -SQLDataPath "C:\MSSQL7\" -SortID 52 -LCIDCompStyle "1033-196609" -HWND 732 -User sa -Pwd
13:58:14 Process Exit Code: (-1)
13:58:14 Setup failed to configure the server. Refer to the server error logs and cnfgsvr.out for more information.
13:58:14 Action CleanUpInstall:
13:58:14 C:\WINDOWS\TEMP\_ISTMP0.DIR\scm.exe -Silent 1 -Action 4 -Service SQLServerAgent
13:58:14 Process Exit Code: (0)
13:58:14 Installation Failed.
~~~~~~~~~~~~~~~end sqlstp.log~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

cnfgsvr.out file
~~~~~~~~~~~~~~~~~~~cnfgsvr.out~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~
Starting Service ...

Connecting to Server ...

driver={sql server};server=JMCGUIRE1;UID=sa;PWD=;database=mast er

[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).

driver={sql server};server=JMCGUIRE1;UID=sa;PWD=;database=mast er

[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).

driver={sql server};server=.;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (Connect()).

SQL Server configuration failed.
~~~~~~~~~~~~~~~end cnfgsvr.out~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~I am able to easily reproduce the error with the following steps:

1. Install WIN95b
2. Install IE5.5
3. Install MDAC 2.6SP1
4. Install MSDE

MSDE does not install on a win95 machine that has MDAC installed.

If I install MSDE, then MDAC it is OK.

Any thoughts??