Summary This article provides information regarding how to download AdminStudio. Discussion The AdminStudio product download is available at the Flexera Software Product and License Center. The  Product and License Center allows you to download products, as well as related product files. To access the AdminStudio product download via the Product and License Center: Log In to the Community. Click on "Other Resources" and select "Product and License Center" From there, find the column with AdminStudio listed and select the “LET'S GO” button below that column Once you have been logged in to the Product and License Center, select "Product list" from the right-hand navigation list If applicable, select the AdminStudio product from the Product List. Select the applicable product version from the Product and File Downloads list. Note: If applicable, clicking the Release Archive tab will give you access to previous versions of AdminStudio. Select the file you wish to download. Click the download hyperlink or select one of the Advanced Download Options. More information can be found in the knowledge base article " How to Access the Product and License Center ": https://community.flexera.com/t5/Downloading-Products/How-to-Access-the-Product-and-License-Center/ta-p/99340 Additional Information AdminStudio Product Serial Number Guidelines: -20 characters long -All characters are capitalized -Do not start with the letters ISMTK -Formatted as follows: (7-3-10): XXXXXXX-XXX-XXXXXXXXXX or (4-4-4-4): XXXX-XXXX-XXXX-XXXX for AdminStudio 2014 and later. -No letter "O"s are contained in the serial number, it's the number zero "0". -Make sure to include the dashes/hyphens (-) when entering. -There are no extra spaces either before or after the serial number.   Order Numbers typically are formatted as one of the following formats: SSF-XXXXXXXXXX Additional information about the Download and License Overview for AdminStudio 2016 and Later can be obtained from the following document: Download and Licensing Overview for AdminStudio   ... View more

Summary FLEXnet Connect is a solution that Flexera Software sells to software vendors that is designed to help you stay connected with your customers after they install your applications. Synopsis FLEXnet Connect is a solution that Flexera Software sells to software vendors that is designed to help you stay connected with your customers after they install your applications. Keeping software updated is one of the many benefits of FLEXnet Connect, but Flexera Software also recommends that software vendors build in an option to disable automatic update checking. If you are using an application that uses FLEXnet Connect, your application may have a configuration option to disable update checking. Please check your application?s menu options. If your application does not have this option, Flexera Software has created a tool called the Software Manager that can disable automatic update checking. The Software Manager utility lists all applications currently using FLEXnet Connect on your computer and the FLEXnet Connect's status with that application. Discussion You may already have the Software Manager installed. If the Software Updates or Program Updates shortcut is listed in your Start menu, then the Software Manager is installed. If you do not have the Software Manager installed, follow these instructions to download and install it: Download and install the Software Manager: Download the latest FLEXnet Connect 6.1 Software Manager and save it to your Desktop. The latest FLEXnet Connect Software Manager can be downloaded here. 2. Double click on the FLEXnet connect executable and follow the instructions to install the Software Manager. Once installed, you can run the Software Updatesshortcut to start the Software Manager. Download and install the uninstall for Software Manager: Download the Update Manager uninstaller and save it to your Desktop. 2. Double click SoftwareManagerUninstall.exe and follow the instructions to uninstall the Software Manager. Note: The SoftwareManagerUninstall.exe only removes entries from the Windows registry which are responsible for starting the common software manager after a reboot. No files are actually removed. ... View more

