Common Outlook Errors

Most Common Microsoft Outlook errors

When you have a program, you know before you even start to use it or even know how that you are going to have problems with it.

There are always going to be error messages and things that don’t work on any program you buy or download; guaranteed.

Even some of the most famous program developers in the world make mistakes from time to time and it is a small price to pay for the programs you get and that is a fact. Microsoft Outlook is like any other program; it has its errors. Here are some of the most common errors for Microsoft Outlook on your computer.

1. Problem receiving emails

Sometimes you can be waiting on really important emails. It is really infuriating when you know that they have been sent, however every time you check your email box, there is nothing there!

Your inbox is empty and your patience is wearing thin, so could it possibly be an error with Microsoft Outlook? There is a high probability that this is the problem. The program can be a bit slow on receiving emails sometimes, often even by days.

This can be caused by any number of things, from having too many emails coming through or having too many emails in your inbox.

If you click ‘send and receive’ at the top, it should speed up your emails coming through, however, so give that a try if you’re waiting on anything to come through. If this doesn’t work, however, your inbox may be full.

Try permanently deleting some useless messages and then click ‘send and receive’ again. All your emails should come through then!

2. General slow performance

Outlook, while it has its advantages, can often be very slow. It is probably slower than some other email programs that require a browser but it is quicker to access, which may make up for this fact.

However, sometimes sluggish performance can be really irritating, so it may be wise to try and fix it if you can. One of the reasons it may be acting slow is if you have too many other Windows applications open.

Applications that may interfere with your Outlook’s speed could be anything from Microsoft Word to Windows Live Messenger. If any of these are open, try closing them and see if that helps with the speed problem.

3. Corrupt files

.dbx files are not accessible by Microsoft Outlook. Therefore, they can cause problems with your emails if you have them within them.

To solve this problem, you may have to delete all of your attached email accounts and then reattach them before you can open your emails again.

These corrupt files can also cause you to be unable to delete emails. You will need to transfer these deleted corrupt files into a separate deletion folder as this is usually caused by the folder being corrupt.

Of all the other most frequent problems with Microsoft Outlook, however, this is probably the least likely to happen, which shows how few problems there actually are with this application after all that!

Conclusion

So there are the most common problems with Microsoft Outlook! Not much wrong at all, is there?

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

Fix Kernel Power Blue Screen in Windows
To function properly and as intended, Windows 10 depends on a number of resources and software components. Even with a simple task as powering the machine, there are already several smaller software components supporting it. However, if any of these resources or components experience issues, it will affect the overall function of the computer. One of the errors reported is the Kernel Power Blue Screen error which is triggered by the Windows Kernel that mostly comes with a Windows Kernel Event ID 41 error. This kind of error can turn off and reboot the computer randomly. Here’s an example of a Bugcheck code entry with the same event:
 “EventData BugcheckCode 159 BugcheckParameter1 0x3 BugcheckParameter2 0xfffffa80029c5060 BugcheckParameter3 0xfffff8000403d518 BugcheckParameter4 0xfffffa800208c010 SleepInProgress false PowerButtonTimestamp 0Converts to 0x9f (0x3, 0xfffffa80029c5060, 0xfffff8000403d518, 0xfffffa800208c010)”
This kind of BSOD error is caused by an issue with the Power Supply components in both the software and hardware parts of your computer. In such cases, if your computer is stuck in a reboot loop, you need to troubleshoot the problem via Safe Mode or in the Advanced Startup options screen.

Option 1 – Try disabling Overclocking

