This website uses cookies. By clicking Accept, 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.
rboutilier
Level 4
- Revenera Community
- :
- About rboutilier
Mar 07, 2014
08:37 AM
I've attached a copy of my project file. Hopefully this will help shed some light on the situation.
... View more
Mar 05, 2014
02:09 PM
I create a separate component for each satellite dll, and control which ones get installed with component conditions. So I'll have something like the following: Component My.Assembly.dll (this is the main assembly and doesn't have a condition) Component My.Assembly_de.resources.dll (this is the German resource assembly, and has a condition of ProductLanguage=1031) Component My.Assembly_fr.resources.dll (this is the French resource assembly, and has a condition of ProductLanguage=1036) I always use ProductLanguage in the conditions so that the assemblies that get installed match the language the installer is running in. This way, you can install in a language different from the system language (i.e. installing the French version on an English OS). Also, it's a good idea to set the "Reevaluate Condition" property of the satellite components to Yes, so that the language can be changed in a maintenance operation. This is the method that I've used with our products, which support 11 languages. Although it results in a lot of components, I've found it to be very reliable. Hope this helps.
... View more
Mar 05, 2014
10:26 AM
This is a project that I created from scratch in InstallShield 2013 SP1 to rule out any possible upgrade issues. I'm actually building the suite project on my build machine, however, which uses the IS 2013 SP1 Standalone Build. I'll try building it in the IDE and will post if I get different results.
... View more
Mar 05, 2014
09:23 AM
I have a suite project organized in the following way: Feature_A Subfeature_AA Package_AA1 (Release flag: CD) Package_AA2 (Release flag: Web) Package_AA3 (32-bit msi, No Release flag) Package_AA4 (64-bit msi, No Release flag) Package_A1 (Release flag: CD) Package_A2 (Release flag: Web) Package_A3 (32-bit msi, No Release flag) Package_A4 (64-bit msi, No Release flag) I have created two releases (CD-ROM and Web) that use the CD and Web release flags, respectively. If I run a full install of the CD-ROM release on a 32-bit system, the following packages are installed: A1,A3. None of the Packages included in Subfeature_AA are installed. Checking the installation log, I find the following entry: Parcel {GUID for Package_AA2} mapped to feature FaroArmUsb was not found There shouldn't be any reference to Package_AA2 at all. It should have been filtered out of the release based upon the release flags. In contrast, Package_A2 is not referenced in the log at all. This error seems to break the action states for all the parcels in the subfeature. All of the final action states of the parcels are set to 5, resulting in none of them being installed. As an experiment, I moved Subfeature_AA left, so that it is a top-level feature. When I do this, everything works as expected. I am left with the conclusion that the build engine does not filter out packages based on release flags when those packages are in subfeatures. Can anyone confirm this? I hope I've explained it adequately. It's not the easiest thing to communicate.
... View more
Labels
- Labels:
-
InstallShield 2013
Nov 01, 2013
09:00 AM
I'm experiencing this as well with InstallShield 2013 SP1. My company is named FARO, so many of our assemblies have the name format Faro.XXXXXX.dll. The build process seems to be mangling the cab file names in the Media table. For instance, the file Faro.DeviceControlPanel.Modules.FaroArmSerial.dll resides in the file Faro.D~1.cab, but the Media table references FAROD~~1.CAB in the Cabinet column. Hopefully Flexera will see this post, because this has to be a bug.
... View more
Aug 20, 2012
11:32 AM
I can confirm that the -y option does not work for a Suite Project. In order to change the version during an automated build, I had to resort to a text replace in the suite project file before launching iscmdbld.
... View more
Apr 24, 2012
10:03 AM
I believe I've found an issue with suite installations and package caching. I have a suite project consisting of one main application and a number of dependencies. Installation works well, but attempting to repair the suite consistently fails. After examining the log file for the repair, I've found the following error to be the culprit: 4-24-2012[08:33:08 AM]: Will launch exe: C:\Users\FAROAD~1\AppData\Local\Temp\{6C09904A-43E4-4A8B-8749-A05C693B5A2D}\{9A2A191D-8FC6-4C3F-AA02-B1D4200E74C8}\dotNetFx40_Full_x86_x64.exe 4-24-2012[08:33:08 AM]: Parcel target exe does not exist 4-24-2012[08:33:08 AM]: Parcel operation return status: 80070002 I have the "Cache Packages Locally" option turned on for the release, but since the dependency was already present when the original suite install took place, it did not get cached. I do have a repair operation defined for the package since I'd like the suite repair to handle the case of a user uninstalling the dependency after the initial suite install. Is there any way to do this? Perhaps a way to force all eligible packages to be cached, even if they are detected?
... View more
Labels
- Labels:
-
InstallShield 2012
Feb 02, 2012
12:31 PM
I have created a suite installer for one of my products and it is working reasonably well. Yesterday I tried creating a web release of the same suite and have run into something I believe is a bug. The suite contains several third-party dependencies and several of my own msi packages. Each of my msi packages is a multi-language release, so each one contains an .msi file, a .cab file, and one .mst file per language. Everything works as it should when each package's location is set to Copy From Source Media. To create a web installer, I set the location of some of the dependencies to Download From The Web, and the rest of the packages to Extract From Setup.exe. When running the web installer, I receive the following error: MD5 check failed for the current file to be staged. The file may be corrupted. File: C:\Users\Roger\AppData\Local\Downloaded Installations\{8947604C-6C77-43C9-BA6A-B026A9A6D330}\1031.mst I looked at this folder and the 1031.mst file is not the correct one for the package. The file is actually the 1031.mst file from one of the other packages in the suite. So it looks like the suite installer engine doesn't work correctly if multiple packages embedded in Setup.exe have identical filenames. At least that's my hypothesis. Can anyone from IS verify this?
... View more
Labels
- Labels:
-
InstallShield 2012
Jan 10, 2012
01:37 PM
Thank you Michael. Your approach did work for me once I played around with it a bit. Since I couldn't add just an .msu file as the only file in a package, I had to add a bogus .exe file, add the adjacent files (the .msu file) and then delete the bogus .exe. I defined the operations as follows: Target: [SystemFolder]wusa.exe EXE Command Line: "[ISPREREQDIR]\Windows6.0-KB958655-v2-x86.msu" /quiet /norestart EXE Silent Command Line: "[ISPREREQDIR]\Windows6.0-KB958655-v2-x86.msu" /quiet /norestart Exit Behavior: Ask whether to continue the setup Reboot Request: Prompt, then exit or reboot the machine Reboot Codes: 3010,8192,1641
... View more
Dec 30, 2011
10:47 AM
I am attempting to convert all the the prerequisites in my current installer into packages in a new suite project. Some of these (namely Windows installer 4.5 for Vista) are actually packaged as .msu files. I don't see any way of including a .msu file as a package file. Is there a way to do this?
... View more
Labels
- Labels:
-
InstallShield 2012
Dec 01, 2011
10:40 AM
That appears to have done the trick. Thank you!
... View more
Dec 01, 2011
09:05 AM
Any word on this? This apparent bug has completely halted my experiments with suite installations. And in reference to a previous query, I do believe this behavior was introduced with SP1.
... View more
Nov 10, 2011
07:41 AM
I've created a suite installation with a single feature containing two packages. Package 1 is the msi installer for the 32-bit version of my application with the following eligibility condition Platform: OSVersion: 5.0-;Architecture: x86 Package 2 is the msi installer for the 64-bit version of my application with the following eligibility condition Platform: OSVersion: 5.0-;Architecture: x64 The suite installation succeeds on a 32-bit OS and correctly installs the 32-bit version of my program. Running the suite installer on a 64-bit OS consistently fails. The last few lines of the debug log are as follows: 11-9-2011[12:26:29 PM]: MSI parcel operation requires elevation 11-9-2011[12:26:29 PM]: Failed to obtain proxy handler for elevated MSI parcel operation 11-9-2011[12:26:29 PM]: MSI parcel launch result: 800700e9 11-9-2011[12:26:29 PM]: Engine: property 'ISInstallStatus' value now 'Package operation complete' 11-9-2011[12:26:29 PM]: UI DLL: Get: Property=ISInstallStatus Value=Package operation complete Return Code=0 11-9-2011[12:26:29 PM]: Engine: property 'ISParcelStatus' value now 'ID_STRING16' 11-9-2011[12:26:29 PM]: UI DLL: Get: Property=ISParcelStatus Value=ID_STRING16 Return Code=0 11-9-2011[12:26:29 PM]: Parcel operation return status: 800700e9 11-9-2011[12:26:29 PM]: MSI parcel detect: product code: '{CB99187B-2F6A-4BA9-9DED-1970B116CC58}', package code: '{BC98C8EF-B9CF-4417-AF94-CD590DE0AC1F}', patch code: '' 11-9-2011[12:26:29 PM]: MSI parcel detect: evaluate status: 0, is installed: false 11-9-2011[12:26:29 PM]: Re-running parcel detection for parcel {59575D73-82DB-4966-8DFD-B2B27D562EF9}, install state: 0 11-9-2011[12:26:29 PM]: Transaction: parcel returned error status 800700e9 11-9-2011[12:26:29 PM]: Transaction: finished running parcels, will roll back transaction 11-9-2011[12:26:29 PM]: End transaction result: 1 11-9-2011[12:26:29 PM]: Engine: error 800700e9 while running parcel operations 11-9-2011[12:26:29 PM]: Engine: parcel operations completed, sending completed event to UI 11-9-2011[12:26:29 PM]: Engine: property 'ISInstallStatus' value now 'IDS_SUITE_INTERRUPTED' 11-9-2011[12:26:29 PM]: UI DLL: Get: Property=ISInstallStatus Value=IDS_SUITE_INTERRUPTED Return Code=0 11-9-2011[12:26:29 PM]: Engine: property 'ISParcelStatus' value now '' 11-9-2011[12:26:29 PM]: UI DLL: Get: Property=ISParcelStatus Value= Return Code=0 11-9-2011[12:26:29 PM]: UI DLL: Get: Property=SETUPSUPPORTDIR Value=C:\Users\FAROAD~1\AppData\Local\Temp\{41957C90-C088-4271-9C1E-C42445DE3F63}\ Return Code=0 11-9-2011[12:26:29 PM]: UI DLL: Get: Property=ISSelectedLanguage Value=1033 Return Code=0 11-9-2011[12:26:29 PM]: UI DLL: Get: Property=SETUPSUPPORTDIR Value=C:\Users\FAROAD~1\AppData\Local\Temp\{41957C90-C088-4271-9C1E-C42445DE3F63}\ Return Code=0 11-9-2011[12:26:29 PM]: UI DLL: Get: Property=ISSelectedLanguage Value=1033 Return Code=0 11-9-2011[12:26:29 PM]: UI DLL: Get: Property=ISInstallStatus Value=IDS_SUITE_INTERRUPTED Return Code=0 11-9-2011[12:26:29 PM]: Engine: property 'ISCurrentPage' value now 'InstallationComplete' 11-9-2011[12:26:29 PM]: UI DLL: Blocking Main Thread 11-9-2011[12:26:55 PM]: UI DLL: Shutting down 11-9-2011[12:26:55 PM]: UI DLL: Releasing Main Thread 11-9-2011[12:26:55 PM]: Engine: all operations completed, final status: 800700e9 11-9-2011[12:26:55 PM]: Final exit status: 800700e9 11-9-2011[12:26:55 PM]: State manager: cleaning up state info Both packages are set to require elevated privileges and the required execution level for the release is Administrator. Earlier in the log file the following appears, which I'm assuming is related: 11-9-2011[12:22:38 PM]: Timed out waiting for proxy to respond Does anyone know what might be causing this?
... View more
Labels
- Labels:
-
InstallShield 2012
Oct 24, 2011
08:35 AM
I have found that uninstalling my suite consistently fails if I do not choose to 'Cache Packages Locally' for my release. Looking at the debug log, I see the following: 10-21-2011[01:33:15 PM]: Will launch exe: C:\Users\FAROAD~1\AppData\Local\Temp\{06A2AB7C-FC01-4ABC-87B7-D1198C3ECDA7}\{925759E8-0010-40E3-9F7C-0E474D141698}\setup.exe 10-21-2011[01:33:15 PM]: Parcel target exe does not exist 10-21-2011[01:33:15 PM]: Parcel operation return status: 80070002 And in fact this path does not exist during the uninstall operation since I am not caching the packages. I would think that if the packages aren't cached, that they would be run from the source location. This is easily remedied by caching the packages, but then why have the option?
... View more
Labels
- Labels:
-
InstallShield 2012
Latest posts by rboutilier
Subject | Views | Posted |
---|---|---|
1974 | Mar 07, 2014 08:37 AM | |
834 | Mar 05, 2014 02:09 PM | |
1974 | Mar 05, 2014 10:26 AM | |
4336 | Mar 05, 2014 09:23 AM | |
1239 | Nov 01, 2013 09:00 AM | |
1772 | Aug 20, 2012 11:32 AM | |
2354 | Apr 24, 2012 10:03 AM | |
910 | Feb 07, 2012 01:40 PM | |
1814 | Feb 02, 2012 12:31 PM | |
1046 | Jan 10, 2012 01:37 PM |
Activity Feed
- Posted Re: Suite project: Packages in subfeatures are not filtered based on release flags on InstallShield Forum. Mar 07, 2014 08:37 AM
- Posted Re: .NET assembly satellite dlls, how to package ? on InstallShield Forum. Mar 05, 2014 02:09 PM
- Posted Re: Suite project: Packages in subfeatures are not filtered based on release flags on InstallShield Forum. Mar 05, 2014 10:26 AM
- Posted Suite project: Packages in subfeatures are not filtered based on release flags on InstallShield Forum. Mar 05, 2014 09:23 AM
- Tagged Suite project: Packages in subfeatures are not filtered based on release flags on InstallShield Forum. Mar 05, 2014 09:23 AM
- Tagged Suite project: Packages in subfeatures are not filtered based on release flags on InstallShield Forum. Mar 05, 2014 09:23 AM
- Tagged Suite project: Packages in subfeatures are not filtered based on release flags on InstallShield Forum. Mar 05, 2014 09:23 AM
- Posted Re: Problem with web installer after InstallShield upgrade on InstallShield Forum. Nov 01, 2013 09:00 AM
- Posted Re: Set product version for Advanced UI Project via command line on InstallShield Forum. Aug 20, 2012 11:32 AM
- Posted Suite installations and package caching on InstallShield Forum. Apr 24, 2012 10:03 AM
- Posted Re: Apparent bug in suite installer on InstallShield Forum. Feb 07, 2012 01:40 PM
- Posted Apparent bug in suite installer on InstallShield Forum. Feb 02, 2012 12:31 PM
- Posted Re: .msu files as suite packages? on InstallShield Forum. Jan 10, 2012 01:37 PM
- Posted .msu files as suite packages? on InstallShield Forum. Dec 30, 2011 10:47 AM
- Posted Re: Suite installation failing on 64-bit OS on InstallShield Forum. Dec 01, 2011 10:40 AM
- Posted Re: Suite installation failing on 64-bit OS on InstallShield Forum. Dec 01, 2011 09:05 AM
- Posted Suite installation failing on 64-bit OS on InstallShield Forum. Nov 10, 2011 07:41 AM
- Posted Suite package uninstallation fails if not cached locally on InstallShield Forum. Oct 24, 2011 08:35 AM
- Posted Suite installation suggestion on InstallShield Forum. Aug 30, 2011 10:50 AM
- Posted Re: Basic MSI: Major Upgrade problem with file versioning rules of Windows Installer. on InstallShield Forum. Apr 27, 2010 08:57 AM
Contact Me
Online Status |
Offline
|
Date Last Visited |
Mar 18, 2019
12:10 PM
|