A Quick Guide to Resolving Uncdms.dll Error Code

Fix Error 0x8024a11a or 0x8024a112

What is Error 0x8024a11a or 0x8024a112 ? If you are trying to update your Windows 10 computer and just when you were done downloading the feature update and about to install it, you encounter an error message saying:

“We’re having trouble restarting to finish the install, Error 0x8024a11a, 0x8024a112, 0x80070005 or 0x80070032”

And so to fix this problem, this post will give you a couple of possible solutions. Refer to the options given below to get started.

Option 1 – Restart your computer many times

This is the first thing you can try since there are instances when the Windows Update process gets stuck for a minor thing and restarting the computer usually helps in resolving the issue. All you have to do is click the Restart now button. However, if it does not work, you can use the Power buttons from the Start Menu or WinX Menu. Aside from that, you can also use your power buttons such as Alt + Ctrl + Del to restart your computer. And during the boot process, it is recommended that you restart your computer in Safe Mode or even in a Clean Boot State. After that, you can restart your computer in normal mode. This will make sure that no third-party processes will be able to interfere with the Windows Update process. To put your PC in a Clean Boot State, here’s what you have to do:

Log onto your PC as an administrator.
Type in MSConfig in the Start Search to open the System Configuration utility.
From there, go to the General tab and click “Selective startup”.
Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
Next, click the Services tab and select the “Hide All Microsoft Services” check box.
Click Disable all.
Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
After that, try to install the Windows Updates or upgrade again.

Option 2 – Try running the Windows Module Installer

The Windows Module Installer is a built-in service in the Windows operating system that could help you resolve the Windows update error 0x8024a11a or 0x8024a112. You need to make sure that this service is Started and that its Startup type is set to Automatic – you can do this via Services Manager or by executing the command given below in an elevated Command Prompt.

Tap the Win + R keys to open the Run dialog box.
Then type “command prompt” in the field and hit Enter to open Command Prompt.
And in the elevated Command Prompt type in the following command and hit Enter:

SC config trustedinstaller start=auto

After executing the command successfully, you should see the “[SC] ChangeServiceConfig SUCCESS” message on the Command Prompt window.

Option 3 – Run the DISM tool

You can also run the DISM Tool as it helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” which could help in fixing the Windows update error 0x8024a11a or 0x8024a112.

Open the Command Prompt with admin privileges.
Then type in the following commands and make sure to hit Enter right after you type each one of them:
- Dism /Online /Cleanup-Image /CheckHealth
- Dism /Online /Cleanup-Image /ScanHealth
- exe /Online /Cleanup-image /Restorehealth
Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 4 – Run the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why you’re getting the errors 0x8024a11a and 0x8024a112. To run the SFC command, follow the steps given below.

Tap Win + R to launch Run.
Type in cmd in the field and tap Enter.
After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

Windows Resource Protection did not find any integrity violations.
Windows Resource Protection found corrupt files and successfully repaired them.
Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 5 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows update error 0xca00a000. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 6 – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error 0x8024a11a or 0x8024a112. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically.

Not enough USB controller resources Error

As you know, USB is now being widely used in all devices with USB A as the leading type with most devices based on it. Peripheral devices such as Pen Drives, External Hard disks, and many more also use a USB port. On the other hand, USB C is also coming up to be the next big standard in the computing world because of its high transfer speeds, wider compatibility as well as support for external Graphics Processing Units. However, just recently, USB 3.0 ports have been reported to cause the following error to pop up on Windows 10 computers every time a USB device is plugged in.

“Not enough USB controller resources. The controller does not have enough resources for this device.”

To fix this error, here are some guidelines you can check out. Make sure to follow them carefully.

Option 1 – Try to use a lower generation USB port

The first thing you can do is to try using a lower generation USB port as this issue mostly occurs when a device is connected to a USB 3,0 port. This means that you have to plug in your device to a USB 2.0 port and then see if it fixes the error or not. You can easily decipher a USB 3.0 port from a USB 2.0 port as the former is in blue.

Option 2 – Try to use a dock

You could also try to use a dock to resolve the error. Note that when too much power on laptops and notebooks are drawn from the USB ports and as a USB 3.0 port draws more power compared to a USB 2.0 port. Thus, if you plug in your USB storage device into a USB 2.0 port with the help of a dock, it should fix the problem.

Option 3 – Try disabling the xHCI Mode option in the BIOS

First, boot your computer into the BIOS.
Once your computer has booted, go to the Advanced tab.
Next, make sure that the entry for “xHCI Pre-boot mode” is set to Disabled under the USB Configuration section.
Now save the changes you’ve made and then restart your computer to Windows 10 and see if the error is now fixed.

Option 4 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:

First, click the Start button and type “device manager”.
Then click on the “Device Manager” from the search results to open it.
From there, look for the “Universal Serial Bus controllers” option and then right click on each one of the USB drivers, especially the Generic USB Hub driver, and then select the Update Driver from the menu.
Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 5 – Run the Hardware and Devices Troubleshooter

You could also run the Hardware and device Troubleshooter to try and fix the “Not enough USB controller resources” error.

