About Mescalero

Mescalero · ‎May 09, 2011

I have a 64-bit installation (specified as x64 in the template summary) where INSTALLDIR is defined as [ProgramFiles64Folder] . I have a dialog screen where the user can modify INSTALLDIR. If they opt to install to \Program Files (x86)\... on a x64 machine, the installation works fine, but the files fail to uninstall during a Remove. Within the verbose log file of the Remove, I see numerous instances of "Disallowing uninstallation of component: {...} since another client exists". None of the components is marked as Shared. This is a 64-bit application, so setting aside for the moment the wisdom of the user even wanting to install under Program Files (x86), why might these files fail to uninstall? Thanks kindly for any info.

Mescalero · ‎Apr 27, 2011

This looks like only occurring on my test machine. No idea why, but it otherwise works, so I can overlook this outlier. 😉

Mescalero · ‎Apr 26, 2011

I have a Basic MSI project that supports multi-instance. I am creating start > programs menu shortcuts for an application file with each installed instance. This file (.exe) has an icon. For the first installed instance, the icon displays. For subsequent instances, the default Windows icon displays. Is this expected behavior? Any insight would be appreciated.

Mescalero · ‎Apr 19, 2011

Thank you for the links. I found that being unable to include the back-slash character after the property name in the Component destination field wasn't a problem: I was able to add the trailing character in the "Set Directory" CAs, and the directory structure on the target machine is now correct.

Mescalero · ‎Apr 12, 2011

Hi, I have a web-based application that needs to be multi-instance. To that end, I am using the [InstanceId] property in the application path. The problem begins in that I cannot correctly define the path for a component, as in this example: [INSTALLDIR]Application\[InstanceId]\ . The IDE forces it to [INSTALLDIR]Application\[InstanceId] (notice the missing "\"), and the application path is thus incorrect when the instance is installed. (I use a custom action to resolve [InstanceId] in the directory name during the install sequence.) If I force the "\" into the path in the Directory table (via Direct Editor), then this error occurs during the project build: "ISDEV : fatal error -6015: Error generating short file name for file...\LOCALS~1\Temp\1\DIR16.tmp\[InstanceId]\...". Is there a way round this, or do I need to find a different naming convention for the instances? Why is this so needlessly difficult to setup? :confused:

Mescalero · ‎Mar 29, 2011

Hi Josh, Thanks. I did an arbitrary property set for ARPSIZE after CostFinalize, and it is not reflected in ARP, as you suggested might occur. (This is an IS MSI project.) For a Basic MSI project (used for the multi-instance capability), the size is accurate. Why the difference in behaviour, and is this something users of Installscript MSI setups just have to grin and bear?

Mescalero · ‎Mar 25, 2011

Any thoughts on how to deal with this ARP size discrepancy?

Mescalero · ‎Mar 22, 2011

Hi All, I have an IS MSI project, and I am trying to get round the problem whereby the app size in ARP is incorrect. I think I've hit upon a way to do it, and it's to call the following bit of Installscript as a custom action: [PHP]szKey = "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{ProductCode}"; RegDBGetKeyValueEx(szKey, "EstimatedSize", nDataType, svValue, nvSize); MsiSetProperty(ISMSI_HANDLE, "ARPSIZE", svValue);[/PHP] But where in the Installer sequence must I call this CA in order for the registry key to have already been created, but before the ARPSIZE value is written to ARP? Or is there an easier way to do this?

Mescalero · ‎Jan 27, 2011

For anyone who encounters this, the problem in my case was consecutive semi-colons (i.e., ";;") in the SecureCustomProperties MSI property; removing one resolved the issue.

Mescalero · ‎Dec 14, 2010

I delete the cached msi file during the uninstall. I had users complain about the "junk" the installations were leaving behind. It does seem these should be deleted during a remove. On the setup.exe tab, I specify the cache location as [LocalAppDataFolder]Downloaded Installations\ to keep things a bit more tidy, and it allows for a consistent search string in the installscript should the app's GUID change.

Mescalero · ‎Dec 14, 2010

Thanks very much for that suggestion! I had [$Documentation} in the Add/Remove programs section of the IDE. Alas, the error still occurs after correcting it to [$Documentation] . Thanks again for the link.

Mescalero · ‎Dec 07, 2010

Thanks for that response. However, I added quotes, even removed the darn command, and still the feature transfer error occurs. I've attached the log file in case anyone would be so kind as to have a look. I'm not expert at interpreting the verbose logs, but this one is telling me nothing... :confused:

Mescalero · ‎Dec 03, 2010

Hello, I have an Installscript MSI project which has been working fine. Today, it errors just before the feature transfer begins with "Error: -1639 Invalid command line argument. Consult the Windows Installer SDK for detailed command line help". I have no idea what I've done that's caused this; the only argument I am passing to the msi file is verbose logging. The log gets created, and it's not clear to me what to look for within. I haven't found any instances of this on the forum that apply to my situation (so far as I can tell). Can anyone suggest something to check, perhaps something in the log file? I have for the moment hit a wall. Thanks very much.

Mescalero · ‎Nov 05, 2010

The problem was that I had left the subject to the default value in the merge module project. I didn't recognise it, as it was called “Blank Merge Module Project Template” in the Redistributables view. A descriptive subject field resolved it. Knew it had to be something simple. :rolleyes:

Mescalero · ‎Nov 04, 2010

Hi Kike, Thanks for your response. Yes, in addition to the automatic copying that takes place when the msm project is built, I've tried manually copying it to the Merge Module directory, to no avail; the other installation projects cannot "see" it in the Redistributables section.

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

files installed under Program Files (x86) are not uninstalled during Remove

Re: Start > Programs menu shortcut icon not displaying for multi-instance

Start > Programs menu shortcut icon not displaying for multi-instance

Re: Problems resolving a property in a path

Problems resolving a property in a path

Re: setting the app size in Add/Remove Programs

Re: setting the app size in Add/Remove Programs

setting the app size in Add/Remove Programs

Re: Error: -1639 Invalid command line argument

Re: How to cache the .msi for maintenance

Re: Error: -1639 Invalid command line argument

Re: Error: -1639 Invalid command line argument

Error: -1639 Invalid command line argument

Re: .msm file doesn't appear in Redistributables list

Re: .msm file doesn't appear in Redistributables list

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