Summary This error message is a system-specific error and can be caused by a system-specific setting. This article attempts to list all the possible steps that have known to resolve this error. Symptoms When running an installation created with an InstallShield product, the following error occurs at the beginning of the installation: Error -1607: Unable to Install InstallShield Scripting Runtime This error message is a system-specific error and can be caused by a system-specific setting. This article attempts to list all the possible steps that have known to resolve this error. Depending on your system, you may need to try some or all of the listed solutions. Cause This does not occur with InstallShield 12 and later. The architecture in InstallShield 12 and later has several advantages over the earlier architecture. End users no longer encounter error 1607, error 1608, or other COM/DCOM run-time errors that are related to finding the running IDriver.exe file. When these errors occurred under the earlier model, they were difficult to resolve, often requiring changes to DCOM settings. Also, the reliance on the running object table made the model brittle across the spectrum of usage scenarios, including Fast User Switching and Windows Terminal Services. Resolution Update the ISScript engine on your computer by downloading the latest one. For more information, see Setup Is Unable To Find or Update ISScript.msi. Make sure that the Installer folder in the Windows directory has full access privileges. The Installer folder may be hidden on your computer, so you will have to set your computer to see hidden files and folders and then set the proper permissions to the <WINDOWSFOLDER>\Installer folder: A. Show Hidden Files and Folder Launch Windows Explorer by pressing the Windows key + E or select Start > Run and typeexplorer. Select Tools > Folder in the Windows Explorer window. Select the View tab. In the Advanced Settings pane, select Show hidden files and folder. B. Set the Installer folder attributes Locate the folder <WINDOWSFOLDER>\Installer: Windows NT and 2000: C:\WINNT\Installer Windows 95/98/Me/ XP: C:\Windows\Installer Note: In some instances this directory doesn't appear on Windows XP machines. Follow these steps to view the folder: a. In Windows Explorer select View > Toolbars and select Address Bar if there isn't a check box next to it. b. In the Address Bar type in the full path: C:\WINDOWS\Installer. 2. Right-click on the Installer folder and choose Properties. 3. Select the Security tab. 4. Make sure the System, Administrators and the specific user have Full Control of this folder. C. Repeat the instructions in Step B for the Temp directory. To locate the Temp directory on your machine, refer to the article Clean the Temp Directory. 3. Make sure that the InstallShield registry key in the Windows registry has full access privileges. Select Start > Run and type regedt32. Browse to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield Check the permissions of this key: Windows XP users can right click and select Permissions. Windows 2000 and NT users navigate to the Security menu and select Permissions. 4. Assign both the Administrators and System group Full Control if they don't already have it. For an idea of what the permissions property dialog will look like, see step 2B-4. 4. If the installation is located on a network drive, copy all of the files to the local hard drive (i.e., Desktop or Temp directory) and attempt to run the installation again. 5. Install the Windows Installer engine on your computer to make sure that it is not corrupt and that it is properly registered on your computer. For more information, see How Do I Install the Windows Installer Engine on My Computer Using InstallShield. 6. Make sure you have full administrative privileges on your computer. This does not apply to Windows 95, 98, and ME. 7. Make sure no other applications, installations, or processes are running in the background. For more information, see Manually Detect and End Previously Running Installation Process and Close Applications Running in the Background . 8. Make sure to check the location from where the installation is being run. If the downloaded installation files are stored in a directory path that contains special characters, such as "&", "-", ".", etc, change the path to something that does not contain these characters. Bad path: C:\downloads\Palm\palm desktop & hotsync\x\setup.exe Good path: C:\downloads\Palm\palm desktop hotsync\x\setup.exe Does Your Issue Still Exist? If after following these instructions your product failed to install, you'll need to contact your vendor. See the Who to Contact page for more information. Related KB Articles Q108353 Q108373 Q108351 Q108345 Q108213 Q111114 ... View more

Summary This article explains how to suggest changes to the ARL, SKU Library, or PURL. Question How can I suggest changes to the FlexNet Manager Suite ARL, SKU Library, or PURL? Answer Flexera welcomes requests from our customers for updates to the Application Recognition Library (ARL), Stock Keeping Unit (SKU) Library and Product Use Rights Library (PURL). I have not purchased a maintenance plan or it has expired. Can I still suggest changes? Simple content requests which fulfill the criteria below can be submitted to the Content team. However, Flexera will not provide updates on the progress or completion of any request and they may be denied by the Content team. Where do I submit the content request? Content requests should be submitted through a support case in our Community at  https://community.flexera.com When will my request be completed? Requests will be qualified and prioritized at our discretion. As general guidelines: We accept all submissions sent through Support. Most requests we receive are completed within 1 to 2 weeks. For example, ARL updates are often available within 1 to 2 weeks; SKU and PURL requests are usually available monthly. Large or particularly complex requests will be assessed separately. For any request that we're unable to deliver in a reasonable time-frame, Flexera Services may be available. Why has my request not been added? Please keep in mind that some applications, SKUs, and PURLs can't be added to our published libraries, such as: Application evidence that has been modified due to customer repackaging or don't include valid publisher, product or version information. The provided SKU details are incomplete, ambiguous, or otherwise unverifiable. Product Use Rights that are only available to a single customer through a unique contractual term. What information do I need to provide for the request to be fulfilled? ARL Unassigned Evidence Customers may generate Evidence submissions and submit these to Flexera Support, which will be attached to a Support ticket and redirected to the Content Team. This can be done in one of two ways, depending upon the version of FlexNet Manager Suite for Enterprises installed. All versions allow export of evidence into a Microsoft Excel spreadsheet, or some versions of FlexNet Manager Suite include a Share button on the Applications views that will generate a submission file. This submission can be emailed directly from the Share button wizard when enabled or can be saved locally and attached or uploaded separately. Note: Detailed instructions for exporting uninstalled evidence can be found in the attachments section. Classifications If you believe that an application has the wrong classification e.g. that it's currently listed as commercial, but it should be freeware, this can be submitted to the Content Team as well.  If possible, please also provide the web link from the vendor which proves the correct classification. New Applications All new application submissions need to follow the recommendations in 'Guidelines for Submitting Evidence in FNMP 2014+.pdf' which is attached to this KB article. If no evidence is known to be associated with the applications, please attach a spreadsheet with the following column headers completed for each application: Publisher, Product, Version, and Edition. SKU Library SKUs can come in many different formats, including price lists, purchase orders or simply just SKU values. Customers are encouraged to submit SKUs for processing to Flexera Support. This can be done in one of two ways: 1. Provide the original SKU data source (e.g., price list or purchase order); or 2. Use the attached template to provide SKU details. While we are happy to accept all submissions, even if you only have the SKU number. Please note that the more information you can provide, the quicker we can add it to the library. The following information for SKUs and PURLs are very helpful in speeding up adding to the content libraries: SKU value Publisher and Description License Type e.g. Upgrade, maintenance, full license A template is attached to this article that can be used to provide information on missing SKUs. If you can't provide this information, please send us the SKU anyway but please be aware that these typically take a lot longer to process as extensive research must be carried out and in some cases, we may not find enough information to process some SKUs. Sending as much information as you have on SKUs is preferable. PURL We welcome PURL requests or updates for how we can improve the PURL. A 'PURL Request' template is attached to this article, which can be used to submit PURL use rights questions or adjustments. The following information will be required for a review to occur: Publisher Product Use Rights Question or Adjustment Requested Reference Documentation Once we receive the completed template, we will review the documentation and provide feedback. How is the accuracy of the content libraries maintained? We have a large team of experts in software licensing and application recognition dedicated to maintaining and enhancing our content libraries. We publish updates weekly for the ARL and Monthly updates for the SKU and PURL, averaging tens of thousands of updates each month across the ARL, SKU, and PURL.  Additional Information The attachment 'Submission Template and Guidelines.zip' includes: 1. SKU / PURL submission templates 2. Guidelines for Submitting ARL data 3. How to engage with our Technical support team to request the content library changes ... View more

