Summary This article provides information regarding how to resolve the activation error: "The quantity specified exceeds maximum quantity allowed (0)". Symptoms Your attempt to activate your license is denied, and the following message is displayed: The quantity specified exceeds maximum quantity allowed (0). Cause This activation error indicates that the license you are attempting to activate has already been activated on another machine. Resolution To resolve this error, it will be necessary to return the license to the account on the activation server. This process is sometimes referred to as a deactivation. You can return the license by uninstalling the application or by clicking the Return License button (available in InstallShield versions 2010 and up). The Return License button is located in the About dialog box (which is displayed when you click About InstallShield on the Help menu). Starting with InstallShield 2008, you can also return the license from the command line, by executing the return command as follows. 1. From the command-line change directories to the appropriate default path: InstallShield Default Path InstallShield 2008 Express C:\Program Files\Macrovision\IS 2008 Express\System InstallShield 2008 Pro/Premier C:\Program Files\Macrovision\IS2008\System InstallShield Express versions 2009 and up C:\Program Files\InstallShield\<VERSION NUMBER> Express\System InstallShield 2009 and up Pro/Premier C:\Program Files\InstallShield\<VERSION NUMBER>\System Note: For 64 bit machines, the default location will be located in the Program Files (x86) Directory. 2. Execute the following command: InstallShield: TSconfig /retur Related KB Articles Q201081: Deactivation of InstallShield and AdminStudio ... View more

Summary This article provides information regarding how to manually enable integration with all versions of Visual Studio .NET. Synopsis This article discusses the manual steps necessary to enable integration between InstallShield and Visual Studio .NET so that InstallShield projects can be created and added to Visual Studio .NET Solutions. Discussion 1. Use RegSvr32.exe to register IsDevEdt.dll, IsDevPkg.dll, and IsDevWiz.dll which are found in the System sub-directory of the main InstallShield installation directory location. 2. Locate devenv.exe corresponding to the version of Visual Studio.NET you are interested in. For example, InstallShield 2013 supports Visual Studio.NET 2012 and this is located in the following folder: C:\Program Files\Microsoft Visual Studio 10\Common7\IDE 3. Run devenv.exe /setup in a command prompt (DOS) window. NOTE: InstallShield Express users should substitute IsExpEdt.dll, IsExpPkg.dll, and IsExpWiz.dll in Step 1. Related KB Articles For an alternative approach to enabling Visual Studio .NET integration, see the Knowledge Base article Manually Enable Integration with All Versions of Visual Studio .NET and Enabling Microsoft Visual Studio .NET Integration and Repair InstallShield Integration with Visual Studio Additional Information Only certain versions of Microsoft Visual Studio .NET are supported with specific versions of InstallShield products. For example: Microsoft Visual Studio .NET 2017 is supported by InstallShield 2016 SP1 and later. Microsoft Visual Studio .NET 2015 is supported by InstallShield 2015 and later. Microsoft Visual Studio .NET 2013 is supported by InstallShield 2013 and later. Microsoft Visual Studio .NET 2012 is supported by InstallShield 2012 Spring and later. Microsoft Visual Studio .NET 2010 is supported by InstallShield 2011 and later. Microsoft Visual Studio .NET 2008 is supported by InstallShield 2009 and later. Microsoft Visual Studio .NET 2005 is supported by InstallShield 11.5 and later. Microsoft Visual Studio .NET 2003 is supported by InstallShield X and later. Microsoft Visual Studio .NET 2002 is supported by InstallShield Developer. If your version is not listed above, please review the Release Notes for your particular release as this contains the most current information ... View more

Summary Build Warning -7235 Synopsis When building an InstallShield Express project, the following warning may occur: ISEXP : warning -7235: InstallShield could not create the software identification tag because the Tag Creator ID setting in the General Information view is empty. Discussion By default, software identification tagging is enabled in all Express projects. This applies to new projects created with InstallShield Express, as well as projects that were upgraded from earlier versions of the InstallShield Express Edition.   If you build a release in an Express project without entering data in the required software identification tag setting (the Unique ID, Tag Creator, and Tag Creator ID settings in the General Information view), and you leave software tagging enabled in the project, the build warning -7235 occurs. This build warning explains that the software identification tag could not be created and included in the installation because a specific required setting was left blank. To resolve this warning, enter an appropriate value in each specific setting, or set the 'Use Software Identification Tag' setting in the General Information view to 'No'.   Related Documents Including a Software Identification Tag for Your Product http://helpnet.flexerasoftware.com/isxhelp23/isxhelp23.htm#helplibrary/SWIDOverview.htm ... View more