If you have enabled Overclocking, you might have to disable it as some users reported that the Kernel-Power Blue Screen error started to appear right after overclocking. To disable it, follow the steps below.
  • Go to the Start Menu and open Settings.
  • Next, select Update and Security and go to the Recover tab.
  • From there, click on Restart now in Advanced startup. This will restart your computer.
  • Once you’re in the Advanced startup, go to Troubleshoot and then select Advanced Options.
  • From there, select the UEFU Firmware Settings.
  • Now click on Restart. Once your computer has restarted, it will automatically open BIOS.
  • From the BIOS, go to the Advanced tab and navigate to Performance and then look for Overclocking.
  • Once you’ve found Overclocking, make sure that it is disabled. If it’s not, then disable it and then save the changes made by tapping the F10 key.
  • Start your computer normally and check if the Kernel-Power Blue Screen error is now fixed.

Option 2 – Try to run the Power troubleshooter

The next thing you can do is to run the Power troubleshooter. To do so, follow these steps:
  • Go to Settings and navigate to Update & Security > Troubleshoot.
  • After that, look for the “Power” option from the given list of built-in troubleshooters and click on it.
  • Next, click on the “Run the troubleshooter” button to run the Power troubleshooter.
  • Once the troubleshooter is done identifying the problems, follow the next on-screen instructions to resolve the problem.
Note: You could also try to run the Blue Screen troubleshooter to fix the Kernel-Power BSOD error. You can find it under the same page as the Power troubleshooter.

Option 3 – Try to replace the Power Supply Unit

You could also try to consider physically replacing the Power Supply Unit or PSU of your computer and see if that helps or not.

Option 4 – Run the Windows Memory Diagnostic tool

Since this error could be caused by some issues in the memory, you can try running the Windows Memory Diagnostic tool and see if it helps.
  • Tap the Win + R keys to open Run and type 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 the option, your PC 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 5 – Try to check physically check your RAM

In this option, you have to check your RAM physically especially if you tend to use multiple physical RAMs on your computer so it can be quite tricky and technical. You have to check first if they are of the same frequency and then verify if the chip is compatible or not. You also have to check if the sockets are attached using some adapter or non-recommended apparatus as it can cause some problems while giving performance hit to your computer.

Option 6 – Try to update the BIOS

Updating the BIOS can help you fix the Kernel-Power BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “msinfo32” in the field and press Enter to open System Information.
  • From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
  • After that, you should see the developer and version of the BIOS installed on your PC.
  • Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
  • If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
  • Now double click on the downloaded file and install the new BIOS version on your computer.
  • Now restart your computer to apply the changes made.
Note: If updating the BIOS didn’t help, you might want to consider resetting it instead.

Option 7 – Disable Fast Start-up

If you want your computer to boot faster, then you might have enabled Fast Start-up. This feature is ideal for computers that are using a hard disk drive. However, turning on this feature also means that when the computer boots, it might lag some drivers that are loaded when it initially boots up. Thus, it might be the potential cause of the Kernel-Power BSOD error. Thus, you need to disable Fast Start-up. To do that, follow these steps:
  • Boot your PC into Safe Mode.
  • Then tap the Win + R keys to open the Run dialog box.
  • Next, type in “control” to open Control Panel.
  • After that, select Hardware and Sound and click on Power Options.
  • Select “Choose what the power buttons do” from the left side menu pane and click on Change settings that are currently unavailable.
  • Afterward, uncheck the “Turn on fast startup (Recommended)” entry and click on Save Changes.
  • Now restart your PC for the changes to take effect and then check if the problem’s fixed afterward.
Read More
Intel Arc A770 GPU

intel's first gaming card that will hit the market soon has been shown in its innovation event, the Intel Arc A770. In its core ticks ACM-G10, coming with 32 Xe-cores and all the way up to 16GB of GDDR6 memory (the basic entry-level version will have 8GB of GDDR6). The card will support ray tracing and supersampling with Intel's XeSS.

intel arc a770

This is Intel's first gaming desktop GPU and after testing with some YouTube channels it turned out that the card itself sits somewhere between nVIDIA RTX 3060 Ti and an RTX 3070 so it will still be low in performance compared with the new RTX 4090 or AMD's new RDNA3 upcoming lineup. But as stated this is Intel's first gaming graphics card and having this kind of performance is no small feat for the first-time product.

