Installing MSDE on different plattforms.

Product
Our product is developed in Visual Studio .NET using MFC and .NET.
It connects to a MS SQL Server Desktop Edition (MSDE), where the data is
stored.
Installation
Our problems relates to the installation of our product.
Installation happens in these steps:
- Install .NET
- Install MSDE2000 (with a SA password we have chosen)
- Reboot
- Start our own InstallDB.exe which does the follwoing:
-- Connects to the MSDE (the master database)
-- creates our own database (called "exordb" and creates our own sql
user called "exor")
-- Connects again to MSDE using the exor user and loads data into the
exordb database.
We are using the following connectionstring for connecting to master db the
first time.
Data Source=127.0.01; Integrated Security=SSPI;Initial Catalog=master
We are considering to use this one instead:
server=127.0.0.1;uid=sa;pwd=****;database=master
after the exordb is set up we connect using
server=127.0.0.1;uid=exor;pwd=***;database=exordb
Problems
1. (the most critical)
Installation failes (the first connection string) for some customers with XP
SP2 even if they turn off the firewall.
They get the standard SQLServer Exception:
SQL Server does not exist or access denied.
The MSDE is there (unnamed instance) and is ON.
2. (Windows 98)
When installed on Windows98 MSDE does not start automatically after the
reboot, at least that what it seems on the WIndows 98 machine we have tested
on. (We have also discovered that only SQL Autentification works on Win98,
we solved that by using the second connection string instead of the first
one).
3. (manual start of MSDE)
How may we detect (in our code, preferrably .NET/C#) that MSDE is not
running and how do we start it from the code?
4. (MSDE installed by someone else)
If MSDE is already installed on the computer by another program and
SQL-authentification is not set, how may we set it so our connection string
will work.
hi Vilhelm,
Vilhelm wrote:
> Product
> Our product is developed in Visual Studio .NET using MFC and .NET.
> It connects to a MS SQL Server Desktop Edition (MSDE), where the data
> is stored.
> Installation
> Our problems relates to the installation of our product.
> Installation happens in these steps:
> - Install .NET
> - Install MSDE2000 (with a SA password we have chosen)
> - Reboot
> - Start our own InstallDB.exe which does the follwoing:
> -- Connects to the MSDE (the master database)
> -- creates our own database (called "exordb" and creates our own
> sql user called "exor")
> -- Connects again to MSDE using the exor user and loads data into
> the exordb database.
>
> We are using the following connectionstring for connecting to master
> db the first time.
> Data Source=127.0.01; Integrated Security=SSPI;Initial
> Catalog=master
> We are considering to use this one instead:
> server=127.0.0.1;uid=sa;pwd=****;database=master
> after the exordb is set up we connect using
> server=127.0.0.1;uid=exor;pwd=***;database=exordb
> Problems
> 1. (the most critical)
> Installation failes (the first connection string) for some customers
> with XP SP2 even if they turn off the firewall.
> They get the standard SQLServer Exception:
> SQL Server does not exist or access denied.
> The MSDE is there (unnamed instance) and is ON.
I'm trying to get some more material about that kind of issue on XP sp2 to
report it to Microsoft representative... but I am unable to repro it in my
tests.. I'm aware of another issue on XP sp2 which cause installation
failure due to MDAC stack troubles, currently with no workaround as no MDAC
2.8 xp sp2 refresh is available... please forward me more info, if you
like..

> 2. (Windows 98)
> When installed on Windows98 MSDE does not start automatically after
> the reboot, at least that what it seems on the WIndows 98 machine we
> have tested on.
it's correct... MSDE runs as a standard application on Win9x platform as it
does not support service mode..
you should check that the service manager is added in the autostart folder
and that the "Autostart service when OS starts" check box is checked ..
to start MSDE you can call the SQL Server Service Manager as following:
(named instance)
scm.exe -Action 1 -Silent 1 -Service MSSQL$InstanceName
(default Instance)
scm.exe -Action 1 -Silent 1 -Service MSSQLServer
please keep in mind that, on Win9x, MSDE path will not be added to
autoexec.bat if you don't reboot the
computer, so you have to rely on Win32 API like FindFirstFile or the like to
find where the scm.exe is (usually ..\Program Files\Microsoft SQL
Server\80\Tools\Binn\scm.exe)

>(We have also discovered that only SQL
> Autentification works on Win98, we solved that by using the second
> connection string instead of the first one).
MSDE installed on Win9x does not support integrated security

> 3. (manual start of MSDE)
> How may we detect (in our code, preferrably .NET/C#) that MSDE is not
> running and how do we start it from the code?
you can rely on SQL-DMO COM object...
you can then ping it like
dim oServer as SQLDMO.SQLServer2
objServer.PingSQLServerVersion
start it, or just connect...

> 4. (MSDE installed by someone else)
> If MSDE is already installed on the computer by another program and
> SQL-authentification is not set, how may we set it so our connection
> string will work.
you have to manually change the login authentication mode, logging in as
member of the server's sysadmin role and setting the
objServer.IntegratedSecurity.SecurityMode = SQLDMOSecurity_Mixed
or modify the Windows registry
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
LoginMode=2
(HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\InstanceName\MSSQLServer for
a named instance)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you a lot for some useful answers!!
More input on question 1.
I have not been able ot reproduce it here, but some of my customers report
this problem. Maybe we can resolve it with some well-phrased questions I can
ask one of my customers on the phone.
We use installshield Premier edition which installs MDAC 2.8 if necessary as
part of the installation process.
Vilhelm Heiberg
Norway.
"Andrea Montanari" wrote:

> hi Vilhelm,
> Vilhelm wrote:
> I'm trying to get some more material about that kind of issue on XP sp2 to
> report it to Microsoft representative... but I am unable to repro it in my
> tests.. I'm aware of another issue on XP sp2 which cause installation
> failure due to MDAC stack troubles, currently with no workaround as no MDAC
> 2.8 xp sp2 refresh is available... please forward me more info, if you
> like..
>
> it's correct... MSDE runs as a standard application on Win9x platform as it
> does not support service mode..
> you should check that the service manager is added in the autostart folder
> and that the "Autostart service when OS starts" check box is checked ..
> to start MSDE you can call the SQL Server Service Manager as following:
> (named instance)
> scm.exe -Action 1 -Silent 1 -Service MSSQL$InstanceName
> (default Instance)
> scm.exe -Action 1 -Silent 1 -Service MSSQLServer
> please keep in mind that, on Win9x, MSDE path will not be added to
> autoexec.bat if you don't reboot the
> computer, so you have to rely on Win32 API like FindFirstFile or the like to
> find where the scm.exe is (usually ..\Program Files\Microsoft SQL
> Server\80\Tools\Binn\scm.exe)
>
> MSDE installed on Win9x does not support integrated security
>
> you can rely on SQL-DMO COM object...
> you can then ping it like
> dim oServer as SQLDMO.SQLServer2
> objServer.PingSQLServerVersion
> start it, or just connect...
>
> you have to manually change the login authentication mode, logging in as
> member of the server's sysadmin role and setting the
> objServer.IntegratedSecurity.SecurityMode = SQLDMOSecurity_Mixed
> or modify the Windows registry
> HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
> LoginMode=2
> (HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\InstanceName\MSSQLServer for
> a named instance)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>

Installed SP4 - Version # okay but Product Level wrong?

I have the developer edition of MS SQL and applied SP4 to it. Here's what I get when I execute SELECT @.@.Version:

Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

According to the readme, here are the version numbers for each service pack:

SQL Server 2000 Version and Level@.@.VERSIONProduct LevelSQL Server 2000 Original Release8.00.194RTMDatabase Components SP18.00.384SP1Database Components SP28.00.534SP2Database Components SP3, SP3a or MSDE 2000 Release A.8.00.760SP3Database Components SP48.00.2039SP4

Do I trust the Version Number or the Product Level? Anyone know what the story is? TIA.

The numbers are TDS( tabular data stream) yes the increament is based on service packs in SQL Sever 2000 and in Win2k you are missing two service packs because I have a box in Houston running it and as of 2005 December I had SP4, I have installed the product that is SQL Server 2000 on all existing os including XP home. I also have SQL Server 2000 SP3 and SP3a in .sql files. So you just need two service packs for Win2k. Hope this helps.|||

Thanks Caddre. I didn't realize it was reporting the OS service pack as opposed to the SQL Server service pack. I'm aware I haven't applied the latest Windows SP - I'm deferring IE 7 for the moment.

|||

EDIT

(Windows NT 5.1 (Build 2600: Service Pack 2)

(SQL Server 2000 Original Release 8.00.194 RTM
Database Components SP1 8.00.384 SP1
Database Components SP2 8.00.534 SP2
Database Components SP3, SP3a or MSDE 2000 Release A. 8.00.760 SP3
Database Components SP4 8.00.2039 SP4)

It was reporting both because the first is for Win2k while the TDS number are for SQL Server 2000 Service Pack because it default to 80 and the extra numbers defines the service packs. One more thing build 2600 in Win2k is Advanced Server.

installation problems : product ID rejected

Hello,

Maybe is it a newbie question : it is the first time I install a SQL Server licence purchased with the eopen program.

My SQL server licence is a french one. I purchased the correct media kit.

During the installation, I am asked the name, and the company name but the product key is greyed with product id which begin with "RY62Q". I guess it is normal (?)

But later on, when it comes to installing SQL server itself, i get a message telling that my product ID is incorrect. (id : 28021; event type : sqlca\sqlcax.cpp@.DetectProductID@.DetectProductID@.x6d75).

I tried dozens of times :

-with another admin account

-after cleaning up the temp and program files subdirectories

-after cleaning up the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server,HKEY_LOCAL_MACHINE\Software\Microsoft\MSFTESQLInstMap; there was nothing anyway)

If it helps, I first try the installation from a wrong media. As I had no key, I went not far away.

I did received the authorisation number etc from Microsoft but I have no clue of what have to do from that.

As you understood, any help would be appreciated.

It is solved. I am really not sure how, but it solved.

I was about to reinstall the server. As it is a remote server, I had to upload the cds. In order not to have to do it again, I moved the cds to another partition. Just to be sure, I tried once again the installation...and it worked. The only possible cause I see is that the installation program detected a subfolder named "sql2005_cd1"(with a wrong media) in the same folder as my "newsql2005_cd1" (which actually contained the correct media). Maybe it is a dummy anti-piracy system, don't know...but now it worked and I am happy

installation fails on xp home - failed to configure server

Hi,
First I attemtped to upgrade MSDE to sp4, and I got the error
"This product is not installed",
So I removed the installation of MSDE and just installed sp4 directly. But
when I do, I get the error
"Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (A4!4C) [12:01:18:241]: Product: Microsoft SQL Server Desktop Engine
(VLM) -- Setup failed to configure the server. Refer to the server error
logs and setup error logs for more information."
The only other line in the log that metions a failure is
Setting SqlEdition property failed
The installer then backs everthing out and removes the service. The service
was already installed and running at that point.
I am using SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE to install,
Thanks,
Brian
hi Brian,
msnews.microsoft.com wrote:
> Hi,
> First I attemtped to upgrade MSDE to sp4, and I got the error
> "This product is not installed",
> So I removed the installation of MSDE and just installed sp4
> directly. But when I do, I get the error
> "Setup failed to configure the server. Refer to the server error logs
> and setup error logs for more information.
> MSI (s) (A4!4C) [12:01:18:241]: Product: Microsoft SQL Server Desktop
> Engine (VLM) -- Setup failed to configure the server. Refer to the
> server error logs and setup error logs for more information."
> The only other line in the log that metions a failure is
> Setting SqlEdition property failed
> The installer then backs everthing out and removes the service. The
> service was already installed and running at that point.
> I am using SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE to install,
this usually means you did not comletely uninstall MSDE (not your fault,
just MSDE fault :D)
I succesfully cleared my registry and file system following
http://support.microsoft.com/default...b;en-us;290991 KB article
adiveces but the Windows Installer entries, that can be cleared using the
Windows Installer SDK tool Msizap.exe as per
http://support.microsoft.com/default...b;en-us;320873 (never tried)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Got it fixed.
To get it to work I did the following:
1. Intalled a default instance. I had removed it as well. That worked.
2. re-registering sqldmo.dll. I did this because DbaMgr got an automation
error when connecting to the default instance
3. Installed the named instance I wanted. This time it worked.
Notes:
The error I was getting was
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error.
Check your network documentation.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()).
Things learned along the way:
1. If the install fails, then enable verbose logging with /L*v
C:\MSDELog.log. Look in the log when its finished for what failed. When you
get the error message box, LEAVE IT THERE, and go look at the log. The last
thing it did is the last line.
2. If you get the error "Unable to configure server", then look in the file
cnfgsvr.out. It will be in C:\Program files\Microsoft SQL
Server\MSSQL$<instancename>\Inatall (assuming drive c)
3. To clean manully to get the installer to resintall completely if a
partial install is left on the system:
- Run Windows Installer SDK tool Msizap.exe as per
http://support.microsoft.com/default...b;en-us;320873
The command is MSIZAP.EXE" T {product code}. The product code can be
found in the install log (C:\MSDELog.log in the example above). The product
code for MDSE service pack 4 was
{E09B48B5-E141-427A-AB0C-D3605127224A} so I ran
MSIZAP.EXE" T {E09B48B5-E141-427A-AB0C-D3605127224A}
- Manually delete the folder C:\Program Files\Microsoft SQL Server\MSSQL
or C:\Program Files\Microsoft SQL Server\MSSQL$<instancename>. Make sure you
look at cnfgsvr.out first if you need too!
Brian
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3s9k91Fn804jU1@.individual.net...
> hi Brian,
> msnews.microsoft.com wrote:
> this usually means you did not comletely uninstall MSDE (not your fault,
> just MSDE fault :D)
> I succesfully cleared my registry and file system following
> http://support.microsoft.com/default...b;en-us;290991 KB article
> adiveces but the Windows Installer entries, that can be cleared using the
> Windows Installer SDK tool Msizap.exe as per
> http://support.microsoft.com/default...b;en-us;320873 (never
> tried)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>