Our compressed installation cannot find the MSI when modifying/uninstalling. How can we fix this? InstallShield had an option to specify a cache directory for the MSI. What is IA's solution?
Matt Houser
Director, Software Development
Pulse Microsystems Ltd.
Compressd Install cannot find MSI when modify/uninstall
Similar problem with MSI File when installing another instan
Hi,
I have got a similar problem when installing another instance of our software compiled with IA 8.01. Here the setup program runs in the error message that it can't find the appropriate setup.msi in a temp folder although this folder and the file both are existing! Installation of each version separetly works fine.
This seems to be a bug in IA 8.01. Is there a solution or workaround for it?
I have got a similar problem when installing another instance of our software compiled with IA 8.01. Here the setup program runs in the error message that it can't find the appropriate setup.msi in a temp folder although this folder and the file both are existing! Installation of each version separetly works fine.
This seems to be a bug in IA 8.01. Is there a solution or workaround for it?
Similar problem with MSI File when installing another instan
Hi,
I have got a similar problem when installing another instance of our software compiled with IA 8.01. Here the setup program runs in the error message that it can't find the appropriate setup.msi in a temp folder although this folder and the file both are existing! Installation of each version separetly works fine.
This seems to be a bug in IA 8.01. Is there a solution or workaround for it?
I have got a similar problem when installing another instance of our software compiled with IA 8.01. Here the setup program runs in the error message that it can't find the appropriate setup.msi in a temp folder although this folder and the file both are existing! Installation of each version separetly works fine.
This seems to be a bug in IA 8.01. Is there a solution or workaround for it?
Hi folks,
the workaround is to use a WEB Deploy build and define an [OFFLINE] Web Media Block on the very top of the MSIcode.
Remove all other Web Media Blocks and you'll habe a stand alone exe or msi (from gpwizard) and the installer data will be cached for uninstallation.
You may also override CACHEOVERRIDE variable in order to put the cache data to $WINDIR$\\Installer instead of APPDATA
Regards,
Kapa
the workaround is to use a WEB Deploy build and define an [OFFLINE] Web Media Block on the very top of the MSIcode.
Remove all other Web Media Blocks and you'll habe a stand alone exe or msi (from gpwizard) and the installer data will be cached for uninstallation.
You may also override CACHEOVERRIDE variable in order to put the cache data to $WINDIR$\\Installer instead of APPDATA
Regards,
Kapa
Regards,
Kapa
Kapa
Hi Kapa,kapa79 wrote:Hi folks,
the workaround is to use a WEB Deploy build and define an [OFFLINE] Web Media Block on the very top of the MSIcode.
Remove all other Web Media Blocks and you'll habe a stand alone exe or msi (from gpwizard) and the installer data will be cached for uninstallation.
You may also override CACHEOVERRIDE variable in order to put the cache data to $WINDIR$\\Installer instead of APPDATA
Regards,
Kapa
thanks for your immediate replay. I made the changes as described in your workaround and it works fine!
Regards,
Ralf
Hi Kapa,kapa79 wrote:Hi Ralf,
you're welcome. It took me 4 hours to figure it out in other topics, how to handle it, but I wouldn't want anybody to get through the same
thanks for your endeavours. It took me much time for the analysing of the problem, fixing and finally testing of the rebuild of the setups, too.
Regards
Ralf