One thing that is really great tho and that is going for Arc A770 GPU is its price! The Limited Edition card will cost $329 which is at this moment most cheapest GPU currently on the market in that performance range. nVIDIA is between $500 and $700 for comparison and if Intel can hold on to its performance with almost half the price card could be a great hit among gamers. GPU itself will launch on October 12th.

Read More
Repair Windows 10 Error Code 0xC1900208, 0x4000C

Code 0xC1900208 0x4000C, What is it?

The Error Code 0xC1900208 – 0x4000C is an error that is caused by an installed application or program on your computer that is not compatible with Microsoft Windows 10. The incompatible application prevents you from being able to complete the upgrade to Microsoft Windows 10 and will continue to do so until the issue is resolved. Common symptoms include:
  • You receive a dialog box displaying Error Code 0xC1900208 – 0x4000C
  • You are unable to successfully complete the Microsoft Windows 10 upgrade process.

Solution

Restoro box imageError Causes

Error Code 0xC1900208 – 0x4000C is caused by a non-compatible application or program that is currently installed on your computer, and is not allowing the Microsoft Windows 10 upgrade to finish the installation and update process.
  • The upgrade is stopped due to an incompatible app or program.
  • Out of date or no longer supported software can cause this error to occur.
  • Device drivers that are not up to date or no longer compatible.
  • The computer might pick up malware along the way and might be preventing the upgrade. If error code 0xC1900208 – 0x4000C is not rectified, you’ll not be able to proceed with your Windows 10 upgrade.

Further Information and Manual Repair

The good news is, error code 0xC1900208 – 0x4000C is a relatively common problem that is usually easily fixed by the user at home, though it can be a little time-consuming. To elude this time-consuming process, use a powerful tool to rectify the issue in no time (TSC). Before making any attempts to repair this error, ensure to perform a compatibility test.
  • Check the compatibility of applications and programs installed on your computer to locate and remove, or fix the one that is incompatible. (Don't stop at the first one you find, there could be multiple incompatibility issues.)
  • Check to ensure all programs and software are not outdated or no longer supported, and remove or fix any outdated or unused, unnecessary programs or software. (This is also a great way to free up space and clean your computer up a bit.)
  • Check to ensure that all of your device drivers are current, up to date, and compatible with Microsoft Windows 10, and replace or update where necessary.

Method 1:

Use the get Microsoft Windows 10 application on your computer to check its compatibility, follow the steps below to run the check.
  1. Look at the taskbar, to the right; you will see an icon for Microsoft Windows 10, right-click the icon. Locate the option in the menu to check the status of your upgrade. This will open an app for getting Microsoft Windows 10.
  2. Next, you will see 3 lines on top of one another on the upper left side, this will open a drop-down menu, once you have this menu open, locate the option to check the compatibility of your computer.
  3. Microsoft Windows will then run a check of your entire computer to check for compatibility with Microsoft Windows 10. Once it has finished its check, a pop-up window will display whether or not your computer will work with Microsoft Windows 10, and will also display a list of any hardware and software that are not compatible with the upgrade.
  4. This may not catch everything and there may still be incompatible programs so the previous steps, though time-consuming may still be necessary.

Method 2:

Once the incompatible applications are discovered, use the control panel to remove/uninstall them. The steps are below:
  1. Locate your computer’s Control Panel.
  2. Choose the option that says “Programs”
  3. From the options available, select the ‘Programs and Features’ link.
  4. Locate the app in the queue or menu.
  5. Right-click and choose the uninstall option.
… another option
You can also locate the app on the ‘app homepage’, right-click and choose the ‘uninstall’ option. If after following these steps the problem is still not corrected, download and install an automated tool for a quick fix.
Read More
Fix Black border or bar on Monitor
If you suddenly see a black border in your computer’s display then you might be wondering how come this happened but worry not for this post will give you a couple of suggestions that could help you resolve the problem. The black bar could appear at the bottom or just the sides of the screen. Whichever it may be, there are options you can check out. Refer to the options givens below and make sure to follow them carefully.

Option 1 – Try checking the screen resolution

You might want to try checking the resolution of your screen.
  • Open the Windows 10 Settings and go to Display.
  • Next, go for the “100% (Recommended)” option under Scale and layout for the size of the text, apps, and other items.
  • After that, select the Recommended setting again under Resolution.
Now check to see if the black bars are still there. They should be gone at this point, but if for some strange reason nothing has changed, then attempt the steps below.

Option 2 – Try updating Graphics & Monitor drivers

You might want to try updating your graphics and monitor drivers if you haven’t updated them for some time now. To do that, refer to these steps:
  • First, boot your computer into Safe Mode.
  • After that, tap the Win + R keys to launch Run.
  • Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
  • After that, a list of device drivers will be displayed. From there, look for the Graphics drivers or the Monitor drivers and then click each one of them.
  • After that, right-click on each entry and select the “Uninstall Device” option from the menu.
  • Now restart your computer.
  • After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.
Note: You can also try to roll back the graphics and monitor drivers back to their previous versions if updating them didn’t work. You can also try visiting the manufacturer’s website and download the graphics or monitor driver setup for your operating system.

Option 3 – Try to run the DISM tool

You can also run the DISM Tool as it might also help in getting rid of the black border or bar on your Windows 10 computer. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” which could help you resolve the problem.
  • 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 – Troubleshot the problem in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing the Black border issue. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.
  • 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.)
  • From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.