Summary This article provides information on how to entitlement administrators can manager support contact for a support plan. Discussion 1. Login to the Flexera Customer Community. 2. Click the Support Plans option under Get Support. 3. Click the Manage Users hyperlink for the applicable maintenance plan. 4. Select the desired user name from the Technical Contact drop down list. 5. Click the Update button. If the name of the desired contact is not available for selection please have them register with the community and contact support to have their Account updated to your Account. ... View more

Summary This article provides steps to resolve the error: This copy of InstallAnywhere could not be registered using the node locked licensing file specified. Synopsis This article provides some causes for the following error while attempting to launch InstallAnywhere: This copy of InstallAnywhere could not be registered using the node locked licensing file specified. Please check if the license file specified at <PATH TO LICENSE.LIC> is a valid license file for this node. Discussion This error may occur as a result of one of the following: Hard Drive or MAC address Change, or License Move InstallAnywhere is Running Under a Different Admin Account. License.lic file Not Found in the Expected Location Additional Information Return a License in the Product and License Center How to Obtain and Configure an InstallAnywhere Node-Locked License File Activate InstallAnywhere 2011 and Later with a Node-Locked License Register InstallAnywhere from the Command-line Licensing Overview for InstallAnywhere 2011 and Later ... View more

Summary This article provides information regarding how to hide the Add/Remove Programs option in InstallAnywhere. Synopsis This article provides information regarding how to prevent the uninstaller from registering itself with Windows Add/Remove Programs in InstallAnywhere. Discussion The InstallAnywhere variable, $REGISTER_UNINSTALLER_WINDOWS$, tells the uninstaller whether it should register itself with Windows Add/Remove Programs. To hide the Add/Remove Programs option, set this variable to FALSE. Additional Information InstallAnywhere HelpNet topic: Standard InstallAnywhere Variables ... View more

Summary This article provides steps on how to enable Red Hat Package Management (RPM) Registration for Linux. Synopsis On supported Linux systems, RPM registration creates a virtual package and uses it to make entries to the RPM database. This can be configured in the RPM Specification Settings dialog. Discussion To launch the RPM Specification Settings dialog box: Click General Settings on the Project page. Click Platforms, and then expand the UNIX Tag. In the Enable RPM Registration (Linux Only) setting, select Yes from the drop down menu, and then click the ellipsis button (...) in this setting. Add the applicable RPM Specification Settings and then click the OK button. Additional Information RPM Specification Settings Dialog Box ... View more

Summary This article includes steps regarding how to activate newer versions of the AdminStudio and InstallShield Node-Locked Licenses. Synopsis This article includes steps regarding how to activate newer versions of the AdminStudio and InstallShield Node-Locked Licenses. Discussion A new Node-Locked License activation process was introduced with the release of AdminStudio and InstallShield versions 2014. To activate a Node-Locked license: 1. Launch the application. 2. Select the option to Activate or Purchase InstallShield/AdminStudio. 3. Enter your product serial number/activation code in the following format (XXXX-XXXX-XXXX-XXXX). 4. Click the Activate button. If the activation process fails: 1. Select the offline activation option. An offline activation request will be generated. 2. Save the offline activation license.request file. 3. Click the Next button. 4. The next dialog should indicate that an offline transaction is pending. 5. Go to the following website to process your offline activation request: https://flexerasoftware.flexnetoperations.com/control/inst/offlineActivation 6. Click the Choose File button and browse to the license.request file that you recently saved. 7. Click the Process button. 8. Save the response.xml file. 9. Launch the application, once again. The Offline Activation dialog should be displayed. 10. Click the Load button and browse to the response.xml file you recently saved. 11. Click the Activate button. 12. Click the Finish button. ... View more