The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
After opening Settings, look for the Update and Security option and select it.
From there, go to the Troubleshoot option located on the left-hand side of the list.
Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Software review series: Adobe Photoshop

From photo editing and compositing to digital painting, animation, and graphic design you can do it all in Photoshop. Bring ideas to life across desktop and iPad. Magically transform images with the power of AI. Learn new skills and share your projects via Livestream. Started as a photo editing application, photoshop has surpassed the original ideas and designs in the following years growing with each release and including more tools and flexibility not matched in other applications. Photoshop was the first to introduce many new features and set standards for other applications. How years have passed product grew and innovation was pushed forward, it took some time but eventually, photoshop was able to set itself as the industry-standard application for pixel editing and it holds that position even today. Throughout the world artist all over the globe are using it to create digital art in various fields be that illustrations, film, photography, texturing, etc. Its vast majority of tools and possibilities as well as its extensibility with plugins, actions, brushes have cemented it in the highest place in any designer or artist toolkit. Today you can get it as a part of a creative suite for a monthly fee on the official adobe website and even if you do not need other creative suite applications photoshop is worth the fee alone. Simply you have to try it, learn it, and then harvest its power. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

New MS Surface coming in October

In the Windows ecosystem, MS Surface laptops are among the best laptops on the market, they are regarded as equivalent to Apple MAC laptops but for Windows. Microsoft Fall 2022 Event will be held on October 12th at 10 AM. The event itself will be held right before it kicks off its annual, developer-focused Ignite event in Seattle from that same day through October 14.

This event is the first in-person event that Microsoft has held since the beginning of the pandemic. We expect the launch of the Surface Pro 9 and the Surface Laptop 5, and maybe Surface Studio 3 as well. There are also some rumors about products themselves like choices between an ARM or x86 CPU but nothing is confirmed so far, we can just wait and see.

Moving mouse pointer via the keypad in W11

In Windows 11 if you do not own a mouse or it has suddenly malfunctioned you can still move your arrow on-screen using the numeric pad. In this guide, we will guide you on how to turn this option ON, follow this easy guide step by step.

Press ⊞ WINDOWS + I to open Windows settings
Click on Accessibility on left
Scroll down to reach the interaction section on the right and click on Mouse
Click on Switch beside Mouse keys under accessibility options
Set your preferences
Close settings

Settings will be as always automatically applied.

How to Fix Task Scheduler Error 0x80070057

One of the important functions in the Windows operating system is the Task Scheduler. It can automatically run various tasks at a certain time where you’ll have to add a task that needs to be executed and then choose the time it has to run at. So when that time comes, the Task Scheduler will run the task automatically. However, some users reported getting an Error 0x80070057 where the Task Scheduler fails to start. This kind of error may be due to a disabled service that prevents the service from running. It is also possible that the antivirus program interfered with the task – it could be that the Task Scheduler is somewhat in the block list since the antivirus adds it to the list automatically when it’s installed. On the other hand, it could be that you lack administrator-level privilege which is why the Task Scheduler was not able to carry out the task. To fix this issue, here are some suggestions you can try.

Option 1 – Try to restart the Task Scheduler service

As mentioned, it is possible that the Task Scheduler service could be disabled. You could have disabled it when trying to enhance your computer’s performance and whatnot. Thus, you need to verify if it’s running or not and then restart it.

First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
You will see a list of Services and from there, look for the Task Scheduler service and double click on it.
After that, go to the General tab and click on the Startup Type options and then select “Automatically” from the given list.
Click on the “RUN” option and select the “Restart the Service” option.
And click on the “After Second Failure” option and then select the “Restart-Service” option again.
Now click on the “After Subsequent Failures” tab and select the “Restart the Service” option.
Finally, click on the Apply and OK buttons and then run the Task Scheduler and see if the issue is now fixed.

Option 2 – Try to temporarily disable the anti-virus program

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed in your computer. Thus, disabling them or any security software installed on your computer is always a good idea you can try when you’re not able to access the shared drive on your computer. There are times when you encounter problems like the Task Scheduler Error 0x80070057 due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program for the meantime and check if it fixes the error or not.

Option 3 – Run the Task Scheduler with an administrator account

Like pointed out, the Task Scheduler Error 0x80070057 may be due to the lack of admin privileges. Thus, you have to log in to an administrator account and try running the Task Scheduler again. It is also recommended that the administrator account you’re going to use as a password when logging in.

Option 4 – Repair the Task Scheduler by deleting corrupted tasks

Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps:

Tap the Win + R keys to open the dialog box for Run.
Next, type in Regedit and click on OK or tap Enter to open the Registry Editor.
Then navigate to this path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTree

Note: In this path, you can see all the tasks that are currently set in the Task Scheduler. And since it would be hard to tell which one of them is corrupted, you have to delete the latest one in Task Scheduler last. But before you do so, make sure that you take note of the ID of the tasks. And for you to get the ID, you have to select the task you wish to delete and double click on the ID string located on your right-hand side, and then copy it in the Notepad.