Read More
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:

  1. Download and install the Network License Manager for Windows:
  2. Open LMTools and access the System Settings tab. Make a note of the "hostname" and "ethernet address" of the license server.
  3. Generate a Network License File in Autodesk Account.
  4. On the Service/License tab, select Configuration Using Services and LMTOOLS ignores license file path environment variables.
  5. On the Config Services tab, enter a name for the new service in the Service Name field.
  6. 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.”
  7. Make sure the "Start Server at Power Up" and the "Use Services" boxes are checked. Then click Save Services.
  8. On the Start/Stop/Reread tab, click Start Server.
  9. On the Server Status tab, click Perform Status Enquiry.
  10. 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
  1. 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.
  2. 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.
  3. 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.
  1. Create /usr/local/flexnetserver/licenses directory for network license file location
sudo mkdir /usr/local/flexnetserver/licenses
  1. Find the license server Host Name and Host ID.
  2. 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.
  1. Create a debug.log file in the /usr/local/flexnetserver/ directory using the following command:
touch debug.log
  1. 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
  1. To obtain license server status enquiry:
/usr/local/flexnetserver/lmutil lmstat -a -c /usr/local/flexnetserver/licenses/adsk_license.lic
  1. To stop the license server:
/usr/local/flexnetserver/lmutil lmdown -q -force
  • A​​lternatively, 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:
  1. 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.
  2. 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.
  3. 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"
  1. 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.
  1. To start the Network License Server
    • /opt/flexnetserver/lmgrd -c /opt/flexnetserver/licenses/adsk_license.lic -l /opt/flexnetserver/server_log.log
  2. To obtain license server status enquiry
    • /opt/flexnetserver/lmutil lmstat -a -c /opt/flexnetserver/licenses/adsk_license.lic
  3. 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)
  4. 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
  1. 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.

  1. Type regedit in the Windows Search box and hit Enter key.
  2. Select the following registry key
  • [HKEY_CURRENT_USER\SOFTWARE\FLEXlm License Manager]
  1. As the key is selected, in right panel ADSKFLEX_LICENSE_FILE will be visible.
  2. Right click on the key and delete it.