Summary Manual PURL Download & Importer instructions for FNMP 9.0 - 9.2.3 Synopsis The download & installation of the SKU & PURL libraries can be performed automatically for servers that can download files from the Internet. Servers without an Internet connection, will need to have these libraries downloaded & installed manually. The following instructions are for FlexNet Manager Platform / Suite versions 9.0 and later. Earlier versions of the product should refer to Knowledge Base #M100999. Discussion Downloading the PURL blades for FlexNet Manager Platform (FNMP) needs to be performed by an installation of FNMP. If the server does not have access to the internet to perform this download, it can be performed on a separate computer, by installing the FlexNet Manager Platform Remote Console. This computer downloads the SKU library, along with the PURL blades. These files are then transferred to the FNMP server and are imported. Please note that the PURL vendor specific publisher downloads also require that the current Application Recognition Library (ARL) has been download and installed. Refer to Knowledge base article #M100995 for further information on downloading the ARL. Installation Installation instructions for FlexNet Manager Platform Remote Console can be found in the ?FNMP Installation Guide? under ?Installing a Remote Compliance Console?. Hint: after installing the console, remember to run the ?ManageSoft.Activation.Wizard? program as an administrator, when importing the license key. Once installed, the file ?ImportPURL.exe? needs to be added. To do this, either copy the ?ImportPURL? file from the ?bin? directory of your FNMP server, or from the link at the bottom of this article (see additional information section). This file needs to be copied to the ?bin? directory of the Remote Console. In a typical installation, this can be found in: C:\Program Files (x86)\ManageSoft\DotNet\bin Usage Download This process is normally run each time you receive notification that new content is available in the product use rights libraries. An alternative is to configure a scheduled task to perform the check weekly and download as required. To download the library files, use the ?ImportPURL? command. This file has the following options: -i Import -dl Download -h Show usage (help) To download the current SKU & PURL files, open a command prompt, navigate to the ?bin? directory and type the following command: ImportPURL -dl <path> Example: C:\Program Files (x86)\ManageSoft\DotNet\bin\ImportPURL ?dl c:\temp   When completed the directory used for the <path> will contain one or more .cab files. These files need to be transferred to your FNMP server   Server Import To import the library files into the server, use the ?MgsImportRecognition? command. This file has the following options: -u Use this Username -p Use this Password -pu Use this Proxy Username -pp Use this Proxy Password -ps Use this Proxy Port -dl Download -ia Import this ARL file -is Import this SKU or PURL file -h Show usage (help)   Navigate to the ?bin? directory and type the following command: MgsImportRecognition -is <path>\<filename>.cab   Example: C:\Program Files (x86)\ManageSoft\DotNet\bin\MgsImportRecognition ?is c:\temp\PURL.cab   This needs to be repeated for every .cab file that has been downloaded and transferred. For example: C:\Program Files (x86)\ManageSoft\DotNet\bin\MgsImportRecognition ?is c:\temp\PURL.cab C:\Program Files (x86)\ManageSoft\DotNet\bin\MgsImportRecognition ?is c:\temp\PURL-adobe.cab C:\Program Files (x86)\ManageSoft\DotNet\bin\MgsImportRecognition ?is c:\temp\PURL-Microsoft.cab Troubleshooting All actions performed by the PURL Importer tool will be logged to the console and to a '%TEMP%\ImportPURL.log' file on the computer it is executed upon; unless specified elsewhere. Additional logs are also generated for each set of publisher information imported, again in the '%TEMP%' directory for the user executing the tool. These will contain details of any errors which occur. Additional Information The attachment (public_ImportPURL.zip) to this article contains two attachments: public_ImportPURL_90_91.zip contains ImportPURL.exe for 9.0 & 9.1 public_ImportPURL_92.zip contains ImportPURL.exe for 9.2 Please ensure you use the correct file for your console version. Download URL's If you require the URL's to download the ARL and PURL files to perform the manual update process please review the "Manual Updates of Library Data" topic in Chapter 2 of the Installing FlexNet Manager Suite On-Premises PDF file available for download from Flexera HelpNet at https://helpnet.flexerasoftware.com/?product=FlexNet%20Manager%20Suite%20On%20Premises. The URL's and update process is outlined in this document. ... View more

