MSDE 2000 Release A and Windows Installer

I am currently writing an installer for our product, which needs to incorporate MSDE 2000.
Previous versions of the MSDE install included merge modules (.msm files) that could be incorporated straight into a Windows Installer .msi file. However, the latest version (Release A) does not include the merge modules, and to top that, also states tha
t "Desktop Engine does not support nested installations. You must not call an .msi file from within another .msi file".
My questions are:
- How are we supposed to install MSDE when we are distributing .msi files? We need .msi functionality for other components of our install, so using a non-Windows Installer technology is not an option. Do we need to ask our users to install MSDE separat
ely (ouch)?
- Why did the merge modules disappear? I thought that these were the Microsoft-sanctioned method for installing runtime components...
- Are there any other options - we want to distribute a single file, and we really don't want to have to mix and match .msi and other setup technologies...
Marc Durdin
Software for Specialists
Hi Andy,
Thanks for the comment. However, this page is not up to date. It recommends using the merge modules... which are not supported any more by Microsoft (and are not even included in the latest release of MSDE). Any other suggestions?
Regards,
Marc

MSDE 2000 Install Problem

Hi
I am trying to install MSDE 2000 sp3 on a Windows XP that has had a previous
installation in the past. The previous installation has been removed, but
when I try installing MSDE again from the command prompt, it starts to set
up the gives me an error saying installation failed.
I have deleted the Microsoft SQL Server directory from Program Files,
cleaned out all registry entries for the instance name and have run the
install using the following command:
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1
SAPWD=<password>
Obviously replacing <password> with an appropriate password.
Are there any other known issues that anyone knows that will get this
installation working? Any advice would be appreciated.
Regards
Jason
hi Jason,
please add the
/L*v 'c:\...\log.txt'
parameter, in order to get a 2mb log file for the installation, where you
can search for
"value 3"
as error indication
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE - Multiple versions coexist?

While setting up for HP Insight Manager...
Microsoft provided documentation is leading me to believe that MSDE 2000 SP3
and previous versions of MSDE could coexist on one box.
Is that true?
I installed MSDE 2000 SP3 on one of my servers which had a previous MSDE
version with existing active databases. The result was that though databases
were still running, I had difficulty seeing the certain databases through
Enterprise Manager.
hi,
"mahlerdw" <mahlerdw@.hotdeleteme.com> ha scritto nel messaggio
news:O7wPFHaoEHA.2032@.TK2MSFTNGP10.phx.gbl
> While setting up for HP Insight Manager...
> Microsoft provided documentation is leading me to believe that MSDE
> 2000 SP3 and previous versions of MSDE could coexist on one box.
> Is that true?
> I installed MSDE 2000 SP3 on one of my servers which had a previous
> MSDE version with existing active databases. The result was that
> though databases were still running, I had difficulty seeing the
> certain databases through Enterprise Manager.
yese , up to 16 instances of SQL Server 2000 and MSDE 2000 at different
service pack level can coexist on the same box.
1 instance will be the default instance, locally available as "(local)" or
generally available as "ComputerName", while all other instances will be
named instances, reachable with teir complete name, made up by the computer
name and instance name, in the form "ComputerName\InstanceName"
what kind of problem are you facing?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I have a server running MSDE and two existing databases or instances. I am
uncertain of the version or how to determine the version.
I'm installing HP Insight manager, which requires MSDE 2000, SP3. I
installed MSDE 2000, SP3 and created the new instance for Insight Manager.
The application worked and the existing databases/instances were accessible
and continued to work.
A few days later, an Programmer/Administrator was trying to
monitor/manipulate one of the previously existing databases via Enterprise
Manager and noticed he could not see it the applications utilizing the
databases worked fine.
I uninstalled the MSDE 2003. The Programmer/Administrator then was able to
monitor/manipulate the previously existing databases via Enterprise Manager.
I'm not certain my explanation is clear. Any help you can provide is
appreciated.
DWM
[vbcol=seagreen]
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rgrn3F1ad8ggU1@.uni-berlin.de...
> hi,
> what kind of problem are you facing?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
|||hi,
"mahlerdw" <mahlerdw@.hotdeleteme.com> ha scritto nel messaggio
news:%23$d0IXkoEHA.3464@.tk2msftngp13.phx.gbl
> I have a server running MSDE and two existing databases or instances.
> I am uncertain of the version or how to determine the version.
> I'm installing HP Insight manager, which requires MSDE 2000, SP3. I
> installed MSDE 2000, SP3 and created the new instance for Insight
> Manager. The application worked and the existing databases/instances
> were accessible and continued to work.
> A few days later, an Programmer/Administrator was trying to
> monitor/manipulate one of the previously existing databases via
> Enterprise Manager and noticed he could not see it the applications
> utilizing the databases worked fine.
> I uninstalled the MSDE 2003. The Programmer/Administrator then was
> able to monitor/manipulate the previously existing databases via
> Enterprise Manager.
> I'm not certain my explanation is clear. Any help you can provide is
> appreciated.
actually there's no reason for that... all instances can be running
(resources allowing it) with no consequences...
each instace will have it's onw TCP address , provided by the service
listening on UDP 1434 port..
check the services (SQL Server services) are running and address each
instance with it's correct name (full name for named instance)
I do not know HP Insight manager, so I'm not able to provide fupport for
that tool/application
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply