Sap2000 License Not Recognized Error 18 Fixed May 2026

In SAP2000, (SentinelLM/Sentinel RMS Error #18) typically indicates that the software cannot find a valid license code for the requested feature

. This commonly occurs because the license file is missing, the wrong license type was selected during installation, or there is a version mismatch with the License Manager. Freshworks Common Fixes for Error 18 Verify Installation Type

: During installation, ensure you select the correct license type (Standard/Standalone vs. Network). Choosing "Network" when you only have a standalone license often triggers this error. Upgrade Sentinel RMS License Manager : Modern versions of SAP2000 (v18 and later) require Sentinel RMS License Manager v8.6 or newer

. Older versions of the manager will not recognize newer licenses. You can find the latest tools on the CSI Knowledge Base Check PC Date/Number Format : Ensure your system's date and number format is set to English (United States)

(mm/dd/yyyy). Incorrect regional settings can prevent the licensing tool from validating the key. Create or Update LMHOST.INI

: For network licenses, if the client cannot find the server, manually create a file named LMHOST.INI

in the SAP2000 installation folder. Inside the file, type the IP address of your license server. Check for License File : Verify that the

file exists in the SAP2000 installation directory. If it is missing or empty, you may need to reactivate the software using the CSiLicensing tool found in the program's subfolder. Run as Administrator

: Right-click the SAP2000 executable or the activation tool and select "Run as administrator" sap2000 license not recognized error 18 fixed

to ensure it has the necessary permissions to read license files. CSI Knowledge Base a standalone license or setting up a network license server AI responses may include mistakes. Learn more I recieve the following error SentinelLM: Error[18]

Troubleshooting and Fixing SAP2000 License Not Recognized (Error 18)

Engineers relying on SAP2000 for structural analysis often encounter the "License Not Recognized" prompt, accompanied by Error 18. This specific code typically stems from a communication breakdown between the software and the Sentinel RMS License Manager or issues with the license file itself.

Below is a comprehensive guide to resolving this error and getting your software back online. 1. Verify the License Server Connection

Error 18 frequently indicates that the client machine cannot find the license on the network server.

Check the LMHOST.INI File: Create a file named LMHOST.INI in the SAP2000 installation folder (e.g., C:\Program Files\Computers and Structures\SAP2000). Inside this file, type the IP address or Host Name of the server machine.

Use LSHOST: Alternatively, creating a file named LSHOST (no extension) with just the server's IP address can help the software point directly to the license source.

Network Stability: Ensure you are on the same network as the server. If working remotely, verify your VPN connection is active. 2. Update and Restart the Sentinel RMS License Manager Why Does Error 18 Happen

If you have administrative access to the license server, the error may be caused by an outdated manager or a hung process.

Restart the Service: Go to Windows Services, locate the Sentinel RMS License Manager, and restart it.

Version Compatibility: Ensure you are running a compatible version of the license manager. For example, SAP2000 v18 and newer often require Sentinel RMS License Manager v8.6 or higher to recognize modern licenses.

Reread License File: If using a web-based administration tool, perform a "Reread/Restart" after updating the lservrc file. 3. Repair Corrupted Registry Entries

Sometimes the "License Not Recognized" error is a symptom of a botched installation or corrupted Windows Registry keys.

Why Does Error 18 Happen? (Root Causes)

Error 18 is rarely caused by a "bad" license. Instead, it is typically triggered by one of the following:

1. Windows Firewall or Antivirus Blocking: Your security software has quarantined or blocked the license manager service.
2. Windows Updates: A recent Windows Update (especially KB500xxxx series) has reset your network settings or firewall rules.
3. Corrupted License Service Installation: The Sentinel RMS License Manager service is installed but fails to start.
4. Hosts File Issue: Your hosts file has an incorrect entry pointing to an old license server.
5. Network Profile Change: You switched from a "Private" to a "Public" network, which blocks inbound license requests.
6. Hardware ID Change: Replacing a network card, motherboard, or switching from Ethernet to Wi-Fi changes your Machine ID.

Fix 4: Contact CSI Support

• If none of the above solutions work, reaching out to CSI's technical support team can provide personalized assistance. They can offer specific guidance based on your system configuration and the exact nature of the error.

What Does Error 18 Actually Mean?

In plain English, SAP2000 found the license file, but it doesn't trust it or can't read it. Common causes include:

• Corrupted local license files.
• A Windows update that overwrote a driver (common for USB dongles).
• Antivirus software quarantining a critical file.
• A mismatch between the installed version of SAP2000 and the license manager version.

6. Firewall and Antivirus Exclusions

Sentinel RMS uses TCP port 1947 (default) for network communication. proceed to Fix #2.

Actions:

• Add inbound/outbound rules allowing lmgrd.exe and hasplms.exe (if present).
• Exclude the entire C:\ProgramData\Computers and Structures\ folder from real-time antivirus scanning.

Fix #1: The "Physical" Check (Hardware Dongle Only)

If you use a USB hardware key (dongle):

1. Unplug and Re-plug: Remove the USB dongle, wait 10 seconds, and insert it into a different USB port. Ideally, use a USB 2.0 port (black plastic tab) rather than USB 3.0 (blue tab), as older dongles have compatibility issues.
2. Check the LED: Most SAP2000 dongles have a small LED light. If the light is off, the dongle is not receiving power. Try a powered USB hub or another computer.
3. Clean the Contacts: Gently clean the metal contacts of the dongle with a dry cloth.

Result: If the LED lights up and the error persists, proceed to Fix #2.

2. Verify License File Location

Standalone (local) license:

• Place sap2000.lic in:

  C:\ProgramData\Computers and Structures\Licenses\
  

  (Create the Licenses folder if missing.)
• Do not place it inside Program Files – UAC may block access.

Network license:

• Point SAP2000 to the server via License Preferences (Start Menu → CSi License Manager → Specify license server as port@hostname).

The 5-Step Fix (From Quickest to Most Thorough)

Start with #1. Do not skip to #5.

Preventing Error 18 in the Future

Once you have fixed the error, follow these best practices to never see it again:

• 📌 Exclude SAP2000 from Antivirus Scans: Add the entire C:\Program Files\Computers and Structures\ folder to your antivirus exclusion list.
• 📌 Set Windows Updates to Manual: Large updates can reset network profiles. Install updates during downtime, not before a deadline.
• 📌 Use a Static IP (for Network Licenses): If your PC gets a new DHCP IP address, the license server may lose connection. Assign a static IP.
• 📌 Regularly Restart the Sentinel Service: Create a simple batch file to restart the license manager on boot.