License Error 120 typically indicates that the license file is incomplete or corrupted
. This error usually pops up when the software's Sentinel RMS License Manager cannot fully read the required authorization data. CSI Knowledge Base Common Fixes for Error 120
Depending on whether you use a standalone or network license, try the following steps: Deactivate and Reactivate
: For standalone licenses, the official recommendation is to deactivate the license and then perform a fresh reactivation to rebuild the license file. Verify System Date/Format
: Ensure your computer's date and time are correct. In some cases, setting the regional format to English (United States)
(mm/dd/yyyy) helps the license manager recognize valid keys. Run as Administrator : Right-click the ETABS shortcut and select "Run as Administrator"
to ensure the software has the necessary permissions to access the licensing directory. Check Sentinel Drivers : If you use a USB dongle, ensure the Sentinel System Driver
is properly installed and the computer recognizes the Computer ID (CID). You can verify this by running WechoID.exe from the ETABS installation folder. Re-link the License File : Ensure the license file (typically named etabs license not recognized error 120 work
) is present in both the main installation directory and the CSi\Licensing subfolder. CSI Knowledge Base Advanced Troubleshooting
If the basic fixes don't work, consider these deeper system checks: Clean Registry
: Registry corruption during installation can cause license recognition failures. You can try a new installation after a complete reboot to clear temporary conflicts. FixSerCom Utility : If you are on a network, an administrator can run the lsclean -fixsercom
command from the Sentinel RMS Utilities folder to reset the license communication. CSI Knowledge Base Further Exploration View the official CSI Knowledge Base for a full table of error codes and specific resolutions. Follow this installation and licensing guide for manual file placement instructions. Check this troubleshooting guide for issues specifically related to Standalone CID keys. Are you using a standalone license with a USB key, or is your license hosted on a company server Licensing errors generated when running CSI software 7 Jul 2025 —
Table_title: Licensing errors generated when running CSI software Table_content: header: | Error Code | Problem Description | row: CSI Knowledge Base Licensing errors generated when running CSI software
ETABS "License Not Recognized" Error #120 typically indicates that the license file is incomplete or cannot be verified by the Sentinel RMS License Manager CSI Knowledge Base Immediate Solutions for Standalone Licenses
If you are using a standalone license, the most common fix is to refresh the activation status: Deactivate and Reactivate StandAloneKey.exe tool (found in the CSiLicensing License Error 120 typically indicates that the license
subfolder of your ETABS installation directory) to deactivate your license and then reactivate it. Verify System Date
: Ensure your computer's date and time are correct, as an incorrect system clock can cause the license manager to reject a valid file. Check the License File : Ensure the
license file is present in the main program installation directory. CSI Knowledge Base Troubleshooting for Network Licenses
If your error occurs on a network setup, the issue often lies with the server connection or version compatibility: Upgrade License Manager : ETABS v17 and later require Sentinel RMS License Manager v9.2
or higher. Older versions (v8.5 or earlier) will not recognize newer licenses. Check Server Connectivity
: Ensure the client machine can "ping" the license server and that the server name is correctly set in your environment variables or configuration files. Restart Services
: On the server, ensure the "Sentinel RMS License Manager" service is running. Restarting this service can often resolve temporary communication blocks. Firewall/Antivirus Uninstall ETABS and CSI License Manager Restart PC
: Verify that your firewall is not blocking communication to the license manager on the server. CSI Knowledge Base Advanced Technical Steps Verify Locking Codes WechoID.exe
(found in the installation folder) to confirm that the "Computer ID" or "Ethernet Address" matches the details provided when the license was generated. Examine Logs : Check the CSI_SentinelLM.log
file in the application data directory for specific error details that can be sent to CSI Support to verify your Computer ID? Licensing errors generated when running CSI software
License file incomplete. For standalone licenses, deactivate license and then reactivate the license. CSI Knowledge Base Licensing errors generated when running CSI software
ETABS License Not Recognized (Error #120) typically stems from incomplete, corrupted, or expired license files, often requiring deactivation and reactivation of the software. Key troubleshooting steps include verifying the lservrc file, adjusting system regional settings, or configuring LMHOST.INI for network licenses. Detailed troubleshooting steps can be found at CSI Knowledge Base. Licensing errors generated when running CSI software
Newer ETABS versions often use digital licenses tied to a machine ID.
Follow these steps in order to diagnose and resolve the issue.
CSI_license.dat)License files are plain text files containing encryption keys, hostnames, and port designations. These files can become corrupted due to: