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.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- SETUPEXEDIR now ORIGINALSETUPEXEDIR
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 03, 2017
09:32 AM
IS 2016 SP1 undocumented changes
I have upraded our build machine with IS 2016 SP1 yesterday. And suddenly, our suite installer was not working anymore. After researching the issue, we found out that now, the setup.exe is being copied to a temp dir and renamed to a random name before being executed.
for example, thsi is the beginning of the suite install log:
Engine: we're running from C:\Users\ALA~1\AppData\Local\Temp\{D863CF9B-54E7-4653-BD30-CC4FE1C77D09}\_isA974.exe
And the command-line, later is
Command Line: /log"C:\ProgramData\Installation\Blah_20170302-161534" -IS_temp ORIGINALSETUPEXEDIR="\\da\Daily Builds\build" ORIGINALSETUPEXENAME="SC Setup.exe" /debuglog"C:\ProgramData\Installation\Blah_20170302-161534\SC Installation.log"
These ORIGINALSETUPEXEDIR and ORIGINALSETUPEXENAME properties are not documented, as far as I know.
Just wanted to share this info, in case someone runs into an issue like ours.
for example, thsi is the beginning of the suite install log:
Engine: we're running from C:\Users\ALA~1\AppData\Local\Temp\{D863CF9B-54E7-4653-BD30-CC4FE1C77D09}\_isA974.exe
And the command-line, later is
Command Line: /log"C:\ProgramData\Installation\Blah_20170302-161534" -IS_temp ORIGINALSETUPEXEDIR="\\da\Daily Builds\build" ORIGINALSETUPEXENAME="SC Setup.exe" /debuglog"C:\ProgramData\Installation\Blah_20170302-161534\SC Installation.log"
These ORIGINALSETUPEXEDIR and ORIGINALSETUPEXENAME properties are not documented, as far as I know.
Just wanted to share this info, in case someone runs into an issue like ours.
(3) Replies
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 06, 2017
11:05 AM
Very interesting. Thanks for the heads up.
I also found an issue with suite installs and IS 2016 SP1 - see https://community.flexerasoftware.com/showthread.php?222402-Suite-package-install-detection-condition-failing-with-IS-2016-SP1
Because of this I've had to backout IS2016 SP1 from our build environment and revert to the original release verson of IS2016. I only use Basic MSI setup projects in conjunction with the suite though and so this won't affect everyone.
I also found an issue with suite installs and IS 2016 SP1 - see https://community.flexerasoftware.com/showthread.php?222402-Suite-package-install-detection-condition-failing-with-IS-2016-SP1
Because of this I've had to backout IS2016 SP1 from our build environment and revert to the original release verson of IS2016. I only use Basic MSI setup projects in conjunction with the suite though and so this won't affect everyone.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 24, 2018
01:08 PM
We are trying to move to InstallShield 2018. I noticed this issue and then searched to findout what was posted.
This change has broken a lot of things in our installs.
Thanks for posting it. It confirms what I am seeing.
--Kim
This change has broken a lot of things in our installs.
Thanks for posting it. It confirms what I am seeing.
--Kim
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 24, 2018
01:40 PM
It is documented with the SUITE properties in InstallShield 2018,