Specify the license server in ADSKFLEX_LICENSE_FILE system variable 

  1. Go to Start > Control Panel > System and Security > System.
  2. Select Advanced system settings.
  3. On the System Properties dialog, click Environment Variables.
  4. Under System Variables, click New.
  5. 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:

  1. Go to Start > Control Panel > System and Security > System.
  2. Select Advanced system settings.
  3. On the System Properties dialog, click Environment Variables.
  4. Under System Variables, click New.
  5. Enter FLEXLM_TIMEOUT for the variable name and 5000000 for the variable value.
  6. 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:

  1. Open a Terminal window
  2. Type open ~ (Mac) or nautilus ~ (Linux) to open $HOME folder
  3. Drag and drop flexlmrc.txt file from Desktop to the home folder.
  4. 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:
  1. Click the Start menu and type cmd.
  2. Right-click on the Command prompt and choose "Run As Administrator."
  3. 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.
  1. Open Registry Editor (Start > type regedit > ENTER).
  2. Navigate to HKEY_CURRENT_USER\Software\FLEXlm License Manager.
  3. On the right-side, verify of the ADSKFLEX_LICENSE_FILE key exists. If yes, remove it (right-click > Delete).
  4. Run the software again.
  5. Select Multi-user in the Let's Get Started screen.
  6. Follow the steps to connect to your license server.
Read More
What you should not share and post on Facebook
Recent Facebook, Instagram, WhatsApp, Messenger & Oculus fiasco and downtime reminded us that even big IT tech behemoth is vulnerable and can go offline. The situation has been resolve in not so fast manner but not long also, let’s say it was resolved in time that people have not left and switched to another platform. What you should not share and post on FacebookThat being said, now when services are back we stopped and reflected on the platform itself and on its users. If Facebook is vulnerable so are its users, but sometimes users themselves are responsible for being a target. We step back and take a look at posts that manifest on Facebook and have come with some advice on what things you should never post on Facebook and on other social platforms.

Pictures of any kind of ID, bill, vaccine cards or similar document

This should be a no-brainer at all but we see people posting this kind of information. They go on a rant about how the bill is too high and place a picture of it, or they took their vaccine shot and posted a vaccine card as proof. Why this is a bad idea is that any of these documents contain certain things like birthdays, names, and even more like addresses and other information that can be used against users.

Information about where you live

This could be tied to the previous point but it is very crucial that a living address is not something that you wish to share publicly. A lot of burglars are stalking social media for exactly this kind of information so they can then analyze when and how to strike and this time you have done all work for them providing them with the information on where to find your flat.

Daily routines and vacation plans

The most burglary happens to believe it or not during the day, in hours when people are at work. So by providing the world with your daily routines and when you are not at home you are putting your home at risk of being broken into. Posting vacation plans are even worse or posting pictures and status when you are on vacation will send a clear message to anyone that your home is empty and unattended.

Pictures of your home interior

This can also sadly disclosure more information that you wish like maybe some interesting facts like address or birthday on certificates, diplomas, or other documents accidentally caught in the taken picture. Also, these kinds of pictures can show much about your home security, alarm positions if you have some, how is your front door secured, etc.

Content that can get you fired

We hear all the time, famous star or director has some tweets that have resurfaced and now it is fired. I know that many of us are not famous stars but we can also be fired. Sharing some offensive opinions, inappropriate content or just plain pure lies like took sick leave to play this new game can have not so great resolution for your working relationship with your employer. We do not support lies nor do any kind of inappropriate content but posting it online on social media will just make things worse for you personally.

Your login info or sites and services that you are using

It is fairly safe to say hey we are chilling with Netflix or watching the new season of Mandalorian on Disney plus but speaking of things like made a new account on freelancer service of got my new e-banking in this cool new bank, etc. is not very wise. Cyber crooks are always on the lookout for identity theft and will use available information to steal data and money. You are risking also losing provided accounts this way leaving you with tons of work to explain that you got mugged to service providers.

Conclusion

