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
- :
- Windows get reboot when compiling my .ism file using IS 2013 SAB SP1
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
Jan 06, 2017
01:33 AM
Windows get reboot when compiling my .ism file using IS 2013 SAB SP1
Hi there,
I have Windows 10 x64 bit machine, and I have installed InstallShield 2013 Standalone Build Service Pack 1 in it.
I am compiling my project (.ism file ) in this machine , So at some point while the build is running PC get rebooted , and it does not shows any error message in installshield log file. In system's Event log it shows an error that "the computer has rebooted from bugcheck "
I have Windows 10 x64 bit machine, and I have installed InstallShield 2013 Standalone Build Service Pack 1 in it.
I am compiling my project (.ism file ) in this machine , So at some point while the build is running PC get rebooted , and it does not shows any error message in installshield log file. In system's Event log it shows an error that "the computer has rebooted from bugcheck "
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 06, 2017
10:02 AM
Do you have a support contract with Flexera Software such that you can get in touch with them? Some questions that they will likely ask, judging from some things I've reported that were similar in nature.
1. Do this happen with any ISM or just one particular ISM file?
2. Can you reproduce on another system using the same ISM file? With another OS?
3. Can you reproduce if you convert the project up to 2016 and install the 2016 SAB and try to compile it on that version?
I can sort of see some of their reasoning when they ask these types of questions.
Typically, even if they can reproduce it on the same older version, if they find your ISM works fine in 2016, or whatever the latest version is, then they will want that to be the solution because they don't have the bandwidth to fix each issue with each version on each OS.
I would recommend contacting Flexera directly on this one.
Chad
1. Do this happen with any ISM or just one particular ISM file?
2. Can you reproduce on another system using the same ISM file? With another OS?
3. Can you reproduce if you convert the project up to 2016 and install the 2016 SAB and try to compile it on that version?
I can sort of see some of their reasoning when they ask these types of questions.
Typically, even if they can reproduce it on the same older version, if they find your ISM works fine in 2016, or whatever the latest version is, then they will want that to be the solution because they don't have the bandwidth to fix each issue with each version on each OS.
I would recommend contacting Flexera directly on this one.
Chad