Need help understanding patching / autoupdates - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

vulgrin
Posts: 40
Joined: Fri Jan 11, 2008 9:49 pm

Need help understanding patching / autoupdates

Ok, I'm evaluating Advanced Installer and I need to figure out how to perform the following scenario:

1. User downloads the MSI from our site and installs the software.
2. User's software checks for updates - or they click to check for updates. (We plan on integrating the update check on launch of the app.)
3. User downloads a patch MSP and has it applied to the software. (Eventually we might also have full fledged upgrades, but I'll ignore those for now.)

I've built a small test app to try this out, that simply displays the current EXE's version number. I can get #1 to work fine, and #2 is finding the update and apparently downloading it fine. However, when the updater goes to run the MSP, I get a windows installer error:

"The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch."

Now, I'm sure I did NOT tell it to update the product code. Tested it twice to be sure. In fact, if it helps, here is how I'm doing this process:

1. Create my EXE with version 1.0.0 stamped on it
2. Create my AIP project, set it up to store everything in the MSI, and set its version to 1.0.0. I build the project and stuff it into a 1.0.0 folder
3. Change my EXE to version 1.0.1
4. Go back to my original AIP project, change the version to 1.0.1 and tell it to keep the product code. Generate the MSI and stuff that into a 1.0.1 folder.
5. Create a new Patch project, give it the paths to the two MSIs, fill in the details on where to put the patch, and give it the name of my product, etc. Put that MSP into a "Patches" folder.
6. Created a Updates.txt file per the example where I specify the location of the patch, the size, tell it to check my EXE for version 1.0.1.
7. I put everything up on my web server.
8. I go to a test machine, go to the page and download and run the 1.0.0 MSI. Test the EXE and it says version 1.0.0
9. I run the Updater /checknow. It says there is an update, I tell it to install it.
10. I get the error message I specified.

Any ideas on what I'm doing wrong? Let me know if you need more information, or if I'm going about this all wrong.

Thanks
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,

I'm not sure why you are encountering this behavior because, from what you explained, everything is configured correctly.

The problem is most likely caused by the patch project. Please try it without using the Updater (install the 1.0.0 version and run the patch). If you get the same error please send us the AIP of the patch project to support at advancedinstaller dot com so we can investigate it.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
vulgrin
Posts: 40
Joined: Fri Jan 11, 2008 9:49 pm

Yeah, I tried that already, thinking the same thing - I get the exact same error message. Which is what led me to believe that the updater was working fine, but that the MSP was bad.

I will send both of my AIPs to you here shortly. Thanks!
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi Dave,

We investigated the AIPs you sent and there seems to be no problem. What version of Windows SDK are you using?

This problem may occur if you are using an older version of "msimsp.exe" (which comes with the Platform SDK). On Vista, you should use the Windows SDK which can be downloaded from the following page:
http://www.microsoft.com/downloads/deta ... laylang=en

If the problem persists and can be reproduced with the latest SDK installed, please send a simple test case (AIP files, the necessary resources and the resulted MSI and MSP files) that reproduces this problem.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”