This website uses cookies. By clicking OK, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Nick_Umanski
Active participant
Nov 06, 2019
10:16 AM
Ah, that sounds like you have an explorer window open in the release folder where the intermediate files are built.
... View more
Nov 06, 2019
09:26 AM
1. Spin the Product and Package GUIDs, make sure the Upgrade GUID is identical 2. Change the ProductVersion 3. Create a Major Upgrade Item Upgrades->Upgrade Windows Installer Setup->Add Major Upgrade Item Name it "UpgradeOlderVersion" or something appropriate, set the options to: . Products sharing my Upgrade Code . Any earlier version 4. Make sure the "Completely uninstall old setup before installing new setup" is in play on the "Upgrade Windows Installer Setup" tab, the other option is unreliable if you don't know what you are doing.
... View more
Nov 06, 2019
09:16 AM
You need to speak to Flexera tech support and ask them to de-register the old version. It is a pain, I've had this happen a couple of times over the years, but they are usually very quick at responding to this and I don't think this requires a maintenance agreement with them.
... View more
Nov 06, 2019
09:10 AM
The warning dialog box should be generated with a "SpawnDialog" event (as opposed to a "NewDialog"). That will leave the originating dialog in play. Then when you click the OK button it's behaviour event needs to be set to EndDialog|Return
... View more
Nov 06, 2019
08:56 AM
You haven't provided anywhere near enough information to answer this question properly, but it has to be one or more issues with either the version numbers of the files or the upgrade settings you are running. I'm not sure why the IDE mode works, but it is a red herring, the only thing that matters is whether your release builds work. I suspect the IDE runs in Major Upgrade mode, but you've got your release builds set to Minor or something else. Questions: . Are you running a major or minor upgrade? . Have you spun the Package and Product GUIDs? . Is the Upgrade GUID identical between the two releases . What are the relevant versions of the files being installed, compared to the existing files. . Does an upgrade actually run when you run the release or does it look like a fresh install? . Are you using the upgrade setting: "Completely uninstall old setup before installing new setup" . Are you running in UI mode or silent mode? . Have you logged the install?
... View more
Sep 12, 2019
04:30 AM
Thanks for the response Jenifer. I am familiar with what should happen and I did compare the logs of a working machine versus non working one (although it stated it had completed successfully), which is how I determined that the non working one didn't think any of the features were installed. What I needed was the nut and bolts of how the MSI engine determined which features were installed and after further investigation I found that it was a set of registry settings namely. [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Features\<MangledProductGUID>] "<TopLevelFeature>"="" "<SubFeature>"="<TopLevelFeature>" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\<MangledProductGUID>\Features] "<TopLevelFeature>"="<HugeRandomStringOfCharacters>" "<SubFeature>"="<HugeButDifferentRandomStringOfCharacters> <TopLevelFeature>" Where <MangledProductGUID> = 42E15F854475F1D41AD1B0543CC43EFA instead of {58F51E24-5744-4D1F-A11D-0B45C34CE3AF} On a bad machine I found the second set of entries missing, while the first set of entries appeared corrupted as follows: [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Features\<MangledProductGUID>] "<TopLevelFeature>"="[ACK]" "<SubFeature>"="[ACK] <TopLevelFeature>" Further investigation found that the apparant corruption was the unicode character ACK, which is actually a valid entries used by the MSI engine to indicate that a feature in not installed. It appears that the entries for all features are added to the registry with the ACK character flagging which ones aren't installed. However, it doesn't seem possible or shouldn't be possible to have the MSI engine flag the <TopLevelFeature> as not installed. Attempting to install the product on a fresh machine and choosing no features on the CustomSetup dialog results in no install of the product, rather than a featureless install, even though the install runs to completion. At this point I don't think the problem is in the installer but an environmental issue. The problem has happened on about 100 out of 800 machines on a single customer with the last upgrade sent out. This customer installs the product via a GPO process. Other customers have no problem and some of them also use a GPO process. Although a second customer did initially report issues this turned out to be on a single machine with an unrelated problem. However, my Support department are coming to me for answers. But although I can now manually replicate the problem, I can't explain how the customer machines got into that state in the first place and the customer is adamant that there is nothing wrong with their environment.
... View more
Sep 09, 2019
05:20 AM
How does a basic MSI package determine what features were installed previously when performing a major upgrade? I have a problem which only affects a small number of machines in that when attempting to upgrade our product, the upgrade appears to complete successfully, but no files are actually upgraded. Further investigating found that when running the Setup, the package determined that no features had been installed (even though they had and the files from those features are present on the machine). Thus when running silently, the product 'successfully' upgraded nothing and when running in UI mode, the CustomSetup dialog was displayed with no features pre-selected (not even the default ones). Note, this only affects a small number of customer machines, most upgrade successfully and we cannot recreate the problem in our test environment. Thanks in advance.
... View more
Labels
Dec 21, 2018
09:53 AM
For point 2, the error is in the String table, not the directory table. Now all strings IDs that begin ID_STRING... have been created by your actions, although you might not be aware of them at the time. When you create a variety of elements (some of which may be entries in the Directory table), InstallShield automatically adds an entry into the String table with this default ID which you can and should change to something more meaningful. Obviously you have only added this particular string in this one project, hence why other projects don't encounter the error. Just go to the string table track it down and it should be fairly obvious what is wrong. Typically you have got an excess opening or closing bracket without the corresponding opposite bracket.
... View more
Dec 21, 2018
05:49 AM
The only thing I can think of that might be causing the difference in behaviour between the two installers could be the setting for "Required Execution Level" Releases View -> Setup.exe tab -> Required Execution Level
... View more
Dec 21, 2018
05:41 AM
Continue to do what? If your package is a downgrade, do you want to disable downgrade prevention? If so remove the upgrade item called "PreventDowngrade" \ "ISPreventDowngrade" or the associated Error CustomAction of the same name. If you just want the installer to run to completion without showing an error message, but actually do nothing. Well that is really quite a complicated set of changes that is required and quite ridiculous too. I would never recommend attempting this.
... View more
Dec 21, 2018
04:53 AM
This is a very poorly worded description, please elaborate, are you trying to upgrade or not. Have you Spun the correct GUIDs and Version number fields, did you create an Upgrade item. Do the individual files have version numbers and if so have they changed between each installation. If this is a Major Upgrade what "Major Upgrade Settings" policy have you set?
... View more
Dec 20, 2018
09:18 AM
Basic MSI Installer. My installer need to be able to run on both 32 and 64 bit machines, thus the Template Summary has to be set to "Intel". I have two versions of a particular DLL that needs to be installed, one is 64 bit and one is 32 bit. They both have the same name. I condition the installation of the component containing the 64 bit dll to VersionNT64 and the 32 bit one to "Not VersionNT64". These DLLs need to be installed into the System32 folder. On a 32 bit machine this works fine. But on a 64 bit machine the 64 bit DLL gets installed into the SysWOW64 folder, which is of course the folder for 32 bit components. To make matters worse it is a COM object and needs to be registered. How can I ensure the 64 bit DLL is installed into the System32 folder on a 64 bit machine? I cannot flag the component as "64 bit component" because the installer won't build, complaining that I have to target a x64 or Intel64 platform. But if I do that the installer won't run on a 32 bit platform (I presume) and needs to.
... View more
Labels
Sep 27, 2018
09:36 AM
I was required to give all users (Everyone) full access permissions to the INSTALLDIR for our product. This I did and the product was released. There was then a change of mind and for the next version of the product I was asked to remove those permissions, which again I did. Works as intended for a fresh install. Problem is if the customer installs the old version and then upgrades, the permissions set by the old version remain in play. How can I remove the permissions already in existence on a folder? Thanks in advance.
... View more
Labels
Nov 16, 2017
04:40 AM
In the last week, whenever I fire up IS2014, I get a pop up box stating: Available Software Update for InstallShield 2014 The following update is available on the Internet Upgrade to InstallShield 2016 at 30% off !! .. To download and install this update, click Next. I presume that if I did click Next I would end up with my paid version IS2014 removed and replaced with a 30 day trial version of IS2016 which would require a payment of £2589.30 to activate. At the very least I'd get a side by side install on my companies production machine with all my file associations for .msi, .ism etc pointing at the 2016 app. I don't know if there are any further warnings as I daren't click 'Next' and risk trashing my version of IS 2014, but I find this completely unacceptable and what is more irritating is that I've been investigation the option to get an upgrade price for IS2016, but Flexera won't allow IS2014 to be so upgraded. It is EOL they say and I have to buy a full paid version minus their current 30% off promotion if I already own a version of IS. Is there anyway of switching off this popup, the opening line can so easily be misread to think it is a free standard update and action it without thinking any further.
... View more
Labels
Latest posts by Nick_Umanski
Subject | Views | Posted |
---|---|---|
808 | Nov 06, 2019 10:16 AM | |
424 | Nov 06, 2019 09:26 AM | |
759 | Nov 06, 2019 09:16 AM | |
938 | Nov 06, 2019 09:10 AM | |
814 | Nov 06, 2019 08:59 AM | |
428 | Nov 06, 2019 08:56 AM | |
523 | Sep 12, 2019 04:30 AM | |
551 | Sep 09, 2019 05:20 AM | |
763 | Dec 21, 2018 09:53 AM | |
1846 | Dec 21, 2018 05:49 AM |
Activity Feed
- Posted Re: Install shield read only mode on InstallShield Forum. Nov 06, 2019 10:16 AM
- Posted Re: upgrade using advanced suite on InstallShield Forum. Nov 06, 2019 09:26 AM
- Posted Re: Reinstall Installshield on InstallShield Forum. Nov 06, 2019 09:16 AM
- Posted Re: Staying with current Dialog box when Next button clicked for some condition on InstallShield Forum. Nov 06, 2019 09:10 AM
- Posted Re: Install shield read only mode on InstallShield Forum. Nov 06, 2019 08:59 AM
- Posted Re: Install shield not over writting the files on destination PC on InstallShield Forum. Nov 06, 2019 08:56 AM
- Posted Re: Feature Selection on Upgrade on InstallShield Forum. Sep 12, 2019 04:30 AM
- Posted Feature Selection on Upgrade on InstallShield Forum. Sep 09, 2019 05:20 AM
- Posted Re: Error building on InstallShield Forum. Dec 21, 2018 09:53 AM
- Posted Re: Running setup.exe as non admin doesn't throw ant error on InstallShield Forum. Dec 21, 2018 05:49 AM
- Posted Re: Skip installing a package if there is already a newer version of it on InstallShield Forum. Dec 21, 2018 05:41 AM
- Posted Re: Some files not installed sometimes on InstallShield Forum. Dec 21, 2018 04:53 AM
- Posted Installing files to System32 on 64 bit machine. on InstallShield Forum. Dec 20, 2018 09:18 AM
- Posted Removing existing permissions on a folder on InstallShield Forum. Sep 27, 2018 09:36 AM
- Posted How to suppress offer to upgrade to IS2016 on InstallShield Forum. Nov 16, 2017 04:40 AM
- Posted InstallShield 2017 or next version? on InstallShield Forum. Oct 26, 2017 04:11 AM
- Posted "Completely uninstall old setup before installing new setup", incorrect behaviour on InstallShield Forum. Mar 08, 2016 08:51 AM
- Posted Re: Codesigning using SHA-2, SHA256 on InstallShield Forum. Jan 14, 2016 11:25 AM
- Posted Re: Codesigning using SHA-2, SHA256 on InstallShield Forum. Jan 14, 2016 09:27 AM
- Posted Re: Codesigning using SHA-2, SHA256 on InstallShield Forum. Jan 14, 2016 08:17 AM
Contact Me
Online Status |
Offline
|
Date Last Visited |
Jul 17, 2020
10:27 AM
|