If you see this error immediately after a new installation, it often means you accidentally selected "Network License" when you should have chosen "Standalone License" (or vice versa).
Fix: Reinstall ETABS and ensure you check the box for "Use Standard License" instead of "Use Network License". 2. Check the System Date
Error #18 (and related Error #20) can occur if the computer’s date is incorrect or if the license was issued for a specific timeframe that the system clock is no longer matching.
Fix: Confirm your system date and time are accurate. If you are using a standalone key, some users find success by setting the date format to US (mm/dd/yyyy). 3. Update Registration Tools
For older versions like v18, corrupt registry entries can trigger licensing failures.
Fix: Run the software with Administrative Privileges. If that fails, locate the CSiLicensing subfolder in your ETABS installation directory and run the standalonekey.exe or activation tool again to refresh the license link. 4. Verify License Expiration
If you are on a network, the license on the server might have simply expired.
Fix: Use the WlmAdmin.exe utility (typically found in C:\Program Files (x86)\Computers and Structures\Sentinel RMS...) to check the expiration date of the license. If it is past its date, you must contact your administrator to renew it. 5. Add an LMHOST.INI File
If you are using a network license and the software can't "see" the server:
Fix: Create a plain text file named LMHOST.INI in the ETABS installation folder. Inside, type the IP address or name of the license server. This helps the software bypass network discovery issues. ✅ Summary
The error occurs because the program cannot find a valid authorization. Most users resolve this by reinstalling and selecting the "Standalone/Standard" license option or ensuring their system clock is correctly synchronized. To help you more specifically, could you tell me: Are you using a Standalone (USB/Web) or Network license?
Did this error start suddenly, or right after a new installation? Etabs 2019 Error #18 - CivilEA.com
ETABS License Error 18 (also identified as "License Not Recognized" or "Error #18") typically indicates that the software cannot find or communicate with a valid license file on the server or local machine. Common Causes
Expired License File: The current license (often named lservrc) has reached its end date and is no longer valid for the installed version.
Connection Issues: The client machine cannot reach the license server due to network settings, firewalls, or incorrect IP/hostname configuration.
Locking Code Mismatch: The license file was generated for a different machine ID (Ethernet address, UUID, or Host ID) than the one currently running the software.
Revoked License: If a license was recently revoked or deactivated, it may still trigger this error until the system is fully updated or restarted. Detailed Troubleshooting Steps etabs license error 18 2021
Verify System Date: Ensure your computer's date and time are accurate. A discrepancy between the system clock and the license's valid period will cause an immediate failure. Check License Path and Settings:
Navigate to Start > All Apps > Tekla > System and User settings (or the equivalent CSI Licensing Configuration tool).
Confirm the License Method is set to "Server" and verify the server name or IP address is correct. Validate the Locking Code:
Run wechoid.exe (found in the CSiLicensing folder within the ETABS installation directory).
Compare the machine's current locking code to the one provided in your official license documentation. If they don't match, you must request a new license key from CSI Support. Manage License Files:
Locate the lservrc file in the ETABS installation folder. If it is missing or corrupted, the software will not launch.
For standalone licenses, try deactivating and then reactivating the license through the CSiLicensing tool. Server Maintenance:
If using a network license, restart the Sentinel RMS License Manager service on the host server.
Ensure that the TCP port used by the license manager (typically 5093 or 5099) is not being blocked by a firewall. Licensing errors generated when running CSI software
: A common trigger for error 18 is the local PC's date and number formatting. To resolve this, change your Windows system settings to English (United States) with the format mm/dd/yyyy Incorrect License Type
: If you chose the "Network License" option during installation but only have a standalone license, error 18 may appear. : Re-run the installation and ensure you select "Use Standard/Standalone License" System Date Mismatch
: Licensing errors can also occur if your system clock is significantly off. Ensure your PC's current date and time are accurate before attempting to activate or run the software. Corrupted License File : If the local license file (
) is corrupted or incomplete, you may need to deactivate and reactivate your license via the CSiLicensing tool Troubleshooting Steps Check Date Settings Control Panel > Clock and Region > Region and set the format to English (United States) Verify License Mode : If you are using a network license, ensure the LMHOST.INI
file contains the correct server IP address and is placed in the ETABS installation directory (e.g., C:\Program Files\Computers and Structures\ETABS 2021 Run as Administrator : Right-click the ETABS shortcut and select "Run as administrator"
to ensure the software has the necessary permissions to read the license file. Reset Toolbars : In some cases, deleting files in the C:\Windows folder and selecting Options > Reset Toolbars within ETABS can clear related internal errors.
For persistent issues, you can generate a locking code using Wechoid.exe (found in the installation's CSiLicensing folder) and contact CSI Technical Support for a manual license refresh. CSiLicensing tool path on your machine or instructions for deactivating a current license? Licensing errors generated when running CSI software If you see this error immediately after a
License Error 18 typically indicates that the software cannot find a valid license to run
. This often occurs because the program is incorrectly searching for a network license instead of a standalone one, or because the license file is missing from the server. Common Fixes for Error 18 Switch License Type : During installation, ensure you select "Use Standard License"
rather than "Use Network License" if you are using a standalone activation key. Check Date and Time
: SentinelLM licensing can fail if your system's date, time, or number format is incorrect. Try changing your PC's regional format to US (mm/dd/yyyy) Standalone License Activation
: If using a standalone license, ensure you have activated it using the StandaloneKey.exe utility found in the CSiLicensing subfolder of your installation directory. Network License Configuration : For network users, ensure the LMHOST.INI
file contains the correct IP address of the license server and is placed in the ETABS installation folder. Restart and Relaunch
: Sometimes the error is a temporary glitch. Force-quit ETABS via the Task Manager and relaunch it. CSI Knowledge Base Advanced Troubleshooting If the basic fixes don't work, refer to the CSI Knowledge Base on Licensing Errors for detailed resolution steps. You may need to: CSI Knowledge Base Deactivate and Reactivate
: For standalone licenses, deactivating and then reactivating the license can fix corrupted license files. Check Port Access : Ensure ports 80 and 443
are open, as they are required for license activation and communication with the server. CSI Knowledge Base Are you using a standalone license server for your 2021 version? Licensing errors generated when running CSI software
License Error #18 in ETABS 2021 typically occurs when the software is unable to find a valid license, often due to configuration conflicts between network and standalone settings or issues with the Sentinel RMS license manager. Common Causes
Incorrect License Type Selection: Choosing "Use Network License" during installation when you actually have a standalone license (or vice versa) frequently triggers this error.
Corrupted Registry Entries: Installation errors or residual data from previous versions can corrupt the license registry paths.
Missing License Files: The lservrc file, which contains the actual license data, may be missing from the ETABS installation or CSiLicensing folder.
Native Image Conflicts: Issues with the .NET native image can sometimes interfere with the licensing handshake. Recommended Troubleshooting Steps
Verify Installation TypeIf you are seeing Error 18, check if you accidentally selected "Network License" during setup. If you are using a standalone key, you may need to reinstall and ensure "Standard/Standalone License" is selected instead.
Environment Variable Check (Network Users)For network licenses, ensure your PC knows where to look for the server: Open Environment Variables in Windows. Create a new System Variable named LSFORCEHOST or LSHOST. Set the value to your server's IP Address or PC Name. License file deleted or renamed accidentally
Manual License PlacementEnsure the lservrc file is present. If you have a valid license file:
Copy it into the main ETABS installation directory (e.g., C:\Program Files\Computers and Structures\ETABS 2021). Also, place a copy in the CSiLicensing subfolder.
Reset Licensing ServiceIf the error persists, you can try to "clean" the licensing state:
Uninstall Native Image: Run a Command Prompt as administrator and execute ngen uninstall ETABS to remove potentially corrupt .NET native images.
Run as Admin: Always ensure you are launching ETABS and the activation tools with Administrative Rights.
Check Sentinel RMS UtilitiesUse the WlmAdmin.exe utility (found in the Sentinel RMS folder) to verify if the license is recognized and hasn't expired. If the expiration date has passed, you must renew the license through the CSI Customer Portal.
For official support, you can refer to the CSI Knowledge Base or contact their licensing department with your Locking Code generated by the WechoID.exe tool. Error codes and descriptions - CSI Knowledge Base
License Error 18 in ETABS (or any CSI software like SAP2000 and SAFE) typically means "The server is down or not responding."
Essentially, your computer knows where the license should be (the Server Name/IP is correct), but it cannot communicate with the server computer to actually borrow the license.
Here is a step-by-step guide to troubleshooting and fixing this error for the 2021 version.
Error 18 means the license file (e.g., lservrc or etabs.lic) is missing, cannot be read, or is not in the expected location. Typical causes:
Since you are dealing with a 2021 version (which is no longer the latest), prevention is key:
C:\Program Files\Computers and Structures\C:\ProgramData\SafeNet\C:\Windows\System32\Lserv.exeCSI_LICENSE_FILE variable and server version.CSiLicensingTool.exe (in the installation folder). Run this as Administrator → Diagnose → It will directly tell you if Error 18 is due to a daemon mismatch.LicenseStatus.log (found in %temp% folder) and a screenshot of your lmgrd version.This is the most effective solution for Error 18 in the 2021 version. Trusted Storage is a hidden folder where Windows stores licensing activation data. Corruption here is rampant after Windows updates.
Step-by-step (Admin rights required):
net stop "Sentinel RMS License Manager" and press Enter.cd C:\ProgramData\SafeNet Sentinel\Sentinel RMS Development Kit\System\
del *.* /Q
net start "Sentinel RMS License Manager"
After reboot, launch ETABS 2021. It will rebuild the Trusted Storage automatically, and Error 18 should vanish.
Licenses folder → Properties → Security.