Causes of the error:
- The license on the License Server is invalid.
- The port for Autodesk Network License Manager is blocked.
- The client computer is configured with incorrect license server information.
- The license request is timing out on the client's computer before the license is obtained.
Solutions for the error:
Verify that the Autodesk License Server is setup with the correct license file.
To set up a license server for Windows, perform the following:
- Download and install the Network License Manager for Windows:
- Open LMTools and access the System Settings tab. Make a note of the "hostname" and "ethernet address" of the license server.
- Generate a Network License File in Autodesk Account.
- On the Service/License tab, select Configuration Using Services and LMTOOLS ignores license file path environment variables.
- On the Config Services tab, enter a name for the new service in the Service Name field.
- Fill the following fields, using the Browse buttons:
- Path to the lmgrd.exe - Navigate to this file: C:\Autodesk\Network License Manager.
- Path to the License file - Navigate to the new Autodesk.lic file, typically placed in: C:\Autodesk\Network License Manager\Licenses.
- Path to the Debug Log file: C:\Autodesk\Network License Manager.
- If no file is present, create a TXT file in Notepad and rename it “Debug.log.”
- Make sure the "Start Server at Power Up" and the "Use Services" boxes are checked. Then click Save Services.
- On the Start/Stop/Reread tab, click Start Server.
- On the Server Status tab, click Perform Status Enquiry.
- Licenses should display as active.
How to set up the Autodesk Network License Manager on a Mac.
- Apple macOS High Sierra 10.13
- Apple macOS Sierra 10.12
- Apple Mac OS X El Capitan 10.11
- Download Autodesk Network License Manager version 11.16.2.0 for Mac
- Download the nlm11.16.2.0_ipv4_ipv6_mac_universal.tar.gz file to the Desktop.
- To install the Autodesk Network License Manager:
- Double click on nlm11.16.2.0_ipv4_ipv6_mac_universal.tar.gz to unpack the installer package.
- After unpacking nlm11.16.2.0_ipv4_ipv6_mac_universal.pkg, will be /Downloads/adlm/FLEXnet folder.
- Double click on nlm11.16.2.0_ipv4_ipv6_mac_universal.pkg to start installation and follow the installation wizard.
- The license server will be installed in /usr/local/flexnetserver/ directory.
- Change permissions for /usr/local/flexnetserver/ directory to 777
- Open Terminal (located in /Applications/Utilities/Terminal) and enter the following command:
sudo chmod -R 777 /usr/local/flexnetserver
- Note: Administrator password may be asked. While typing no characters are shown, just type out the password and hit return key.
- Note: To start the license server only with elevated permissions (using sudo command), change permissions to 755 instead of 777.
- Create /usr/local/flexnetserver/licenses directory for network license file location
sudo mkdir /usr/local/flexnetserver/licenses
- Find the license server Host Name and Host ID.
- Generate the Network License File in the Autodesk Account
- Once the license file is generated, make sure it has a .lic extension (e.g. adsk_license.lic) and is in a plain text format and place it in /usr/local/flexnetserver/licenses directory
- Create a debug.log file in the /usr/local/flexnetserver/ directory using the following command:
touch debug.log
- To start the Network License Server use the following command:
/usr/local/flexnetserver/lmgrd -c /usr/local/flexnetserver/licenses/adsk_license.lic -l /usr/local/flexnetserver/debug.log
sudo /usr/local/flexnetserver/lmgrd -c /usr/local/flexnetserver/licenses/adsk_license.lic -l /usr/local/flexnetserver/debug.log
- To obtain license server status enquiry:
/usr/local/flexnetserver/lmutil lmstat -a -c /usr/local/flexnetserver/licenses/adsk_license.lic
- To stop the license server:
/usr/local/flexnetserver/lmutil lmdown -q -force
- Alternatively, run ps command to obtain process ids for lmgrd and adskflex and then kill those processes:
ps -ax | grep lmgrd
ps -ax | grep adskflex
kill -9
- (provide process ids obtained by previous commands individually)
How to set up the Autodesk Network License Manager on Linux.
- Red Hat® Enterprise Linux® 7
- Red Hat Enterprise Linux 6
- SUSE Linux Enterprise 12
- SUSE Linux Enterprise 11
- Download Autodesk Network License Manager v. 11.16.2 for Linux from this link
- Download the nlm11.16.2.0_ipv4_ipv6_linux64.tar.gz file to your desktop.
- To install the Autodesk Network License Manager run following command as root.
- tar –zxvf nlm11.16.2.0_ipv4_ipv6_linux64.tar.gz
- rpm -vhi nlm11.16.2.0_ipv4_ipv6_linux64.rpm
- The license server will be installed in /opt/flexnetserver/ directory.
- Find the license server Host Name and Host ID
- To obtain the license server system hostid run the following command
- To obtain the license server system hostname run the following command
- Generate your Network License File in Autodesk Account
- Once the license file is generated, make sure it has .lic extension (e.g. adsk_license.lic) and place it in /opt/flexnetserver/licenses directory. If the directory doesn't exits, create it with this command: sudo mkdir /opt/flexnetserver/licenses
- To start the Network License Server
- /opt/flexnetserver/lmgrd -c /opt/flexnetserver/licenses/adsk_license.lic -l /opt/flexnetserver/server_log.log
- To obtain license server status enquiry
- /opt/flexnetserver/lmutil lmstat -a -c /opt/flexnetserver/licenses/adsk_license.lic
- To stop your license server service
- /opt/flexnetserver/lmutil lmdown -q -force
- alternatively you can also run ps command to obtain process ids for lmgrd and adskflex and then kill those processes
- ps -aw | grep lmgrd
- ps -aw | grep adskflex
- kill -9 (provide process ids obtained by previous commands individually)
- To start the license server automatically after the system reboot
- Open /etc/rc.d/rc.local script as root and enter license server start up command in it.
- Make sure that all necessary ports are open:
- lmgrd.exe needs ports 27000 to 27009.
- adskflex.exe needs port 2080.
Verify that TCP ports (2080, 27000-27009) used by Autodesk Network License Manager are not blocked by Firewall.
The FLEXlm® based version uses the following incoming ports:- TCP ports 2080 (for the adskflex vendor daemon)
- TCP ports 27000 to 27009 (for the lmgrd master daemon, which uses the first open port in the range)
Verify that the client computer is configured with the correct license server name or IP.
Windows:
Clear license server information from the system registry.
- Type regedit in the Windows Search box and hit Enter key.
- Select the following registry key
- [HKEY_CURRENT_USER\SOFTWARE\FLEXlm License Manager]
- As the key is selected, in right panel ADSKFLEX_LICENSE_FILE will be visible.
- Right click on the key and delete it.
Specify the license server in ADSKFLEX_LICENSE_FILE system variable
- Go to Start > Control Panel > System and Security > System.
- Select Advanced system settings.
- On the System Properties dialog, click Environment Variables.
- Under System Variables, click New.
- Enter ADSKFLEX_LICENSE_FILE for the variable name and 2080@SERVER_NAME _OR _IP for the variable value.
If the license server is on a VPN or a remote network set the FLEXLM_TIMEOUT environment variable:
- Go to Start > Control Panel > System and Security > System.
- Select Advanced system settings.
- On the System Properties dialog, click Environment Variables.
- Under System Variables, click New.
- Enter FLEXLM_TIMEOUT for the variable name and 5000000 for the variable value.
- Click OK to save the setting.
Mac/Linux:
Specify the Autodesk Network License server information in $HOME/.flexlmrc file.
- ADSKFLEX_LICENSE_FILE=@SERVER_NAME _OR _IP
- ADSKFLEX_LICENSE_FILE=@localhost
Once flexlmrc file is created move it to user's $HOME folder as follows:
- Open a Terminal window
- Type open ~ (Mac) or nautilus ~ (Linux) to open $HOME folder
- Drag and drop flexlmrc.txt file from Desktop to the home folder.
- To make the file a configuration file, rename it to .flexlmrc (please note . [DOT] in front of the file name) by running the following command:
- mv flexlmrc.txt .flexlmrc (Mac)
- mv flexlmrc .flexlmrc (Linux)
Verify that the license server information registered with the product is correct (versions 2020 and later only)
In versions 2020 and later, the license server information is registered with the AdskLicensing service running locally on the workstation. When changing to a new license server, the old server information may still be registered with AdskLicensing and result in the error above, if this is not appropriately updated. See the below steps to solve this:- Click the Start menu and type cmd.
- Right-click on the Command prompt and choose "Run As Administrator."
- In the Command prompt, run the following command, followed by ENTER:
"C:\Program Files (x86)\Common Files\Autodesk Shared\AdskLicensing\Current\helper\AdskLicensingInstHelper.exe" change -pk PRODKEY -pv VER.0.0.F -lm "" -ls "" -lt""
Note:
- Replace PRODKEY with the product key correspondent to your product(s). See Look Up Product Keys for the full list.
- Replace VER with the version you are using. E.g. 2020 for AutoCAD 2020.
- Repeat this step for each software you need to reset.
- Open Registry Editor (Start > type regedit > ENTER).
- Navigate to HKEY_CURRENT_USER\Software\FLEXlm License Manager.
- On the right-side, verify of the ADSKFLEX_LICENSE_FILE key exists. If yes, remove it (right-click > Delete).
- Run the software again.
- Select Multi-user in the Let's Get Started screen.
- Follow the steps to connect to your license server.