Summary If you use a proxy server in your environment you would often configure this in Internet Explorer and mgsimportrecognition.exe would use the IE settings however in some cases you might not be able to use the proxy in Internet Explorer e.g. another application won't work through the proxy. Synopsis If you use a proxy server in your environment you would often configure this in Internet Explorer and mgsimportrecognition.exe would use the IE settings however in some cases you might not be able to use the proxy in Internet Explorer e.g. another application won't work through the proxy. Discussion If this is the case you will need to manually enter the proxy server using the -ps switch in mgsimportrecognition e.g. mgsimportrecognition.exe -ps <ProxyServer>:<ProxyPort> -pu <ProxyUsername> -pp <ProxyPassword> The proxy username and password may not be required, it all depends on your configuration. Additional Information Once the command has been run once with the -ps -pu -pp switches it should save the configuration so that next time it works by just running the executable. The configuration settings are saved in the following registry key: KEY_LOCAL_MACHINE\SOFTWARE\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\Recognition ... View more

Summary If you find that it will be necessary to move your license to a new machine, the license must first be returned or deactivated from the previous machine before it can be activated on the new machine. Synopsis AdminStudio and WiseScript Editor node-locked licenses are single-machine, single-user licenses according to the End-User License Agreement (EULA). This means that they can be activated on one machine and accessed by one user. If moving a license to a new machine is required, the license must be returned or deactivated from the machine on which it is currently activated, before attempting to activate the license on a new machine. Please note that there is a return limit for each type of licence: Node Locked Licence If your licence is a node locked licence, then you are allowed to return/deactivate/transfer your licence up to a maximum of four times per year. Concurrent Licence If your licence is a concurrent licence and you would like to return/transfer it from the current licence server to a new/another licence server, then please note that there is a return/transfer limit of 2 returns/transfers per year. Discussion This section included steps for both online and offline activation methods of deactivation. Online Deactivation: 1) Reinstall the software on the previous machine (if it has been uninstalled). 2) From the command-line change directories to the appropriate default path: Version Default Path AdminStudio 8.5 C:\Program Files\Macrovision\AdminStudio\Common AdminStudio 8.6 C:\Program Files\Macrovision\AdminStudio\Common AdminStudio 9 C:\Program Files\AdminStudio\9.0\Common AdminStudio 9.01 C:\Program Files\AdminStudio\9.01\Common AdminStudio 9.5 C:\Program Files\AdminStudio\9.5\Common AdminStudio 10 C:\Program Files\AdminStudio\10.0\Common AdminStudio 11 C:\Program Files\AdminStudio\11.0\Common AdminStudio 11.5 C:\Program Files\AdminStudio\11.5\Common AdminStudio 2013 C:\Program Files\AdminStudio\2013\Common AdminStudio 2014 C:\Program Files\AdminStudio\2014\Common AdminStudio 2015 C:\Program Files\AdminStudio\2015\Common AdminStudio 2016 C:\Program Files\AdminStudio\2016\Common AdminStudio 2018 C:\Program Files\AdminStudio\2018\Common AdminStudio 2019 C:\Program Files\AdminStudio\2019\Common AdminStudio 2020 C:\Program Files\AdminStudio\2020\Common WiseScript Editor C:\Program Files\WiseScript Package Editor\WiseScript Package Editor Note: For 64 bit machines, the default location will be under the (x86) Directory. For example: AdminStudio 11.0 on a 64-bit machine will be located at C:\Program Files (x86)\AdminStudio\11.0\Common WiseScript Editor on a 64-bit machine will be located at C:\Program Files (x86)\WiseScript Package Editor\WiseScript Package Editor 3) Based on the product installed, execute the following Command: For AdminStudio use TPSconfig /return For WiseScript Editor use TSWconfig /return Activation Server URL: activationservice.installshield.com Note: We suggest allowing incoming and outgoing traffic to and from *.flexerasoftware.com and *.installshield.com as well as making sure that ports 80, 443 & 8443 are open. Offline Deactivation: 1) Reinstall the software on the previous machine (if it has been uninstalled) 2) Open up a Command Prompt and CD to the appropriate default path. 3) Execute the following command which will generate a request code: For AdminStudio use TPSconfig /return /no_internet For WiseScript Editor use TSWconfig /return /no_internet 4) For AdminStudio 2014 and later, process the request code at our Product and License Center self-service web page. ... View more

