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
- :
- How to debug a Suite Installation (Problem with Windows Feature Activation)
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
‎Oct 10, 2013
08:32 AM
How to debug a Suite Installation (Problem with Windows Feature Activation)
Hi,
I am new to Suite installations....is it possible to debug a Suite Project Installation? In the Release view I cannot pass a log parameter 😉
My Suite installation seems to stop durings Windows Feature Activation.
I have integrated a IS Setup and for this package I have defined one Windows Feature (IIS-WebServerRole).
It doesn't work and I don't know where to start...
I am new to Suite installations....is it possible to debug a Suite Project Installation? In the Release view I cannot pass a log parameter 😉
My Suite installation seems to stop durings Windows Feature Activation.
I have integrated a IS Setup and for this package I have defined one Windows Feature (IIS-WebServerRole).
It doesn't work and I don't know where to start...
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 10, 2013
08:35 AM
Okay the help was my friend:
To create a debug log file, run the Advanced UI or Suite/Advanced UI installation from the command line with /debuglog parameter. To generate a log file named InstallShield.log in the same directory as the Setup.exe file, pass just the command-line parameter. Note that this does not work if the Setup.exe file is in a read-only location. For example:
Setup.exe /debuglog
To create a debug log file, run the Advanced UI or Suite/Advanced UI installation from the command line with /debuglog parameter. To generate a log file named InstallShield.log in the same directory as the Setup.exe file, pass just the command-line parameter. Note that this does not work if the Setup.exe file is in a read-only location. For example:
Setup.exe /debuglog
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 11, 2013
12:09 AM
Please check in the Onlinhelp "Generating Package Log Files While Running an Advanced UI or Suite/Advanced UI Installation" and "Logging an Advanced UI or Suite/Advanced UI Installation to Troubleshoot Issues"
It is possible to set a directory and a file name:
-> Suite.exe /log:"C:\PathToLogFiles" /debuglog"C:\PathToLog\setupexe.log"
"Note that this works if the Setup.exe file is in a read-only Location"
It is possible to set a directory and a file name:
-> Suite.exe /log:"C:\PathToLogFiles" /debuglog"C:\PathToLog\setupexe.log"
"Note that this works if the Setup.exe file is in a read-only Location"
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)