1Jan

Installshield Not Launching Version

1 Jan 2000admin

Using MSI Launch Conditions to Prevent Installation on Unsupported. Format of the LaunchCondition table in the InstallShield Direct Editor. Not VersionNT64, ProductName will only work on 32-bit versions of Windows. Is there any setting in InstallShield which enables Setup.exe to read write in Setup.iss file. I am running following command from command prompt Setup.exe -r and getting Setup.iss file at C: Windows with following contentInstallShield Silent Version=v7.00 File=Response File File Transfer OverwrittenReadOnly=NoToAll.

  • we are connecting to license server for licensing..For other machines in our team, the commandline version is working but not in my machine.
    • just your machine?? Is DNS resolving the server name OK
      • yes.all other shares are working.
      • its not about shares. if installshield is working on your machine, you might still need another separate license for the iscmdbld part of the app.
  • We are connecting to the internal license server for licensing of installshield.
    In my peers machines, iscmdbuild.exe is also working.But it is not in my machine.Even the 'Flexnet Licensing Service' is also running.
    Could you please suggest what I need to check in that machine o troubleshoot the same.
    • 'not working' = fails to launch?? Or can be launched by fails, is there a log or anything in eventvwr?? is it a licensing issue, or do you just think its a license issue
      • When I build the exe using Wizard then it is building correctly.When I do with ISCMDBuild.exe then I am getting the console output as below screenshot.
        http://www.mediafire.com/view/rjafp97c9j0vqpq/ISCmdBuild.exe+error.PNG
        http://www.mediafire.com/download/rjafp97c9j0vqpq/ISCmdBuild.exe+error.PNG
      • Below is the console output, if you can't access the screenshot.
        Microsoft Windows [Version 6.1.7601]
        Copyright (c) 2009 Microsoft Corporation. All rights reserved.
        C:Userskirud01>'C:Program Files (x86)InstallShield2014SystemIsCmdBld.exe'
        -p 'H:ERwin ISMx64ISMERwin Data Modeler r9.64.02_64bit.ism' -r 'Release 1'
        InstallShield (R)
        Release Builder
        Copyright (c) 2013 Flexera Software LLC.
        All Rights Reserved.
        Build started at Aug 19 2016 03:07 PM
        Building Release: Release 1
        ISDEV : fatal error -7159: The product license has expired or has not yet been i
        nitialized.
        Product Configuration 1Release 1 - 1 error(s), 0 warning(s)
        Build finished at Aug 19 2016 03:07 PM
      • Can you check the license status of the iscmdbld from the IDE??

Hi all,
I'm working on our new product install which will the version 10.0 family. We are coming from 8.6 and earlier. When I run the upgrade from 8.6.x to 10.0.1 all works as planned. Old version detected and removed and the latest is put in place.
I thought I would look ahead and ensure a Major Upgrade in our new version family worked as expected. When I try moving from 10.0.1 to 10.0.257, the old is not removed and I see two instances in Add Remove Programs.
I can't for the life of me figure out what is wrong. I bumped the ProductVersion, obviously. Changed the ProductCode and PackageCode and changed the MaxVersion field value in the Upgrade Table.
All I see in the Log is Not Related and I don't see the ISFOUNDCURRENT property set in the second log. Here are images of the Upgrade settings in InstallShield..

You can download and see the install logs here.. http://community.flexerasoftware.com/showthread.php?p=477700#post477700


I even tried changing the Upgrade Code and creating a separate Upgrade table entry for the v10 family, but that didn't work either. On this new entry I tried including the MinVer, but to no avail.
I just can figure this out. It almost seems there is a problem using 10 versions at this point, but that's absurd.
Any help in this would be greatly appreciated!
Thanks MUCH in advance!!

Steps to follow in order to run HyperTerminal in Windows 10. Download Hyperterminal from the following link. Or you can copy the hyper-terminal files from Windows XP. Windows XP for HyperTerminal. Program Files Windows NT hypertrm.exe. WINDOWS system32 hypertrm.dll. Properties Dialog. Click Settings tab. Check Terminal Keys. Set Emulation to Auto Detect. Click ASCII Setup button. Under ASCII Sending, check Echo typed characters locally. Under ASCII Receiving, check Append line feeds to incoming line ends. How to setup hyperterminal WINDOWS 95/98 SETUP Start HyperTerminal by clicking on ‘Start - Programs - Accessories - Communications - HyperTerminal’. A window will appear with a number of default HyperTerminal setups (‘.ht’ files). Double click on ‘Hypertrm’ to start HyperTerminal. The next screen that appears depends on whether HyperTerminal has been run before. Click Start Programs Accessories Communications HyperTerminal. Once HyperTerminal opens, it will automatically prompt you to create a new connection if none exist. Specify a name for the connection, choose an icon, and click OK. In the Connect To dialog box, choose the COM port being used.