About Mescalero

Mescalero · ‎Jun 03, 2010

Hello, Is there a way to delete the cached MSI file during an initial (clean) install? Bear with me here: I know that I can configure the installation not to cache the msi on the local machine, but I see that deleting the cached file after the first-time install doesn't cause problems for initiating maintenance mode; the msi still gets cached when setup.exe is called, allowing it to execute. (I am using Installscript MSI.) What I've tried is to use an Installscript CA to delete the application's sub-folder under [LocalAppDataFolder]Downloaded Installations, to no avail. I am placing the CA in the Installation Execute sequence after InstallFinalize. The reason I want to do this is that some end users have complained about the disk space these use. So is it possible to do this during a first-time install? Perhaps more importantly, is it wise to do it? I would very much appreciate any advice...

Mescalero · ‎May 05, 2010

Thanks, Hidenori, that is quite helpful. I wish there was an easier way to differentiate/isolate the instance data, as I may allow the user up to 10 or so instances of this application. But so long as there is indeed a way... 😉 Thanks again.

Mescalero · ‎May 05, 2010

Hello, I do indeed have components that are not being removed. The files within are, but since this is a multi-instance install, that would seem to explain why the first Remove is unsuccessful in deleting reg and SCM entries. If the Component Codes are the same between the two instances, would that explain this behavior? And if so, how does one change those GUIDs between instances? Also, the [InstanceId] property is not being resolved in the path of the components, although it is for the registry and SCM entries. (So the path on the target machine literally becomes \Program Files\ \[InstanceId].) Not sure if that plays a role in the components being set to "Action: File Absent" during the first uninstall. I must either not understand some fundamental Windows Installer concept that drives the multi-instance functionality, or it's hopelessly unwieldy.

Mescalero · ‎Apr 22, 2010

Sorry guys, for the late response. (So much for the thread alerts!) The files themselves (and parent components) are being removed, except for those that I wish to remain on the machine (e.g., configuration file for the service). Interestingly, it isn't the base instance whose service is removed, but whichever instance I remove LAST. So, for instance, with three instances, the first two removes do not uninstall the respective service instance, but the final remove does, in whatever order I decide to remove them. Hope that makes sense. What might I look for in the verbose log? It looks rather normal...

Mescalero · ‎Apr 09, 2010

Hi, Check out the Direct Editor, the table ISString. I think the string IDS_IsInitDlg_PreparingWizard is what you are looking for.

Mescalero · ‎Apr 09, 2010

Hi Rich, This isn't automatic, but it is easy to configure. In your IDE, go to Releases > Product Configuration > Release, and select the setup.exe tab. In the "MSI Command Line Arguments" field, you could enter something like "/l*v %WINDIR%\Installation.log". This particular command creates a verbose log of the install, and there are of course many other logging options (and destinations for the log file) which may better suit your setup. Hope this helps.

Mescalero · ‎Apr 05, 2010

Hello, I've seen the subject raised here, but haven't been able to track down a solution: in a multiple instance install, the services install successfully in the Services Control Module, but upon Remove, only the base instance is unregistered from SCM. This is an IS 2010 Basic MSI project, and I'm curious whether this is a known issue (i.e., bug). Thanks to anyone out there who has knowledge of this and is willing to share it. 😄

Mescalero · ‎Mar 26, 2010

I'm encountering the same problem...

Mescalero · ‎Mar 23, 2010

Great, directly editing the tables did the trick. Josh, many thanks for your help.

Mescalero · ‎Mar 23, 2010

Josh, On the first issue, I'm confused: the name field that you refer to, it is the name one gives the service under Component > Advanced Settings > Services > Service Name? I can't enter spaces or the brackets for a property name in that case... Thanks for your explanation on the second point.

Mescalero · ‎Mar 22, 2010

Incidentally, for any others that run into this, the problem was that the websites' file components had their destination set to [INSTALLDIR]. Once I changed this to [INSTALLDIR]\ , the websites are now deleted on uninstall.

Mescalero · ‎Mar 22, 2010

Hi Josh, I found my problem. Thanks for pointing me in the right direction!

Mescalero · ‎Mar 19, 2010

Hello All, I have a couple of problems when using the multi-instance functionality with a Basic MSI installation: 1) to differentiate the service display names for my multi-instance app in Services, I'm using " [InstanceId]" in the Display Name field for defining the service. The first time, this works fine, as the InstanceId property populates the name: " 0". However, when I install a second instance, " 1" overwrites the first instance name. 2) The [InstanceId] property apparently does not get resolved in time to display in the status boxes, Add/Remove programs, etc. (One sees the actual property [InstanceId] appended to the Product Name.) Is there a way to resolve this property earlier in the installation? I should mention that I'm using the [InstanceId] property because the number of instances installed to a machine is indeterminate--defining a set number of instances in the Multiple Instances view isn't an option. I could get round 2) by defining some number of instances that no user is likely to install. Surely there's a way to resolve the first problem? Thanks to anyone who has dealt with this or knows of a fix.

Mescalero · ‎Mar 19, 2010

Hi Aaron, I think that option 2 is the way to go: detect whether the user is installing on 32 or 64 bit, and link that result to a component/feature that is installed accordingly. (Set the appropriate feature to "TRUE", the other to "FALSE".) Sounds good in theory, anyway. 😄

Mescalero · ‎Mar 18, 2010

Attached. Thanks, Josh.

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:11 PM

Deleting the cached MSI file during first-time install

Re: multi-instance services not removed

Re: multi-instance services not removed

Re: multi-instance services not removed

Re: "Preparing For Installing..." strings

Re: Installation Log

multi-instance services not removed

Re: Multiple instance & .NET installer deinstallation problem

Re: Problems with Multi-instance functionality

Re: Problems with Multi-instance functionality

Re: Error uninstalling IIS web site with dynamic port

Re: Error uninstalling IIS web site with dynamic port

Problems with Multi-instance functionality

Re: 32 and 64bit web apps

Re: Error uninstalling IIS web site with dynamic port

Re: Separating .msi file from setup.exe in setup package.

Re: Separating .msi file from setup.exe in setup package.

Re: updating an "intermediate" version of a file during a patch

Re: How to Force ..\Program Files\.. Folder from 32 bit installer

Re: How to Force ..\Program Files\.. Folder from 32 bit installer

Re: updating an "intermediate" version of a file during a patch

updating an "intermediate" version of a file during a patch

Re: InstallShield 2012 wishlist

Re: Custom action running in uninstall but shoudl not

Re: Chained MSI, Temp location and MSP Patch