We know that this article seems paranoid and maybe assumes that among your friends there are some crocks and people trying to take advantage of you. As this certainly was not our attention nor goal, we had to point to extremes in order to protect you the most.
Read More
New Chrome update brings surveillance debate
Google Chrome 94 is here and it has introduced a controversial idle detection API. For those people that do not know what idle detection API is, well basically Chrome can be asked by a website to report when a user of the site has a site open and is idle on the device. The issue that people have with this is that this particular feature can be used to report when the user is not using a computer at all. chrome idle detection featureGood thing is that website or web application will prompt you to allow it to use this feature like when a site/application wants to use your microphone or web camera. Developers are on board with this feature since it can provide them with more telemetric data on how users are interacting with their website/application but there are some that are strongly voicing against this. Tantek Çelik, Mozilla Standards Lead, commented on GitHub, saying:
As it is currently specified, I consider the Idle Detection API too tempting of an opportunity for surveillance capitalism motivated websites to invade an aspect of the user’s physical privacy, keep long-term records of physical user behaviors, discerning daily rhythms (e.g. lunchtime), and using that for proactive psychological manipulation (e.g. hunger, emotion, choice)… Thus I propose labeling this API harmful and encourage further incubation, perhaps reconsidering simpler, less-invasive alternative approaches to solve the motivating use-cases.
Others who have spoken against this feature are people from the WebKit development team inside Apple. Ryosuke Niwa, an Apple software engineer who works on WebKit said:
That doesn’t seem like a strong enough use case for this API. For starters, there is no guarantee that the user won’t immediately come back to the device. Also, who is such a service supposed to know what another device user might be using at any given point? We’re definitely not going to let a website know all the devices a given user might be using at any given point. That’s a very serious breach of the said user’s privacy. It seems to me that such a suppression/distribution mechanism is best left for the underlying operating systems/web browsers to handle.
Of course, technology itself as always can be used for good or for bad and time will tell if this feature has brought good stuff or it has paved another brick in surveillance and privacy manipulation. As said for now option will prompt for agreement and let's hope that it will be used for good causes from this day into the future.
Read More
Fix Folder Redirection Failed in Windows
If you got an error message saying, “Folder Redirection Failed, Failed to build the list of regular subfolders, Access is Denied” after you configured a new Group Policy Object or GPO which redirects User folders to a new network share or when you click on Reset default location under the Windows File Explorer or Folder Options, then you’ve come to the right place as this post will show you how to resolve this kind of error on your Windows 10 computer. Follow the given options below carefully to fix the “Folder Redirection Failed” error.

Option 1 – Take Ownership of the folder

If you are not able to access the folder could be one of the reasons why you’re getting the “Folder Redirection Failed” error and so you need to take ownership of the folder to resolve the problem. Before you proceed, make sure that your account is an admin account.
  • First, locate the concerned folder and right-click on it then select Properties.
  • Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
  • After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
  • Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
  • Now edit the permission to Full Control for “Everyone”.
  • Click OK to save the changes made and then exit.

Option 2 – Try to add Authenticated Users or Domain Computers

Make sure that the Folder Redirection group policy removal option is set to “Redirect the folder back to the user profile location when the policy is removed” when using the Folder Redirection. After that, you have to add Authenticated Users group with the “Read” permissions on the Group Policy Objects or GPOs. And if the Domain computers are part of the group of “Authenticated Users”. Note that by default, the “Authenticated Users” have these permissions on any new Group Policy Objects or GPOs. Once again, you have to add just “Read” permissions and not “Apply Group Policy” for “Authenticated Users”. Furthermore, to fix the “Failed to build the list of regular subfolders” errors, here are some options that could help.

Option a – Try to clear disk space

You might have to check if your disk is running out of space because if it is, then it will fail to create a list abruptly. And so you need to free up some disk space. You can either check on the files manually especially if you tend to keep your files at random places in your disk drive.

Option b – Find the Target route

