How can I force a major upgrade to not switch to maintenance mode using the old installation package

Posted by Brian on Stack Overflow See other posts from Stack Overflow or by Brian
Published on 2010-04-29T17:32:19Z Indexed on 2010/04/29 17:37 UTC
Read the original article Hit count: 413

Filed under:

msi

|

major-upgrade

|

maintenance-mode

I have an installer that I would like to use for a major upgrade. I have done the following:

Increased the version number (from a.b.c to a.b.c+1)
Changed the ProductCode
Kept the same UpgradeCode
Made the appropriate entry in the Upgrade table
Changed the component ID of an existing component
Changed the name of the installer package
Changed the PackageCode

Basically I've done everything I can think of to force MSI to treat this as a major upgrade.

However, when I attempt to install this new package, the installer log says "Product registered: entering maintenance mode" and proceeds to try to find the old installer file (which fails, since the new installer is in a different folder than was used for the original installation, and wasn't even what I wanted to happen).

What am I missing? Why does the installer switch to maintenance mode right away rather than perform the major upgrade?

Thanks!

© Stack Overflow or respective owner

Related posts about msi

Error with SQL Server Setup 2012 on Windows 2012

as seen on Server Fault - Search for 'Server Fault'
I am trying to install SQL Server on Windows 2012. I was able to finally get the wizard up and running after making some changes on the server, but now it fails no matter what I do with the following error: TITLE: SQL Server Setup failure. SQL Server Setup has encountered the following error: … >>> More
Why does SQL 2005 SSIS component install fail?

as seen on Server Fault - Search for 'Server Fault'
I am trying to install SSIS on our production SQL 2005 SP2 box. Each time I try, the install/setup screen results in failure, starting with the native client, and moving on down. Screen shots below show what I see: Here is the result of clicking on the status link to the right of the native… >>> More
Wix - Upgrade always runs older installer msi and fails in trying to read old msi

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm having a problem though with the Windows caching of the installer. I'm trying to do an upgrade and each time the Windows installer is launching the installer of the older version. And when I do the upgrade it is complaining about problems with reading the older version's msi file (because its… >>> More
Java update/install via group policy

as seen on Server Fault - Search for 'Server Fault'
I trying to deploy the latest Java RE version via GP, Java 7 update 9. I want to update computers that are currently running an older version of Java, a mixture of 7.6 and 7.7, some computers are running versions as old as 6.31. Some are running a mixture of both. I would also like this GP to install… >>> More
What Every Developer Should Know About MSI Components

as seen on Geeks with Blogs - Search for 'Geeks with Blogs'
Hopefully nothing. But if you have to do more than simple XCopy deployment and you need to support updates, upgrades and perhaps side by side scenarios there is no way around MSI. You can create Msi files with a Visual Studio Setup project which is severely limited or you can use the Windows Installer… >>> More

Related posts about major-upgrade

WiX major upgrade refuses to replace existing file!

as seen on Stack Overflow - Search for 'Stack Overflow'
Hello! I have inherited this project with a WiX installer, and am required to make this version usefully upgrade the previous one! My problem comes in replacing the database files with new versions. No, the problem is not that they are locked, I can replace them manually, and in fact now ONE of… >>> More
Replacing unversioned files in WiX major upgrade.

as seen on Stack Overflow - Search for 'Stack Overflow'
I am still having this problem. This is the closest I have come to a solution that works, and yet it doesn't quite work. Here is (most of) the code: <Product Id='$(var.ProductCode)' UpgradeCode='$(var.UpgradeCode)' Name="Pathways" Version='$(var.ProductVersion)' Manufacturer='$(var.Manufacturer)' Language='1033'> … >>> More
Problem with WiX major upgrade!

as seen on Stack Overflow - Search for 'Stack Overflow'
Okay, my last question on this journey of WiX upgrades managed to get my settings file to be preserved! However, There is another component that is being preserved that I don't want to! I need it to overwrite, and it's not. The component "Settings" now works, with the NeverOverwrite="yes", and… >>> More
How can I force a major upgrade to not switch to maintenance mode using the old installation package

as seen on Stack Overflow - Search for 'Stack Overflow'
I have an installer that I would like to use for a major upgrade. I have done the following: Increased the version number (from a.b.c to a.b.c+1) Changed the ProductCode Kept the same UpgradeCode Made the appropriate entry in the Upgrade table Changed the component ID of an existing component Changed… >>> More
Prevent MSMQ queues from being removed and recreated during a major upgrade

as seen on Stack Overflow - Search for 'Stack Overflow'
I have an installer which creates MSMQ message queues. During a major upgrade I am noticing that the queues are getting removed and reinstalled. Any suggestions to avoid this from happening? I am currently scheduling remove existing products after InstallInitialize <RemoveExistingProducts After="InstallInitialize"/>… >>> More