About twunky

twunky · ‎Apr 21, 2021

I had these problems today: I wanted to share my fixes since it was difficult to find the answer and support was not helpful (didn't respond back). Problem: The product license has been corrupted. You must repair the license before you can continue. Click yes to repair now. After I click Yes, I get this message: “Installshield Activation Wizard has stopped working” Solution: SOLUTION • Un-install, reinstall Installshield 2018 (might not be needed. Try deleting the MVSN_* files first before uninstalling - next step) • Navigate to %ProgramData%\Flexnet (might be %ProgramData%\Flexera in other versions) • Show all hidden files and Delete all files starting with MVSN_* • Open InstallShield 2018 and it should now work Cause: The cause of this appeared when IT changed out MAC Address on a build machine with a Perpetual Install (IDE/Development). Other Solutions: Let IT/DevOps know that build machines with Node-Locking Installshield licenses need to have a static MAC Address. The license is tied to the HostId (MAC Address). This is an issue we ran across with a SAB (Stand alone build) install also. Since you can only return a license once a year, a static MAC Address makes sense. SAB Change MAC Issue: PROBLEM The product license has expired or has not yet been initialized. SOLUTION The HostID (MAC Address) has most likely changed on that machine. Check the Flexera Licensing site and the MAC Address on that machine. IT can either change the MAC Address back, or your have to return that license and issue a new one for that address/machine.

twunky · ‎Jun 18, 2019

The main installer is calling a subinstall, and that contains the 4.8 pre-req. I looked at the log files and it just shows the subinstall taking a long time to complete: Clean Install: Action 17:26:52: SetupCompleteSuccess. Dialog created MSI (c) (04:B8) [17:26:57:369]: PROPERTY CHANGE: Adding LAUNCHPROGRAM property. Its value is '1'. MSI (c) (04:B8) [17:26:59:119]: PROPERTY CHANGE: Adding ISSHOWMSILOG property. Its value is '1'. MSI (c) (04:B8) [17:27:22:743]: Doing action: LaunchWorkStation Action 17:27:22: LaunchWorkStation. Action start 17:27:22: LaunchWorkStation. Action ended 17:42:03: LaunchWorkStation. Return value 1. MSI (c) (04:B8) [17:42:03:195]: Doing action: ShowMsiLog Action 17:42:03: ShowMsiLog. Action start 17:42:03: ShowMsiLog. Updated Installer: MSI (c) (84:0C) [16:41:53:725]: PROPERTY CHANGE: Adding LAUNCHPROGRAM property. Its value is '1'. MSI (c) (84:0C) [16:41:56:135]: PROPERTY CHANGE: Adding ISSHOWMSILOG property. Its value is '1'. MSI (c) (84:0C) [16:41:58:260]: Doing action: LaunchWorkStation Action 16:41:58: LaunchWorkStation. Action start 16:41:58: LaunchWorkStation. MSI (c) (84:0C) [16:56:10:950]: Doing action: ShowMsiLog Action 16:56:10: ShowMsiLog. Action start 16:56:10: ShowMsiLog. I'll see what I can do to get a log of the subinstaller

twunky · ‎Jun 18, 2019

Hello, I'm trying to solve an issue we are noticing with InstallShield installing 4.8 framework. When we do a clean/fresh install of our product, the pre-req (.net 4.8) installs in about 5 mins (as expected). But when we do an upgrade of our product and a previous version of our product is on the machine, the .net 4.8 framework takes about 15 mins to install. It then usually causes a reboot (we don't want that also). I'm running some tests now to see if 4.7.2 has the same issues. If not we'll be rolling back to 4.7.2 Any thoughts on what's going on, or even how to debug this issue?

Online Status	Offline
Date Last Visited	‎Sep 21, 2021 06:27 PM

Installshield Activation Wizard has stopped working

Re: .NET 4.8 Offline installation takes 15 mins

.NET 4.8 Offline installation takes 15 mins

Installshield Activation Wizard has stopped working

Re: .NET 4.8 Offline installation takes 15 mins

.NET 4.8 Offline installation takes 15 mins