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.
don_walker
Level 3
- Revenera Community
- :
- About don_walker
Jul 23, 2015
10:37 AM
Michael, thanks once again for an informative and detailed reply. You've confirmed that I need to upgrade the IS 2014 Suite to IS 2015. As we are still in development this shouldn't be any problem. Our situation is that two of our products will be sharing a configuration editor. Since one product is in beta and the other in development we are just starting to encounter sharing problems. What we want is the following: 1. Only the latest version of the shared package will be installed. If an earlier version is present it will be skipped. 2. When all shared references are removed the package will be uninstalled. To confirm, the package GUID is the same in the IS 2015 and the IS 2014 suite. The IS 2015 suite fails to install when a newer version of the shared package has been installed by the IS 2014 suite. At present we are working around the problem by manually uninstalling the newer version. Let me know if you require any more details.
... View more
Jul 22, 2015
03:06 PM
I have a suite built with IS 2015 that has a shared dependency package. I have another suite built with IS 2014 that has the same dependency package (same Package GUID). According to the help file "If two Advanced UI or Suite/Advanced UI installations share different versions of the same package, the later version of the package is the one that is installed on target systems after both Advanced UI or Suite/Advanced UI installations are run, regardless of which one was run first". In my case, the IS 2014 suite has a newer version of the package and is installed first. The IS 2015 suite then fails to install because it tries to install the shared package and detects that a newer one is already installed. I suspect, and would like to confirm, that I need both suites built with IS 2015 for shared packages to work properly.
... View more
Labels
- Labels:
-
InstallShield 2015
Oct 17, 2014
01:20 PM
I've submitted the formal bug report. it is Case #00485691
... View more
Oct 16, 2014
01:40 PM
Continuing on point 3, anytime the suite setup.exe passes a path from a 32-bit-component to a 64-bit component it should pass the actual path, rather than a path is could be subject to redirection. Stackoverflow has a suggested way to determine the actual path at https://stackoverflow.com/questions/23650436/how-to-get-actual-path-of-redirected-path I plan to file an official support request and will update here when that is done. Thanks again for your responses.
... View more
Oct 15, 2014
10:08 AM
Thanks for your prompt response. Some additional comments and questions follow: 1. Since we've started in the forum I would prefer to continue discussions here. However, I have an active support contract and can log a formal bug report if you want me to. Let me know. 2. I'm not aware of any explicit references to 64-bit paths or packages in the suite. All our own msi files are for 32-bit apps. However, we do include a number of standard Microsoft rediistributables. I've attached a copy of the suite .issuite file. 3. Whatever the technical reasons that you are not applying file system redirection consistently I have to say that I consider this a moderately serious bug because of the impact it has on what I assume is a standard practice with SCCM. I will note that we don't have SCCM installed here and that what I know about SCCM comes from Google searches If there are any SCCM experts reading this I would appreciates comments. .
... View more
Oct 14, 2014
03:31 PM
This problem occurs on Windows 7 64-bit. We have a suite built with IS 2014 that installs properly when run by an admin user. However, we have a customer using SCCM who experiences failures when they push the install with SCCM, which runs the install in system context. I have been able to recreate the problem using System Internals psexec utility to run the suite with the -s parameter. The first package the suite tries to install is an msi package that fails with the following message: MSI (s) (2C:A4) [14:52:36:799]: Note: 1: 2203 2: C:\Windows\system32\config\systemprofile\AppData\Local\Downloaded Installations\{A7C4B3C0-F3A0-426A-A043-E13DBA123E52}\SSCERuntime_x86-ENU.msi 3: -2147287037 which says the msi file isn't there. This is technically correct as file system redirection actually places the file in: "C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Downloaded Installations\{A7C4B3C0-F3A0-426A-A043-E13DBA123E52}\SSCERuntime_x86-ENU.msi" MichaelU addressed a similar problem in his post https://community.flexerasoftware.com/archive/index.php?t-192926.html Michael, could you, or someone else confirm that I have correctly determined the problem. If so, the implication is that any suite created with default settings will fail when run from SCCM or similar services that run the install in system context. I understand that the fix is to set the Cache Path to a directory that will not be redirected. In reviewing the list of properties available at the suite level it appears that either CommonAppDataFolder or CommonDocuments would be safe locations. Comments?
... View more
Labels
- Labels:
-
InstallShield 2014
Apr 09, 2014
01:05 PM
Thanks for considering the possibility of a new feature. While I was researching the subject I found a few hits describing the Windows Installer calls required to do this in an MSI so I'm not the only person to want the functionality. The other subject I found much more frequently in my search was people asking for ways to stop the MsiRMFilesInUse dialog from appearing. Is there a best practice way to stop the ISRMFilesInUse dialog from appearing? I will also ask that you consider a feature to provide a similar functionality at the start of the suite install. I am under the impression that suites are intended to do all their UI up front and then install their packages. Having ISRMFilesInUse dialog's pop up for each MSI package seems at odds with this approach. This is a fairly low-priority suggestion as I realize that it may be necessary to perform package-specific UI (one of my suites does).
... View more
Apr 08, 2014
04:34 PM
Thanks for explaining that ISRMFilesInUse is invoked automatically by the MSI packages. Once I knew that, I tested while leaving some of the install targets running and saw the dialog appear. It appears that this is just a suite-level replacement for the Windows Installer MsiRMFilesInUse Dialog. One of the reasons I was confused was that I was expecting a feature that allowed me to terminate selected processes at the start of the suite install and optionally restart them at the end instead of a feature that applies to each MSI package at the time it is installed. The other problem I have is that I wanted to specify processes that wouldn't normally be detected by Windows Installer. See https://stackoverflow.com/questions/20561990/how-to-solve-the-specified-service-has-been-marked-for-deletion-error for details. I solved this problem by adding a custom kill-process action to one of my MSI packages. It would have nice to have a feature where I could just specify a list of image names and let the suite handle it.
... View more
Apr 04, 2014
04:39 PM
There are two predefined secondary windows for the Suite Wizard pages that appear to be intended to be used for checking files that are in use. They are ISFilesInUse and ISRMFilesInUse. I have not been able to find any documentation about how to use them and their associated properties ISFilesInUseList and ISCloseApplications. While I could get the dialog to display with a Click Show Window action and populate the list there doesn't seem to be any logic hooked up to the dialog. Does anyone have any idea about how these are supposed to be used? Note to the InstallShield docs team - this feature appears to be completely undocumented!
... View more
Labels
- Labels:
-
InstallShield 2013
Jun 07, 2013
11:04 AM
If I've read this Microsoft Support statement ( http://msdn.microsoft.com/en-us/vstudio/ms788708 ) correctly, you are right and the basic VB6 runtime is no longer required. We only go back as far as XP SP3.
... View more
Jun 07, 2013
09:43 AM
We also have customers using Windows XP. It seems like you got a bit carried away with removing stuff. One of the items listed is the "Microsoft Visual Basic Virtual Machine 6.0", which, as far as I know, is the VB6 runtime. I think I would have heard if Microsoft had dropped support for VB6.
... View more
Latest posts by don_walker
Subject | Views | Posted |
---|---|---|
1506 | Jul 23, 2015 10:37 AM | |
2771 | Jul 22, 2015 03:06 PM | |
2930 | Oct 17, 2014 01:20 PM | |
2930 | Oct 16, 2014 01:40 PM | |
2930 | Oct 15, 2014 10:08 AM | |
5003 | Oct 14, 2014 03:31 PM | |
1892 | Apr 09, 2014 01:05 PM | |
1892 | Apr 08, 2014 04:34 PM | |
3035 | Apr 04, 2014 04:39 PM | |
2247 | Jun 07, 2013 11:04 AM |
Activity Feed
- Posted Re: Shared packages require both suites to be IS 2015? on InstallShield Forum. Jul 23, 2015 10:37 AM
- Posted Shared packages require both suites to be IS 2015? on InstallShield Forum. Jul 22, 2015 03:06 PM
- Tagged Shared packages require both suites to be IS 2015? on InstallShield Forum. Jul 22, 2015 03:06 PM
- Tagged Shared packages require both suites to be IS 2015? on InstallShield Forum. Jul 22, 2015 03:06 PM
- Tagged Shared packages require both suites to be IS 2015? on InstallShield Forum. Jul 22, 2015 03:06 PM
- Posted Re: Installing a suite in system context - file system redirection problem? att: MichaelU on InstallShield Forum. Oct 17, 2014 01:20 PM
- Posted Re: Installing a suite in system context - file system redirection problem? att: MichaelU on InstallShield Forum. Oct 16, 2014 01:40 PM
- Posted Re: Installing a suite in system context - file system redirection problem? att: MichaelU on InstallShield Forum. Oct 15, 2014 10:08 AM
- Posted Installing a suite in system context - file system redirection problem? att: MichaelU on InstallShield Forum. Oct 14, 2014 03:31 PM
- Posted Re: Checking for files in use at the Suite level on InstallShield Forum. Apr 09, 2014 01:05 PM
- Posted Re: Checking for files in use at the Suite level on InstallShield Forum. Apr 08, 2014 04:34 PM
- Posted Checking for files in use at the Suite level on InstallShield Forum. Apr 04, 2014 04:39 PM
- Posted Re: Merge Modules on InstallShield Forum. Jun 07, 2013 11:04 AM
- Posted Re: Merge Modules on InstallShield Forum. Jun 07, 2013 09:43 AM
Contact Me
Online Status |
Offline
|
Date Last Visited |
Mar 18, 2019
12:11 PM
|