Summary This article provides steps regarding how to activate an AdminStudio Node-Locked License Synopsis This article provides steps regarding how to activate an AdminStudio Node-Locked License. Discussion To activate your AdminStudio Node-Locked license: Launch the AdminStudio application. Enter your product serial number in the following format (XXXX-XXXX-XXXX-XXXX). Click the Activate button. If the activation process fails: Select the offline activation option. An offline activation request will be generated. Save the offline activation license.request file. Click the Next button. The next dialog should indicate that an offline transaction is pending. Go to the following website to process your offline activation request: https://flexerasoftware.flexnetoperations.com/control/inst/offlineActivation Click the Choose File button and browse to the license.request file that you recently saved. Click the Process button. Save the activation.xml file. Launch the AdminStudio application, once again. The Offline Activation dialog should be displayed. Click the Load button and browse to the activation.xml file you recently saved. Click the Activate button. Click the Finish button. ... View more

Summary This article provides information regarding how to return or deactivate a WiseScript Editor license. Synopsis Before moving a Adminstudio WiseScript Editor license to a new machine, it will be necessary to first return or deactivate the license from a command line. This article includes steps regarding how to return or deactivate the WiseScript Editor license from a command line. Discussion The following steps should allow you to return or deactivate a WiseScript Editor license from a command line: 1. From the command-line, change directories to one of the following default paths: a. C:\Program Files (x86)\WiseScript Package Editor\WiseScript Package Editor b. C:\Program Files\WiseScript Package Editor\WiseScript Package Editor 2. Execute the following command: tswconfig.exe /return 3. You should receive a message that the license was successfully returned 4. You can then proceed to activate the license on the new machine The following command can also be used to activate the WiseScript Editor license from a command line: tswconfig.exe /activate ... View more

Summary Build error 7104 information Symptoms When building a project, the following error may occur: ISDEV : error -7104: The destination of component %1 is the GlobalAssemblyCache. The component must contain a key file. Cause This error occurs at build when a component destination is the Global Assembly Cache and a key file is missing from the component. Resolution Include a key file, or mark one of the existing files as a key file to the applicable component, and then rebuild once again. 1. Click on the Component view. 2. Select the applicable component and then expand the component's view. 3. Click the Files view. 4. Add or modify the existing file. Right click the applicable file and then select the option, ?Set Key File?. 5. Rebuild your release. Additional Information For more information on this error, please refer to the HelpNet article Build Errors and Warnings ... View more

Summary This article describes how to password protect a setup. Question How Do I Password Protect My Setup? Answer InstallShield gives you the option to password protect your setup using the following steps: 1. Select your Release. 2. Click the Setup.exe tab. 3. In the Password Protect Launcher property, select Yes. 4. In the Launcher Password property, type in a valid password for verification. InstallScript Project Type: 1. Select your Release. 2. Click the Setup.exe tab. 3. In the Media Password property, type in a valid password. 4. In the Show Password Dialog property, select Yes to set the SHOW_PASSWORD_DIALOG system variable to a non-zero value, which executes the password-checking code in the OnCheckMediaPassword event handler function?s default code. If Show Password Dialog property is set to, "No", you will need to enter your own code in the script in order to request the password from the end user and check it by calling FeatureValidate. Related Documents InstallShield Helpnet: Setup.exe Tab for a Release ... View more

Summary Run-Time Language Support for InstallShield Express Synopsis This article provides information regarding run-time language support for the InstallShield Express Edition. Discussion Language support varies, depending on the edition of InstallShield that you are using. With the InstallShield Express Edition you can create an installation that runs in a particular language; that is, the run-time dialogs that appear during installation contain text in the specified language. Creating an installation for one language is the first step in completing your installation project when you plan on distributing your installation in a number of different languages. When you create your project, you can select one of the supported languages from the Project Language list on the New Project dialog box. Your selection determines the language in which all of your installation?s run-time dialogs appear. You can create different installation projects for each language in which you want to distribute your application. If you plan to distribute your installation in both English and German, for example, you can create two different installation projects?one in which you select English as the project language and one in which you select German as the project language. If you want your installation to appear in a different language, you can export the string entries, translate the strings, and then import them back into your project. Note: You cannot change the language after you have created your project, except by exporting and importing the string entries for translation. After you have created your project, you can use the Text and Messages view to edit the text that appears in the run-time dialogs. The Express project type available in InstallShield supports only one language per installation project. If you want to create an installation that runs in more than one language, it is recommended that you upgrade to the Premier edition of InstallShield; this edition has built-in support for creating projects that run in more than one language. It also offers granular control at both build time and run time over which files are installed based on the language. In addition, the Premier edition enables you to add unsupported languages, beyond the built-in languages, to projects. Related Documents Exporting Strings Importing String Tables Editing Run-Time Strings Text and Messages View ... View more