This document contains the NI Volume License Manager 3.2 known issues that were discovered before and since the previous release. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
The following items are known issues in Volume License Manager 3.2 sorted by Date.
ID | Known Issue | |||||
---|---|---|---|---|---|---|
424640 Return | The Getting Started Wizard incorrectly shows per Windows user account. The Volume License Manager Getting Started Wizard will show on different Windows user accounts. If there are multiple administrator accounts, each account will walk through the Getting Started Wizard when they first open Volume License Manager. However, the second account to walk through the wizard won't be prompted to install the license file and sees similar menus to a user who has just upgraded Volume License Manager. Workaround: N/A
| |||||
454572 Return | Backup licenses don't work for users that contain spaces in the username When using user-based licenses, if a user's username contains a space, it can successfully check out licenses from the Volume License server. However, if connection to the server is lost, the backup license that gets automatically generated will not work for that user. Workaround: Use computer-based licenses.
| |||||
719438 Return | Volume License Installer dialog appears twice If no administrator information has been entered for the server, creating a Volume License Installer (Tools >> Create Volume License Installer) results in a warning dialog that no administrator fields have been entered. Clicking 'OK' results in the same dialog reappearing. Workaround: Press OK twice.
|
Document last updated on 6/18/2019