Right-click on the task name and then delete it.
After that, delete the very same GUID which you have copied earlier from these folders:
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheMaintenance
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTasks

Note: You might not see the same GUID from these folders but if you see it, delete it right away.

Next, navigate to this location: C:/Windows/System32/Tasks
Delete the very same tasks you just deleted from the Registry Editor.
Restart your PC and check if the Task Scheduler is back to its normal state or not.

How to see your Wi-Fi password in Windows 11

Each time you connect to a Wi-Fi network your PC saves that network password. If for any reason you need to see this password or passwords there are ways you can do it and we are here to show you how.

Hello and welcome to error tools where we aim to help you with all of your Windows problems and issues, where we offer our insight on various topics and sometimes go offroad and write something crazy. This time we will offer you a way on how to easily and quickly see how can you find out your memorized Wi-Fi password.

Find your W-Fi password

Make sure that you are connected to the Wi-Fi network you wish to find out the password of
Open Windows Settings app by pressing ⊞ WINDOWS + I
On the left side choose Network & Internet and click on it
Click on Advanced Network Settings
Inside Advanced Network Settings go to Related Settings
Select More Network Adapted Options
Right-click on your adapter and select Status
Click on Wireless Properties
Click on the Security tab
Click on enable on Show Character box beneath Network Security key to reveal Wi-Fi password

Fix volsnap.sys failed BSOD Error in Windows

The Volsnap.sys is a Windows operating system file that is related to the Volume Shadow Copy Service or VSS. It is known to cause a Blue Screen of Death error. The main cause of the Volsnap.sys Blue Screen errors include conflicts with the RAM, issues with the hard disk, incompatible firmware, corrupted drivers, malware infection, and many more. Despite its many possible causes, its fixes are quite straightforward so won’t have any problem following them. The Blue Screen errors that are related to the Volsnap.sys file are:

KMODE EXCEPTION NOT HANDLED
PAGE FAULT IN A NONPAGED AREA
SYSTEM THREAD EXCEPTION NOT HANDLED
IRQL NOT LESS OR EQUAL

You might want to try performing System Restore as it could resolve Blue Screen errors like the ones related to the Volsnap.sys before you proceed with the troubleshooting tips given below. To run System Restore, follow these steps:

Tap the Win + R keys to open the Run dialog box.
After that, type in “sysdm.cpl” in the field and tap Enter.
Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first.

Option 1 – Check if the Volume Shadow Copy service is running and restart it

The first thing you need to do is check if the Volume Shadow Copy service. To do that, refer to the following steps:

Click on Start and type “cmd” and right-click on Command Prompt from the search results.
Then select the “Run as administrator” option to open Command Prompt with admin privileges.
After that, type “net stop sdrsvc” and hit Enter to execute the command in stopping the Volume Shadow Copy service.
Next, type the “net start sdrsvc” command and hit Enter to start the service again.

Note: You can also restart the service using the Windows Services Manager.

In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
From there, look for the Volume Shadow Service (sdrsv) from the list of services. Its Startup type should be set to Manual by default.
Restart the service and if you don’t encounter any error while you turn it on, re-run the backup service and see if the backup process runs successfully.

Option 2 – Try checking the Memory for the Errors using Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the Volsnap.sys Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
After that, it will give two options such as:
- Restart now and check for problems (Recommended)
- Check for problems the next time I start my computer
Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select your preferred option, your computer will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 3 – Try to update or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or rollback the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

Open the Devices Manager from the Win X Menu.
Then go to the section of IDE ATA/ATAPI controllers as well as Storage Controllers and right-click on them to open the Properties.
After that, switch to the Driver tab and click on the Uninstall Device button.
Follow the screen option to completely uninstall it.
Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 4 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the Volsnap.sys Blue Screen error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

Open Command Prompt with admin privileges.
After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

Wait for the process to be completed and then restart your computer.

Option 5 – Run the System File Checker Scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

Tap Win + R to launch Run.
Type in cmd in the field and tap Enter.
After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

Windows Resource Protection did not find any integrity violations.
Windows Resource Protection found corrupt files and successfully repaired them.
Windows Resource Protection found corrupt files but was unable to fix some of them.

Restart your computer.

Option 6 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Volsnap.sys. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

Tap the Win + I keys to open the Settings panel.
Then go to Update & Security > Troubleshoot.
From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

5 ways to open task manager in Windows 11

Something we are used to doing in a certain way inside Windows 10 is slightly changed in Windows 11. One of those things is how you open task manager, well kind of.

Option to right-click on the taskbar and launch task manager is gone but do not worry there are other same and simple ways you can launch it.

Press CTRL + SHIFT + ESC or CTRL + ALT + DEL
Right-click on the START button
Type task manager in start search on top in the start menu
Type taskmgr in command prompt
Press ⊞ WINDOWS + R to open run dialog and type in taskmgr

And that’s it, now depending on your situation, you might use different methods to evoke task manager.

Network License NotAvailable15.570.0 Autodesk

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:

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.

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:

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

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

See System Requirements for the Network License Manager

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.

1 2 3 … 171 Next »