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.
tonia
Level 4 Flexeran
- Revenera Community
- :
- About tonia
Feb 05, 2019
05:50 PM
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
Labels:
Nov 24, 2018
09:27 AM
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
Labels:
Nov 16, 2018
07:40 PM
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
Nov 12, 2018
07:17 PM
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
Labels:
Nov 12, 2018
04:50 PM
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
Labels:
Nov 09, 2018
08:27 PM
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
Jul 18, 2018
08:14 PM
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
Jul 12, 2018
09:51 PM
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
Jun 27, 2018
11:09 PM
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
Jun 27, 2018
10:47 PM
Summary This article includes steps regarding how to activate an InstallShield Node-Locked License. Synopsis This article includes steps regarding how to activate an InstallShield Node-Locked License. Discussion To activate your InstallShield Node-Locked license:
1. Launch the InstallShield application.
2. Enter your product serial number in the following format (XXXX-XXXX-XXXX-XXXX).
3. 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: www.installshield.com/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 activation.xml file.
9. Launch the InstallShield application, once again. The Offline Activation dialog should be displayed.
10. Click the Load button and browse to the activation.xml file you recently saved.
11. Click the Activate button.
12. Click the Finish button.
... View more
Labels:
Jun 06, 2018
02:59 AM
Summary
This article provides information regarding the tsconfig executable file.
Synopsis
This article provides information regarding the tsconfig executable file.
Discussion
The tsconfig executable file is used to activate the InstallShield product and is located under the InstallShield System folder, the default paths are provided below.
32-bit Default Location: C:\Program Files\InstallShield\<PRODUCT VERSION>\System
64-bit Default Location: C:\Program Files (x86)\InstallShield\<PRODUCT VERSION>\System Launching the tsconfig.exe will display the InstallShield Product Activation dialog, where a serial number can be entered in order for node-locked licenses to activate the product. This dialog also has a link to configure the License server information for concurrent licenses. The tsconfig.exe accepts the following parameters when using a commandline prompt:
/repair
Repair license
/return
Return license to account
/activate
Activate license
/info
Show license information
/help
Show help information
/h
Show help information
/?
Show help information
/no_internet
Perform offline transaction only
/serial_number
Serial Number
/verbose
Log Verbose Information
/silent
Perform silent transaction
/set_license_server
Set license server
/feature
Feature Enum
/uninstall_service
Uninstall licensing service
... View more
Labels:
May 11, 2018
02:32 AM
1 Kudo
Summary Upgrade Error: A newer version of this application is already installed on this computer. Symptoms During a major upgrade installation, the following error message may be displayed: A newer version of this application is already installed on this computer. If you wish to install this version, please uninstall the newer version first. Click OK to exit the wizard. Cause This error has been known to occur when the product version of the ISPreventDowngrade item is not set correctly. Example: The Product Version is set to: Any earlier version Resolution By default, each project includes an ISPreventDowngrade major upgrade item, which enables you to prevent end users from being able to install the current version of your product over a future major version of the same product. To resolve this error message, set the Product Version of the ISPreventDowngrade item within a specific range of versions as follows: 1. Expand the Media folder. 2. Click Upgrades. 3. Expand the Upgrade Windows Installer Setup option. 4. Click the ISPreventDowngrade item. 5. In the Product Version section, select the option: Within a specific range of versions: (Minimum Version ? Maximum Version) 6. In the Minimum Version field, enter the product version number of the current project that includes your major upgrade item. The Maximum Version field can be NULL. Additional Information For more information about the ISPreventDowngrade support, take a look at the InstallShield Help Library topic: Preventing the Current Installation from Overwriting a Future Major Version of the Same Product
... View more
Labels:
Dec 17, 2014
12:39 PM
For Flexera Software's FlexNet Licensing pricing information, please contact Sales as follows. URL: http://www.flexerasoftware.com/producer/company/about/contact-us/ Thanks, Tonia
... View more
Dec 10, 2014
12:51 PM
The InstallShield 2014 Professional Edition includes one Standalone Build license. The Standalone Build module enables you to install only the part of InstallShield that compiles the installations, plus any redistributables that you may want to include. You can install the Standalone Build module on your build machine, and then run it from the command line. After purchasing, you can access the InstallShield 2014 Professional download and license files via the Product and License Center (https://flexerasoftware.flexnetoperations.com).
... View more
Dec 10, 2014
11:41 AM
Try to return and then reactivate the license from the command line. 1. From the command-line, change directories to the following default path: C:\Program Files\InstallShield\2012\System 2. Execute the following command: tsconfig.exe /return 3. Once the license has been successfully returned, execute the following command: tsconfig.exe /activate
... View more
Latest posts by tonia
Subject | Views | Posted |
---|---|---|
4515 | Feb 05, 2019 05:50 PM | |
1866 | Nov 24, 2018 09:27 AM | |
5709 | Nov 16, 2018 07:40 PM | |
1716 | Nov 12, 2018 07:17 PM | |
552 | Nov 12, 2018 04:50 PM | |
544 | Nov 09, 2018 08:27 PM | |
816 | Jul 18, 2018 08:14 PM | |
1826 | Jul 12, 2018 09:51 PM | |
1393 | Jun 27, 2018 11:09 PM | |
4771 | Jun 27, 2018 10:47 PM |
Activity Feed
- Kudoed Steps to generate the new FNMEA license file for Akshitha. Apr 03, 2024 07:10 PM
- Got a Kudo for Re: SunOs - Oracle database multitenant. Oct 22, 2020 01:03 PM
- Posted InstallShield Activation Error: The quantity specified exceeds maximum quantity allowed (0). on InstallShield Knowledge Base. Feb 05, 2019 05:50 PM
- Posted Manually Enable Integration with All Versions of Visual Studio .NET on InstallShield Knowledge Base. Nov 24, 2018 09:27 AM
- Posted Build Warning -7235 on InstallShield Knowledge Base. Nov 16, 2018 07:40 PM
- Posted Error: This copy of InstallAnywhere could not be registered using the node locked licensing file specified. on InstallAnywhere Knowledge Base. Nov 12, 2018 07:17 PM
- Posted How to Hide the Add/Remove Programs Option on InstallAnywhere Knowledge Base. Nov 12, 2018 04:50 PM
- Posted How to Enable Red Hat Package Management (RPM) Registration for Linux on InstallAnywhere Knowledge Base. Nov 09, 2018 08:27 PM
- Posted Build Error -7104 on InstallShield Knowledge Base. Jul 18, 2018 08:14 PM
- Posted How Do I Password Protect My Setup? on InstallShield Knowledge Base. Jul 12, 2018 09:51 PM
- Posted Run-Time Language Support in InstallShield on InstallShield Knowledge Base. Jun 27, 2018 11:09 PM
- Posted How to Activate an InstallShield Node-Locked License on InstallShield Knowledge Base. Jun 27, 2018 10:47 PM
- Posted TSCONFIG.EXE on InstallShield Knowledge Base. Jun 06, 2018 02:59 AM
- Posted Upgrade Error: A Newer Version of This Application is Already Installed on This Computer on InstallShield Knowledge Base. May 11, 2018 02:32 AM
- Posted FlexNet Licensing Pricing on FlexNet Embedded Forum. Dec 17, 2014 12:39 PM
- Posted InstallShield 2014 Developer and Build licenses on InstallShield Forum. Dec 10, 2014 12:51 PM
- Posted Re: Installshield 2012 reactivation fails on InstallShield Forum. Dec 10, 2014 11:41 AM
- Posted Re: New Install 2011 Express on InstallShield Forum. Dec 20, 2013 09:34 PM
- Posted Re: Difference between InstallShield and InstallAnywhere on InstallShield Forum. Dec 20, 2013 09:06 PM
- Posted Re: Uninstall doesn't work! on InstallShield Forum. Dec 20, 2013 06:18 PM
Contact Me
Online Status |
Offline
|
Date Last Visited |
May 01, 2024
05:17 PM
|