You need to find the target route of the folder and then restore it if you are getting the “Failed to build the list of regular subdirectories” when you try to relocate the folder to the original location.

Option c – Try to change Ownership/Reset Defaults for all the User folders

If the “Failed to build the list of regular subdirectories” error pops up when you are trying to move a large number of files from one location to another, then you need to change the ownership of the folders as pointed out earlier.
Read More
Attempt was made to reference a token
If you were trying to open File Explorer but it suddenly stopped working and you encounter an error message that states, “An attempt was made to reference a token that does not exist”, read on as this post will guide you in fixing this problem. This problem was initially reported after the April Update and Microsoft was able to fix it right after correcting the build. However, this effort seems futile for some users as recently, some reported getting the same error when they try to open not just Windows File Explorer but also with utilities like Microsoft Management Console or MMC, Visual Studio, Task Manager, Printer, Recycle Bin, etc. Two of the most likely causes of this error are a troublesome Windows Update and corrupted system files. Whatever the cause is, here are some suggestions you can follow to fix the “An attempt was made to reference a token that does not exist” error.

Option 1 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.
  • Open Command Prompt as admin from the WinX menu.
  • Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
    • exe /[DLL file]
    • exe [DLL file]
Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.
  • After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 2 – Replace the DLL file from a trusted source

  • First, you need to get the new DLL file from another computer with preferably the same file version number.
  • After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
    • x86: This PC > C:/Windows/System32
    • x64: This PC > C:/Windows/SysWOW64
  • Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
  • Now type the “regsvr32 ntdll.dll” command and hit Enter.
  • Restart your PC and check if the error is now fixed.

Option 3 – Perform a System File Checker scan

The System File Checker or SFC scan could detect and automatically repair damaged system files that could be causing the “An attempt was made to reference a token that does not exist” error to pop up. 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 and hit Enter.
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:
  1. Windows Resource Protection did not find any integrity violations.
  2. Windows Resource Protection found corrupt files and successfully repaired them.
  3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 4 – Try reverting back to the previous build of Windows

This kind of error might have something to do with a Feature Update so you can try to revert your computer to a previous build of Windows 10 as it could help you fix the problem. In this case, it would better if you refrain from updating your Windows 10 computer until this problem is completely resolved by Microsoft.
Read More
Fix GDI32.DLL error in Windows 10
The GDI32.DLL is a DLL (Dynamic Link Library) file that was developed by Microsoft. It is an essential file of the Windows OS as it contains instructions and information for exe files to follow. These DLL files also use to store the various procedures and codes for the Windows programs. It is considered an essential component of Windows because it ensures that all the programs on Windows are operating properly. So, if the gdi32.dll not found on your computer, then it can negatively impact your computer and the associated programs. Though DLL files used to be so efficient and convenient, they are extremely vulnerable to errors and issues.
  1. Perform SFC scan

    Press ⊞ WINDOWS + X to open the Windows menu keyboard with windows and x marked From the menu choose command prompt (admin) Windows menu command prompt adminIn command prompt type sfc /scannow and press ENTER Leave the computer for the operation to be completed and Reboot your computer
  2. Run DISM

    Press ⊞ WINDOWS + X to open the Windows menu keyboard with windows and x markedFrom the menu choose command prompt (admin) Windows menu command prompt adminin command prompt type: DISM.exe /Online /Cleanup-image /Restorehealth and press ENTER wait for the process to be finished and Reboot your computer
  3. Update device driver

    Go to your manufacturer's website and update drivers for your components with the latest versions.
  4. Update Windows

    If you have an update ready for Windows, update it and see if this will remove the error
  5. Scan computer for malware

    Perform a full PC scan for malware to see if this is causing issues with the GDI32.DLL error.
  6. Download file

    One solution is to download a file from the official site and place it in the corresponding folder.
  7. Perform System restore

    Rollback system restore before the issue happened and your Windows will be working as intended
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status