California's Department of Fair Employment & Housing has widened its anti-discrimination lawsuit against Activision Blizzard and claims the publisher has been shredding vital documents relevant to the ongoing investigation.
A recent report from Kotaku described the department as offering poorly paid, highly insecure positions, with a culture of hostility towards LGBTQ+ testers. The DFEH's rewording of "employees" to "workers" now hopes to take these contractors' experiences into account.
"As a contract employee, I feel there's a lot of pressure to excel, impress, and move through the ranks as fast as you can before your contract ends and you're forced to go 3 months without income or find another job," Axios reports one worker saying. "I take pride in what I do, but it feels like it's never enough."
Activision's contentious hiring of union-busting third-party law firm WilmerHale "directly interferes" with its own investigation, it says. By going to WilmerHale, Activision appears to be claiming that all work related to the investigation is privileged and can't be shared with DFEH.
The suit also claims that Activision HR shredded documents related to "investigations and complaints", against its legal obligation to retain them during the investigation. The relevant parts of the updated lawsuit were shared by Axios reporters Stephen Totilo and Megan Farokhmanesh, the former also noting that the DFEH "fixed their misspelling of Bill Cosby's name".
"DFEH is also informed and aware that documents and records have not been maintained as required by law or by the DFEH's Document Retention Notice," the complaint reads, "including but not limited to documents related to investigations and complaints were shredded by human resource personnel and emails are deleted thirty days after an employees separation."
With its Rift model, Oculus set itself as a big player in VR. Now the company is slowly bowing out of the dedicated, tethered VR headset with its latest Quest 2 designed to primarily be a standalone headset.
In case you do not know, tethered headset means that the headset itself is connected to your PC and is using its power to drive your VR experience.
Now technical specifications of Quest 2 are pretty OK and it can drive stuff pretty decently and if you want you can purchase the dedicated cable to connect it to your PC for the full experience of games requiring more capable hardware.
Oculus Quest 2 is the cheapest headset on this list and with its stable performance, is highly recommended.
Although the headset itself is nothing revolutionary or special its controllers are. They can track individual finger movements, making games (that take advantage of them) much more immersive than the standard trigger grips on other controllers.
The Index's higher refresh rate makes for smoother action, as well, which is another nice bonus. If you already have an HTC Vive or Vive Cosmos Elite, and their base stations (not the regular Cosmos), you can buy only the controllers.
The PlayStation VR is compelling thanks to Sony backing its development, plus the PlayStation 4's affordability and availability compared with gaming PCs. All you need is the headset, a PlayStation 4, and a PlayStation Camera (now included with most PlayStation VR bundles).
Not really the best of the bunch but still one of the top ones for console gaming. Sony is working on a new PlayStation VR system for the PlayStation 5, with redesigned controllers. The new headset hasn't been revealed yet, but the company has released a preview of the new controllers.
HP headset is one which you get if you want the best image quality in VR headset, sadly controllers did not follow the same quality of headset itself. But this is still a pretty decent headset overall and worth the purchase.
HTC's Vive Cosmos is the upgraded version of the Vive. It features a higher resolution and replaces the external base stations with outward-facing cameras for motion tracking. It's a comprehensive package for whole-room VR.
HTC recently released the Vive Pro 2, a high-end VR headset targeting both enterprise users and consumers. This new headset features a 2,448-by-2,448 resolution display for each eye, making it the highest-resolution headset currently available. It's also more expensive than the Cosmos Elite.
Sadly one thing that is bringing this headset down is the price.
The application settings screen will open, in upper tabs locate Compatibility and left-click on it.
After the click, you will find yourself in application compatibility settings.
In this window, you will face different options to run the chosen application in various modes in order to make it run. How settings are self-explanatory and different applications will need different settings sadly we can not cover them all but your safest bet is to run them in an environment where they have worked.
For example, if the application was working fine in Windows XP and required administrator privileges, check Run this program as an administrator and Run this program in compatibility mode for Windows XP. 