Summary This article explains how Inventory Manager and FlexNet Manager Suite are licensed and the behaviour of these products when license consumption approaches or exceeds the purchased license entitlements. Synopsis In this article, we'll explain how Inventory Manager and FlexNet Manager Suite are licensed and the behaviour of these products when license consumption approaches or exceeds the purchased license entitlements for this product.   Discussion Inventory Manager licensing How license consumption is measured Inventory Manager is licensed per computer/device under management, as determined by there being at least one installation record for that computer in Inventory Manager. Computers that have been discovered by IM but which have no installation records do not count towards license consumption, as they're deemed to not be managed. To calculate license consumption, run the following SQL query on the Inventory Manager database: SELECT COUNT(DISTINCT ComputerID) FROM Installation What happens when a license is breached When license consumption exceeds 80% of the overall license entitlement, a warning is displayed the next time the Inventory Manager Server console is opened. The user can configure the amount of time that should pass before the next warning is shown. When Inventory Manager exceeds its license entitlement, all subsequent attempts to open the administration console are denied. All users are locked out of the administration console until license consumption is reduced to an acceptable level. FlexNet Manager Suite licensing How license consumption is measured FlexNet Manager Suite is licensed per computer. Ignored and discarded computers do not count towards license consumption. For releases 8.2.1 to 8.6, computers linked to retired or disposed assets do not count towards license consumption. For release 9.0 and later, virtual machines without agent inventory do not count towards license consumption. Note that computers require a license regardless of whether they have been imported from IM, SMS or any other inventory source. To calculate license consumption for release 9.0 and later, run the following SQL query on the FlexNet Manager Suite database: SELECT COUNT(*) FROM dbo.ComplianceComputer AS cc LEFT OUTER JOIN dbo.Asset AS a ON a.AssetID = cc.AssetID -- Ignore ignored, placeholder and discarded computers WHERE cc.ComplianceComputerStatusID NOT IN (2, 4, 5) AND -- Ignore computers linked to retired or disposed assets (a.AssetID IS NULL OR a.AssetStatusID NOT IN (4, 5)) AND -- Ignore remote devices cc.ComplianceComputerTypeID <> 4 AND -- Ignore light virtual machines cc.ComplianceComputerInventorySourceTypeID <> 2 To calculate license consumption for servers, run the following SQL query on the FlexNet Manager Suite database: select count(1) from compliancecomputer where OperatingSystem like '%windows%server%' or OperatingSystem like '%linux%' or OperatingSystem like '%Ubuntu%' or OperatingSystem like '%centos%' or OperatingSystem like '%sunos%' or OperatingSystem like '%sun_os%' or OperatingSystem like '%aix%' or OperatingSystem like '%bsd%' or OperatingSystem like 'VMWare ESX%' or OperatingSystem like '%Mac%server%' or OperatingSystem like '%HPUX%' or OperatingSystem like '%HP_UX%' or operatingsystem like '%SuSE%server%' or operatingsystem like '%redhat%server%' or operatingsystem like '%red hat%server%' or operatingsystem like '%RedHatEnterpriseAS%' or operatingsystem like '%RedHatEnterpriseES%' or operatingsystem like '%Red Hat %AS%' -- ADDM evidence or operatingsystem like '%Red Hat %ES%' -- ADDM evidence or operatingsystem like '%RH-EL-%' or operatingsystem like '%RH-ES-%' What happens when a license is breached? If you exceed the number of active computers for which FlexNet Manager Suite is licensed, users are given a warning each time the administration console is opened for the next 30 days. If the license breach is not resolved within 30 days, FlexNet Manager Suite subsequently does not allow the addition of any new computers, as follows: The inventory importer doesn't import any new computers. However, computers already in FlexNet Manager Suite are updated as normal. The administration console doesn't allow manual creation of a new computer.   Workaround To remove unwanted devices, please view R emove unwanted computers and network devices from ManageSoft . Additional Information Note: If you have Inventory Manager and Flexnet Manager Suite installed on the same computer, then you need to run each query, and the highest of these will be used by the license enforcement to calculate the license count. ... View more

