MSDE 2000 SP3a merge modules - upgrade problem

MSDE 2000 SP3a merge modules - upgrade problem

Post by Venkat » Wed, 04 Jun 2003 22:52:43


I have an application that has installed MSDE 2000 SP3 using the
merge modules as part of the app. MSI install. I am trying to wrap
the merge modules for MSDE SP3a as an upgrade for that package.

The install goes through and finally aborts with an error. The
MSI log file has:
Running script :
-n -b -d master -SHOSTNAME -i "C:\Program Files\Microsoft SQL
Server\MSSQL\Install\upgrade.sql" -o "C:\Program Files\Microsoft SQL
Server\MSSQL\Install\upgrade.out" -E
Query execution failed
C:\Program Files\Microsoft SQL Server\MSSQL\Install\upgrade.sql
C:\Program Files\Microsoft SQL Server\MSSQL\Install\upgrade.out
Exit Code = 1
Failed on call to UpgradeMaster
Falied on call to UpgradeDatabases

The file upgrade.out has:
[Shared Memory]General network error. Check your network
[Shared Memory]ConnectionRead (recv()).

Has anybody seen this problem before? Is there a workaround?



1. MSDE 2000 merge modules on machines where MSDE is already installed

I have created a Windows Installer package (with InstallShield for Windows
Installer) which includes the MSDE 2000 merge modules.

For a new installation of my company's product, everything works fine.

However, if I create an updated package, containing a new version of the
product, and try to install this on a machine, where MSDE is already
installed, then I run into problems.

At first, I was getting the error message "The instance name specified is
invalid". I have got rid of this by removing the custom action
"DetectInstanceClash" from SqlBase.msm. (Of course, this may have side
effects which I am not aware of!)

I am specifying an instance name.
I have a custom action which detects if my instance of MSDE is installed,
which I can easily extend to set properties etc.

I have tried setting the properties SqlUpgrade/SqlUpgradeUser, also setting
the property SQLMSDEInstalled and clearing the property SQLMSDESelected, but
so far have not found any combination which works.

Has anybody managed to create a package which would update their own product
without affecting an existing MSDE installation?


2. query cannot be executed because some files are either missing or not registered

3. MSDE 2000 SP2 Merge Modules Problem w/ ODBC Data Source

4. Did you use E-R modelling for your database design ?

5. MSDE 2000 Merge Module installation problem


7. MSDE 2000 Install problem from Merge Modules

8. Is there a decent relational database for the Macintosh?

9. MSDE 2000 installation on Windows 2000 SP2 Professional using Windows Installer Merge Modules from SP1

10. MSDE 2000 Beta 2 installation fails using MSM merge modules

11. MSDE 2000 merge module install (MSI/InstallShield)

12. MSDE 2000 Merge Modules in InstallShield 7.02 Project

13. MSDE-2000 SP1 Merge Modules