If when trying to start Autodesk applications you receive a Network license not available error then please keep on reading, this guide is for you:
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.
Note: The Autodesk License Server Manager (version 11.16.2.0) is supported only on the following Mac operating systems:
- 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
Note: In this article we will refer to adsk_license.lic as network license file name. Feel free to change the actual name of the license file, but make sure to reflect the new name when using the commands below.
- Create a debug.log file in the /usr/local/flexnetserver/ directory using the following command:
- 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
Note: If folder permissions for /usr/local/flexnetserver/ are set to 775, then use sudo command to start the server. For example:
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.
Note: The Autodesk License Manager (11.16.2.0) is supported only on the following Linux distros:
- Red Hat® Enterprise Linux® 7
- Red Hat Enterprise Linux 6
- SUSE Linux Enterprise 12
- SUSE Linux Enterprise 11
To configure the license manager use the following steps:
- 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
/opt/flexnetserver/lmutil lmhostid
From the command output note the hostid in quotes, if the system has two active NIC cards, select the first MAC address.
lmutil - Copyright (c) 1989-2018 Flexera. All Rights Reserved.
The FlexNet host ID of this machine is "000c297949e0"
- To obtain the license server system hostname run the following command
/opt/flexnetserver/lmutil lmhostid hostname
From the command output note the hostname of the license server.
mutil - Copyright (c) 1989-2018 Flexera. All Rights Reserved.
The FlexNet host ID of this machine is "HOSTNAME=Centos7.localdomain"
- 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
Note: in this article we will refer by adsk_license.lic your network license file name.
- 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.
touch /var/lock/subsys/local
/opt/flexnetserver/lmgrd -c /opt/flexnetserver/licenses/adsk_license.lic -l /opt/flexnetserver/server_log.logNote: To ensure that the script will be executed during boot, run following command as root.
chmod +x /etc/rc.d/rc.local
- Make sure that all necessary ports are open:
- lmgrd.exe needs ports 27000 to 27009.
- adskflex.exe needs port 2080.
Note: Errors may occur if the network license file is corrupt or in the case of a combined network license it has incorrectly combined licenses. To learn more about combining licenses, see Combining License Files for Multiple Autodesk Products. Use the
License File Parser to verify that the license contains the appropriate products and
FLEXnet feature codes and does not display an error
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)
Note: If these port addresses are restricted by a router or firewall software, users on the remote side of the router will not have access to licenses controlled by the Network License Manager.
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.
Note: the license server information most often is recorded in LICPATH.lic file and can be verified there too. ADSKFLEX_LICENSE_FILE system variable supersedes LICPATH.lic. Thus, setting the system variable is preferable when this error is seen.
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.
Note: if needed the variable value can be increased to 10000000.
Mac/Linux:
Specify the Autodesk Network License server information in $HOME/.flexlmrc file.
Use a text editor to create a flexlmrc.txt file and save it in Plain text format (In TextEdit on Mac: Format - Make Plain Text) on desktop.
The file content should look like this, except with the name or IP address of the license server.
- ADSKFLEX_LICENSE_FILE=@SERVER_NAME _OR _IP
If the license server is on the same machine as the Autodesk software, use localhost as the license server name. Thus, the content of flexlmrc file could look like this:
- ADSKFLEX_LICENSE_FILE=@localhost
Note: On firewall restricted network or when accessing the license server via VPN, need to include TCP port/s (usually 27000 or 2080) into Autodesk License Server service as follows: ADSKFLEX_LICENSE_FILE=2080@SERVER_NAME _OR _IP
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.
If you consider yourself a power user or you value your privacy then firefox is the browser for you. It is open source and is packed with great features like reporting when your email has been used for a known data breach, it stops annoying pop-up notifications, stops browser fingerprinting, and many more. Firefox is also a cross-platform browser making it a great choice if you want to transfer and use your data across multiple devices with one account. The downside of firefox however is its speed, this browser is the slowest on this list, I guess features and advantages took their tool in the speed department, but if that is not a concern for you and you feel like the positives outweigh some slower speed, grab it 
Chrome browser has been a game-changer when it was released and even today some of its features are still great and needed. It is packed with some great features like tab freezing, for example, it is cross-platform meaning that also as firefox you can change data between browsers on different devices. it is a very expandable browser with tons of extensions and its speed performance is very very good. The downside of Chrome are two things sadly, one of them is its hunger for RAM, the browser takes a big chunk of RAM once it is active and on some older computer with limited RAM it performs slowly, another is telemetry which its sending, in other words, other browsers don’t come with the lingering fear that Google’s just a little bit too involved in all of our lives. But if downsides do not trouble you and you have a decent amount of RAM in your system chrome might be the best solution for you, grab it 
Or should I say Microsoft edge 2.0 since this new Edge is completely recoded and rethought, a completely new browser based on chromium. The first version of the edge was an inhouse attempt from Microsoft and it was a disaster, I guess the lesson was learned, and this new edge we have today is a great Browser, it is lightning fast and packed with some great features with one among them standing out I just love, that is the ability to save web pages as applications and truth to be told you have to try this in order to see al great advantages it offers. A very interesting feature is that edge itself wins the speed race from all of the 5 contestants here which is a great surprise. Of course, the downside of annoying Microsoft pushing it to be your default is, well it's Microsoft, as chrome is tied to Google so is edge tied to Microsoft, and the same dreaded feeling that big MS is watching you. If however, you do not concern yourself with these kinds of things, since it is already part of Windows 10, give it a spin and try it, I am sure you will at least love its blazing speed.
A new kid on the block, relatively unknown Browser Vivaldi offers some great customizable features no other one on this list offers, a very unique and down to each detail customization option, you can literally tweak each and every aspect of this browser making it best customizable and personal browser ever. How it is also based o chromium, every chrome extension works in it naturally. It is very good in speed and constantly updated and developed. The downside, well if you are anything like me, you could spend ages trying to customize it, ages, it has tons of features, and making it really feel and tick as you want can consume a really lot of time. If this thing does not bother you at all, grab Vivaldi 
Last but not least, we have another relic of the old browser age, the Opera browser. Packed with great security and great in-house features like a built-in VPN, built-in ad blocker, built-in crypto wallet, etc this browser seems like a swiss army knife. Opera is full of features and it shows once you start using it. The downside of opera is that its look and feel are specifically tailored to a certain type of user and not everyone will find that appealing or attractive, add some great but hidden and hard to come by features and it may go unnoticed. However, I think you should really give it a go since it definitely deserves more attention than it gets. Grab it 
The greatest lag and server crashes are pinpointed to game-creating events. When a player creates a new online game, the server needs to pull a lot of details from the database and make a game, due to some legacy code present this process takes some time and it is demanding a bit on the server-side, and although code was optimized to cater to more modern approach some legacy code still remains.
Another thing that was spotted to affect performance itself is player behavior, to be more specific, modern gamer behavior. Where players find good builds and runs on the internet and then go to farm-specific areas or bosses for loot or experience points, which in return boils down to making plenty and short runs that are made by creating games and after run eliminating them. Now pair that with the previous statement about legacy server and database code and you can add 1 and 1 and see how this might be an issue.
A lot of short games over legacy code are placing games in a state it was not designed for back in 2001 and therefore we have issues. Sadly solutions without completely rewriting the whole code are not very promising and they include rate limiting, which will prevent players to create many games in succession in a short period of time and maybe even login queues to drop a load on servers.
Blizzard reached to people in the whole company, even old diablo 2 developers to ask for advice and they say that they are working on solutions so they could lift limitations and have everything running fine. 