Summary This article outlines the processes involved in updating the FlexNet Manager Suite (FNMS) Application Recognition Library (ARL). Included in this article is information about the Flexera Software factory process, the automatic update process, the manual update process, and the ARL update behavior. Introduction Generally an updated ARL will be automatically downloaded and installed by operational FNMS systems everyday at 1am. Discussion Flexera Software factory process Flexera Software continuously updates and improves rules and information in the ARL. This process includes the addition of new applications and associated evidence, and the extension and revision of existing titles. Revisions may include the standardization of data formats, such as application publishers, inclusions of details such as categories and classifications for application titles, and additional evidence. New evidence may include installer evidence for recognition and file evidence to allow usage data to be collected on a greater range of applications. The ARL is published as an SQL script hosted on the ManageSoft website (www.managesoft.com). This script is executed both to install the ARL on a new installation of FNMS, and to update an existing installation with new data. There are two ways to download and run this script: The Recognition data import scheduled task (configured in the Microsoft Task Scheduler) will collect and run the script on your schedule You can run the command-line tool, MgsImportRecognition.exe (typically installed to C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform\DotNet\bin), which will perform the same task as the automatic procedure. Automatic update process The Recognition data import task, by default, will check for an update at 1am each day. If a new version of the ARL is found, the database update script will automatically be downloaded and executed, updating your database. To confirm results from the most recent ARL update attempt, you may check Recognition.log. This log file can be found, in a default installation, in C:\ProgramData\Flexera Software\Compliance\Logging\Content (see below for more details about configuring the log file location). The first line of this file will show you the version of the ARL that the script attempted to install, and the last line will tell you if the latest download was successful. If the last line reads "Completed executing SQL file" then the latest ARL download and installation was completed successfully. If an error has occurred, the end of the log file will contain a message similar to the following: ------------------------------------------------------------------- Msg 50000, Level 16, State 1, Server QA01A, Procedure ARLConsistencyCheck_ONE_FUID_per_ONE_InstallerEvidence, Line 68 ERROR! Consistency check failed! Starting: Rollback to previous ARL state Finished: Rollback to previous ARL state The first line shows the error message (which will vary depending on the cause of the error), the procedure where the error was found, and the line of code which it references. The second line gives a brief description of the error, and the final two lines state that the database is being reverted back to the previous ARL state. For more detailed information on the error, scroll up in the log file to look for a sentence beginning with ?WARNING!? This is followed by a description of the error, and where applicable, details of the affected records in the ARL. If the ARL update is unsuccessful, please open a case with Flexera Software Support team, and include a compressed copy of the Recognition.log, mgsImportRecognition.log, and importPURL.log,. Manual update process The automatic update process can be disabled if you prefer to run the task manually. To turn off the Import ManageSoft Application Recognition Library task, view the task properties using Microsoft Task Scheduler and uncheck the Enabled (Scheduled task runs at specified time) box. To run the update process manually, you can either right-click on the Recognition data import task and select Run; or you can run the ARL update using the MgsImportRecognition.exe command-line tool. In your operating system command line, navigate to C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform\DotNet\bin, and then enter MgsImportRecognition.exe to check for updates and install the latest ARL update. Logs similar to one created in the automated update process is created in this scenario, too. For more detail on the manual update process see the System Reference Guide. Log file The ARL update process, whether run by scheduled task or manually, creates a Recognition.log file. From release 8.0 of FNMP, the Recognition.log file is located, by default, in the Temp directory of the current account. For example, with the normal account of Adminstrator running the executable, the log file will be written to C:\Documents and Settings\Administrator\Local Settings\Temp. You can quickly access the Temp directory of the current account by typing %TEMP% in the address bar of Microsoft Windows Explorer. From FNMS 2018 R2 on, the default location for the log is C:\ProgramData\Flexera Software\Compliance\Logging\Content ARL update behavior The execution of the ARL script can add new records, modify existing records, and delete old records. New records are added to increase the number of applications recognized. Records are modified to make them more reliable and to help standardize the ARL. Old records that are no longer needed are deleted. Usually the modifications will be accepted, but in a few instances an ARL modification will be blocked. There are three reasons why an ARL update would be blocked: The record has been modified locally The record has a license attached The modification would result in a primary key clash Records modified locally For any given application, the ARL may update several database tables including SoftwareTitle, FileEvidence, InstallerEvidence, WmiEvidence, and the links that exist between these. In order to preserve any local changes that you have made to your data, each of these areas is guarded by separate checksums. If a checksum shows that you have altered an item, that item will no longer be updated by the ARL (although other related but unchanged items may still be updated). For example, if you edit a record of installer evidence linked to an application, then that installer evidence record will no longer be updated by the ARL, although the related application may still be updated. Similarly, if you add new evidence to an application (thereby changing the links between items), the ARL will no longer update relationships around this application (that is, will not make any changes to those links), but may still update the basic records. Also note that the checksums do not protect every field in a record, and you may change the 'unprotected' fields without impact. You can restore all your locally modified records to match the ManageSoft ARL by changing an internal ForceUpdateAllRecords configuration setting value to "true". This value can be set by running the following SQL command on your ManageSoft database: USE ManageSoft UPDATE SoftwareRecognitionConfiguration SET Value = 'true' WHERE Property = 'ForceUpdateAllRecords' Once this command has run, all records will be modified to match the ARL every time an ARL update is downloaded. To change it back to the default behavior, replace 'true' with 'false' and re-run the above command. Note: All of your local modifications will be lost when you update the ARL with this value set to 'true'. Records with attached licenses If the ARL attempts to delete an application that has been linked to a license, then that deletion will be blocked. Your database will keep the application and its attached license even though it is no longer in the published ARL. Any other types of modifications to the same record (other than deletion) should be updated successfully, as long as you have not also manually modified details on the application. Primary key clashes A primary key clash results when an ARL update tries to modify an existing record, or add a new record, in such a way that it will exactly match primary key values on an existing record. This is only likely to occur when an old record has been deleted from the published ARL, but has not been deleted locally for one of the two reasons listed above.  Additional Information Reporting issues and requesting updates Issues, queries and requests for updates to specific titles in the ARL may be directed to the Flexera Software Support team. When reporting issues about a particular title in the ARL, please be sure to provide: Screenshots showing complete details of how the title appears in your local ARL, including information from the following tabs from the application properties dialog: General, File Evidence, Installer Evidence and History. A copy of the current Recognition.log (C:\ProgramData\Flexera Software\Compliance\Logging\Content). Download URL's If you require the URL's to download the ARL and PURL files to perform the manual update process, they can be downloaded from the Product and License Center. ... View more

