dantoniuk
Posts: 3
Joined: Wed Sep 04, 2013 4:10 am

Patch created but won't install

I've been looking around the forums but can't seem to find an answer to my problem. I just upgraded to Enterprise (10.5) to use the patching feature, having been successfully creating regular installers for 3 years with AI. I followed the tutorial on creating patches - and the resulting patch managed to build with out any errors. It is the right size (the original install and the patched version are about 355 MB each, while the patch with three updated files is only about 2.7 MB).

When I run the patch.exe, I get the Setup Wizard Screen, and the Ready to Install screen, then as the patch moves to installing files I get the following message:
The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternative patch to a folder containing the installation package 'MyProduct.msi' in the box below.
I get this error on the authoring machine as well as other test machines. It almost looks like the patch uncompresses to a folder it does not have access to. I've been trying to solve this for days. Any ideas?

Thanks,
David
dantoniuk
Posts: 3
Joined: Wed Sep 04, 2013 4:10 am

Re: Patch created but won't install

I just found this in the patch documentation, which might explain what my problem is:
Note that, when applied, the patch will request the original MSI package (because, by default, the bootstrapper deletes the extracted files). In order to avoid this problem, select the option "Do not delete extracted MSI and CAB files" in the Media page, "Bootstrapper" tab.
But in AI 10.5 (build 52704), the Bootstrapper tab of the Patch Project no longer has this "Do not delete extracted MSI and CAB files" option. Does anyone have any idea how do you now prevent the Patch from looking for the original package in order to delete the extracted files?
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Patch created but won't install

Hello David and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

Please keep in mind that a patch can run only against its target installation package. So, if the target MSI doesn't exist on target machine (or isn't cached) when running the patch you will be prompted to supply the MSI file. However, in order to avoid this behavior you can build your target installation package as an EXE package type and enable (in the target installation project) the "Do not delete extracted MSI and CAB files" option from "Builds -> Configuration tab -> Bootstrapper Options" group.

Also, you can take a look on our "Why does the .msp installation requirs original .msi" thread which debates a similar issue.

If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
dantoniuk
Posts: 3
Joined: Wed Sep 04, 2013 4:10 am

Re: Patch created but won't install

Daniel,

If I understand you, I would have to select the "Do not delete extracted MSI and CAB files" option from "Media" on the original install. But the installer I am trying to patch has already shipped (on a DVD-ROM) and is also quite large (350-700 MB, depending on the configuration).

So it looks like I can not use the "patch" feature on my current, already shipping, product. And I am not sure I want my future users to have to have a backup 700 MB MSI and CAB file, which duplicates the 700 MB installed program, just in case they need to update a few MB of files.

I did find another solution on the forum last night that I am experimenting with, even if it is not ideal. Does this seem like the best way to update a few files?
There is another manual way to perform an upgrade similar to the patch but it is not recommended and the version will not be increased for your product on the target machine. For example here are the steps to upgrade a file:
- create a new project
- perform a search from the Search page for that file on the target machine
- set the application folder to the search name
- perform a file removal operation on that file ( here is how )
- add the upgraded file in the application folder in the files and folders page
- in the Product Details page disable the "Register product with Windows Installer" option

All the best,
Mihai
Thanks,
David
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Patch created but won't install

Hello David,
If I understand you, I would have to select the "Do not delete extracted MSI and CAB files" option from "Media" on the original install.
Yes, this is correct.
I did find another solution on the forum last night that I am experimenting with, even if it is not ideal. Does this seem like the best way to update a few files?

There is another manual way to perform an upgrade similar to the patch but it is not recommended and the version will not be increased for your product on the target machine. For example here are the steps to upgrade a file:
- create a new project
- perform a search from the Search page for that file on the target machine
- set the application folder to the search name
- perform a file removal operation on that file ( here is how )
- add the upgraded file in the application folder in the files and folders page
- in the Product Details page disable the "Register product with Windows Installer" option
As my colleague already mentioned in the above thread this is not a recommended approach. However, you can try to implement this workaround for your scenario and see if it helps.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”