Synopsis Sometimes, the FlexNet Code Insight application can appear to hang or become unresponsive. The initial approach to debugging this situation is usually to generate a thread dump to see where the process currently is in the Java call stack. Discussion Process on Linux Option 1: jstack The jstack utility comes with the JDK and is located in the bin folder inside the JDK home directory. We recommend using the JDK with the same version as the Java process running Tomcat for compatibility. The JDK archive downloads can be found here. Find the Process ID (PID) of the Java process running FNCI using one of the following methods i. jps (this can be run from $JAVA_HOME/bin/ if it is not in your path) This might return a process called "Bootstrap" with an associated process ID. ii. ps aucx | grep java This might return a process called "java" with an associated process ID. iii. ps -ef | grep palamida This is useful if you have multiple Java processes running and need to verify which one is the FNCI process. Check for the path of your FNCI installation in the output. Use jstack to generate the Java stack trace to an outfile. i. Run the command: $JAVA_HOME/bin/jstack , pass it the Java process ID, and direct it to an outfile: Take three of these thread dumps, about a minute or two apart each, so that the outputs can be compared for differences. Alternatively, you can use the kill -3 command with the process ID to send the thread dump to the $FNCI/tomcat/logs/catalina.out file instead. Process on Windows The process on Windows, when running Tomcat interactively (i.e., not as a Windows service) is very similar to the above. Find Tomcat's Java process ID using Task Manager, then from the CMD line, run %JAVA_HOME%\bin\jstack with the process ID as the argument and redirecting to an outfile (same as Linux). However, if running Tomcat on Windows as a service, the process is a bit more involved, so please contact support for the full set of instructions. ... View more

Symptoms Please consider the following scenario: - Select an existing Purchase Order ? or even create a new one - Select an Purchase Order Line that is not linked to an Entitlement ? or create a new PO Line and assign a license directly by the ?Licenses? tab, click ok and close the PO Line - Select ?Edit/View?? for the PO Line and go to the ?Licenses? tab to assign an Entitlement and click ok (applies only for existing PO) - Now, the focus is back on the PO Line Manager with the recently linked PO Line, but the Icon did not change from green to red o I understand that this will remain unchanged unless the ?Apply? button was selected ? from my point of view that?s not an defect - If the customer want?s to review the PO Line by selecting ?Edit/View?? again, the assigned Entitlement is gone. - After confirming all changes by using ?Apply? the linked Entitlement is shown as well as the icon of the PO Line has changed. Resolution This issue has been addressed. ... View more

AMS sending multiple identical emails when user clicks Edit Data button on Data Entry Tab . Steps To Reproduce 1. Logon as a customer company user and create a new application request. 2. After submitting the request an email is then sent to all relevant users notifying them of the new request. 3. Click the Edit Data button, enter a reason for editing the step then click Continue Edit. Resolution Result: Multiple emails are sent from AMS notifying all relevant users of a Change of Data even though the user has not made any changes yet. Expected: No email is expected until the user actually changes something and only one email is necessary showing updates made by the user. ... View more

Summary この記事では、InstallShield の同時接続ライセンスの借用についての解説と、ライセンスの借用を行う前に確認すべき留意事項が挙げられています。 Synopsis この記事では、InstallShield の同時接続ライセンスの借用についての解説と、ライセンスの借用を行う前に確認すべき留意事項が挙げられています。   ナレッジベース記事の英語版 は、 KB Q213787  を参照してください。 [To see an English version of this KB article, see KB Q213787 .]   Discussion 借用とは、FlexNet Licensing Server が配置されているネットワークへの接続を切断して、同時接続ライセンスの使用を可能にできる機能を意味します。       「   InstallShield の同時接続ライセンス用のライセンス サーバーを設定する   」  の解説にある手順を実行すると、ライセンスサーバー マネージャー (lmadmin) によって、チェックアウト可能なライセンスが表示されます。「Activatable」 アイコンをクリックして、利用可能なライセンスの数を確認してください。次の lmadmin のスクリーン ショットでは、InstallShield 2013 Premier Edition (IS2013-PREM-CC) の同時接続ライセンスが 2 つチェックアウト可能になっています。また、現在、借用状態になっている、または解除 (Detached) されているライセンスが 0 であることも分かります。また、このスクリーンショットでは、InstallShield 2013 Standalone Build (IS2013-SAB-CC) が 1 つチェックアウト可能になっていて、借用状態になっているライセンスがないことも分かります。         チェックアウトされたライセンスが、借用中でない場合、[Concurrent] アイコンをクリックした時、ライセンスはチェックアウト状態、もしくは使用中であることが示されます。次のスクリーン ショットでは、InstallShield (IS2.win.prem) が 1 つチェックアウトされていることが示されています。         ライセンスが借用された場合、[Activatable] アイコンをクリックすると、ライセンスが借用中、または切断状態であることが示されます。下のスクリーンショットでは、2 つある InstallShield 2013 Premier (IS2013-PREM-CC) の同時接続ライセンスのうち 1 つが現在、借用中であることが分かります。Standalone Build (IS2013-SAB-CC) の同時接続ライセンスは、1 つだけ借用が可能になっています。       ライセンスの借入方法についてのステップバイ ステップ ガイドについては、「   ライセンス サーバーから InstallShield または InstallShield Collaboration ライセンスを借用する   」をご覧ください。ライセンスを借用する場合、ライセンス   の借用ウィザードで、借用期間 (ライセンスを借用する日数) を入力する必要があります。いったん借用期間が過ぎると、借用されたライセンスはクライアント側で無効になり、再度、ライセンス サーバーでチェックアウトが可能な状態になります。       指定可能な日数の値は、1 から 60 です。FlexNet Licensing Server では、借用期間が過ぎるまで、借用されたライセンスをキャンセルできませんので注意してください。借用期間が過ぎる前にライセンスを再度利用可能な状態に戻す必要が発生した場合、クライアントからライセンスを返還します。       借用期間が過ぎる前にライセンスを返還するには、以下の手順に従います:       FlexNet Licensing Server と同じネットワークに接続している状態で、InstallShield を起動します。   [ヘルプ] メニューで、[バージョン情報] をクリックします。[バージョン情報] ダイアログ ボックスが開きます。ダイアログ ボックスで、借用期間の残り日数が表示されます。   [ライセンスの返還] ボタンをクリックします。       返還が成功すると、ライセンスは FlexNet Licensing Server に戻され、再度チェックアウト可能な状態になります。       クライアントから、FlexNet Licensing Serve に接続できなかった場合、エラーダイアログが表示されます。 Additional Information 一旦ライセンスが借用されると、FlexNet Licensing Server では、借用されたライセンスをキャンセルすることができません。つまり、借用期間が終了するまで、FlexNet Licensing Server から強制的にライセンスを返還することは不可能になります。 ライセンスは、ユーザーによって返還されるか、または借用期間が完全に終了するまで使用できません。 借用期間が終了する前にライセンスを返還するには、クライアントが、ライセンスが借用された FlexNet Licensing Server に接続されている必要があります。 クライアントのハードウェアで障害が生じた場合、ライセンスは、借用期間が終了するまでチェックアウトは不可能になります。 限られた数のライセンスを使用しているユーザーは、ライセンスを借用すべきかどうか、および借用期間の長さを決定するとき、これらの条件を念頭に置いておく必要があります。 クライアント側におけるハードウェア障害を懸念するユーザーは、借用されたライセンスにアクセスできなくても問題が発生しないとあらかじめ分かっている日数に、借用期間を制限するようにしてください。 ... View more

Summary This article provides the steps for manually creating a Customer Community User in Salesforce. Synopsis When a contact is added as an entitlement contact, a customer community login is automatically created for the user, but there may be some scenarios in which a contact does not need to be an entitlement contact but still needs access to the Customer Community. This article provides the steps for manually creating a Customer Community User in Salesforce. Discussion In order to create a Customer Community User, a Contact must exist in Salesforce. These steps assume that a Contact already exists. While there are various methods that can be used to find a contact in Salesforce this method searches for the Contact email. Within the Salesforce global search bar (at the top of Salesforce), search for the contact email. If a contact exists with that email, the record will be displayed within the Contacts section of the search results. Click on the Contact Name. On the Contact Detail page, click on the Manage External User button towards the top of the page. Click on the Enable Customer User option. (If you do not see this option, the customer already has a Customer Community User) This will take you to the Customer Community User profile page. By default the users name will be the email address of the contact. (User Name must be unique) Also select Customer Portal User - SLO in the Profile field. Click Save. The customer will be sent an email automatically with the username and a temporary password for the account. The customer must change the password before logging in. ... View more

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 AdminStudio 11.x and up). The Return License button is located in the About dialog box (which is displayed when you click About AdminStudio on the Help menu). Starting with AdminStudio 8.5, 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: AdminStudio Default Path AdminStudio versions 8.5 and 8.6 C:\Program Files\Macrovision\AdminStudio\Common AdminStudio versions 9.x and up C:\Program Files\AdminStudio\<VERSION NUMBER>\Common Note: For 64 bit machines, the default location will be located in the Program Files (x86) Directory. 2. Execute the following command: AdminStudio: TPSconfig /return ... View more