FanFiAddict

A gaggle of nerds talking about Fantasy, Science Fiction, and everything in-between. They also occasionally write reviews about said books. 2x Stabby Award-Nominated and home to the Stabby Award-Winning TBRCon.

In CSI SAP2000, Error 18 typically indicates that the software cannot find a valid encrypted license file or that the existing license file is corrupted. This often happens due to registry corruption during installation, changes in system hardware IDs, or outdated license management tools. Common Causes of Error 18

Corrupted License File: The lservrc file (or similar license markers) may be damaged or missing from the installation directory.

Registry Issues: Conflicts in the Windows Registry can prevent the software from properly communicating with the Sentinel RMS License Manager.

Hardware Changes: Because licenses are often locked to specific hardware (like Ethernet Address or CPU ID), updating drivers or changing hardware can invalidate the existing license.

Version Mismatch: Using an older Sentinel RMS License Manager that does not recognize newer v18 licenses. Step-by-Step Solutions 1. Regenerate and Replace the License File

If the license is corrupted, you may need to manually place a fresh license file in the correct folders. Locate your license file (typically named lservrc).

Copy and paste it into the SAP2000 installation folder (e.g., C:\Program Files\Computers and Structures\SAP2000 18).

Also place a copy in the CSI Licensing subfolder within that directory. 2. Refresh the Native Image

The "CSI Native Image Gen" tool can sometimes resolve registration errors between the software and the OS. Navigate to the SAP2000 installation directory.

Right-click CSI.NativeImageGen.exe and select Run as Administrator.

Press F4 on your keyboard to uninstall existing images (you may need to hold the Fn key on laptops). Follow the prompts to refresh the installation. 3. Update the License Manager (Network Licenses Only)

If you are using a network license, ensure your server is running Sentinel RMS License Manager v8.6 or newer. Older versions like v7.x or v8.x may not recognize SAP2000 v18 licenses. Download the latest manager from the CSI Knowledge Base.

Follow the official Sentinel RMS Installation Guide to upgrade without losing your current license configurations. 4. Check User Account Control (UAC) Settings

Windows UAC can block SAP2000 from accessing the registry keys required to "recognize" the license. Ensure you are logged in as an Administrator.

Try running SAP2000 by right-clicking the shortcut and selecting Run as Administrator.

If the error persists, consider temporarily lowering UAC settings during a re-installation to ensure all registry entries are written correctly. 5. Repair via Microsoft FixIt or Reinstallation

If registry corruption is suspected, use the Microsoft Program Install and Uninstall troubleshooter (formerly FixIt) to clean up residual files. Uninstall SAP2000. Reboot your machine.

Run the Microsoft Troubleshooter to clear corrupted registry keys. Re-install SAP2000 using the official installer. Verification Checklist Network licensing errors during software startup - Autodesk

SAP2000 "License Not Recognized" Error #18 (SentinelLM Error #18) typically indicates that the software can see a license, but it is not valid for your specific setup or product version The "Proper Story" (What’s Really Happening)

This error is usually caused by one of three common scenarios: Network vs. Standalone Conflict : During installation, if you select "Use Network License"

but you are actually using a standalone key (or vice versa), SAP2000 will check for a license server that doesn't exist or isn't configured, throwing Error 18. Date/Time Mismatch : The license file (

) is extremely sensitive to your system clock. If your computer's date or time is incorrect, the Sentinel system will flag the license as invalid. Lock Code Mismatch

: If you recently changed hardware (like a new motherboard or network card), your machine's unique Locking Code

has changed. Since the license file is "locked" to your old hardware ID, it is no longer recognized as valid for the current machine. BricsCAD Help Center How to Fix It Check Installation Type : Re-run the installer or setup and ensure you select "Standalone License"

if you have a local key. If you are on a network, ensure the LSFORCEHOST environment variable is correctly set to your server's IP. Sync Your Clock

: Verify your system date, time, and time zone are accurate. Even being off by a few minutes can sometimes trigger Sentinel errors. Verify the Locking Code echoid.exe wechoid.exe utility in the SAP2000 installation folder. Run it to see your current machine's locking code.

Compare this to the code listed in your license request. If they don't match, you must request a new license file from CSI Support Update Sentinel Driver

: Ensure you have the latest Sentinel System Driver installed. You can often find this on the official Safenet/Thales website

Are you using a standalone USB dongle or a cloud-based network license?

Knowing this will help narrow down which configuration file needs editing.

SAP2000 License Not Recognized Error 18 is a common licensing issue associated with the Sentinel RMS (formerly SentinelLM) system used by Computers and Structures, Inc. (CSI).

It typically indicates that the software cannot find a valid license to run, often due to a mismatch between the license type (Standalone vs. Network) or configuration issues between the client and the license server Freshworks Primary Causes of Error 18 Incorrect License Type Selection

: Selecting "Network License" during installation when only a "Standalone" license is available (or vice versa). Missing or Invalid License File

file, which contains the authorization code, is either missing from the installation folder or is corrupted. Connectivity Issues (Network Licenses)

: The client machine cannot locate the license server on the network. HostID Mismatch

: The HostID (locking code) of the machine has changed or does not match the one bound to the license file. Outdated License Manager

: Using an older version of the Sentinel RMS License Manager that does not support the version of SAP2000 installed. BricsCAD Help Center Troubleshooting and Solutions 1. Verify Installation Settings

If the error appeared immediately after a fresh installation, it is likely due to the license type selected during the setup process. : Reinstall the software and ensure you select Standard/Standalone License if you are not using a server-based network license. Verification : Check if the software was installed on the

, as some users report errors when installing on secondary partitions. 2. Configure Network Connectivity (For Network Licenses)

If your organization uses a network license, the client machine must be able to "find" the server. I recieve the following error SentinelLM: Error[18]

To resolve the SAP2000 License Not Recognized Error 18, typically associated with the SentinelLM or Sentinel RMS License Manager, follow these troubleshooting steps. This error generally indicates that the software cannot find a valid license for the specific version or feature you are trying to run. Common Fixes for Error 18

Verify Version Compatibility: Ensure the license on your server matches the version of SAP2000 installed. Note that older license managers (e.g., version 7.x.x) may not recognize licenses meant for newer versions like Sentinel RMS 8.6.

Run as Administrator: Right-click the SAP2000 executable or the licensing tool and select "Run as Administrator" to ensure it has proper permissions to read registry entries.

Clear Corrupted Registry Entries: This error can be caused by corrupted registry data during installation. Use a trusted registry cleaner or the Microsoft Program Install and Uninstall Troubleshooter (formerly FixIt tool) to repair installation issues.

Network License Connection (LMHOST.INI): If you use a network license, create a file named LMHOST.INI in the SAP2000 installation folder. Open Notepad, type the IP address or server name of the license server, and save it as "All Files" to ensure it has no hidden .txt extension.

Restart the License Manager: On the server machine, restart the Sentinel RMS License Manager service to refresh the license pool.

Reinstall on C Drive: Some users report that installing the software directly on the C: drive (default path) resolves path-related recognition errors on newer systems like Windows 11.

Step-by-Step Troubleshooting Guide

Follow these steps in order. Do not skip the diagnosis section.

4. Resolution Procedures

Solution A: The USB Selective Suspend

Windows, by default, turns off USB ports to save power. This kills the dongle.

  1. Control Panel → Power Options → Change plan settings → Change advanced power settings.
  2. Scroll to USB settings → USB selective suspend setting.
  3. Set to Disabled.
  4. Apply → Reboot.

When to Contact CSI Technical Support

You have exhausted all fixes. Error 18 persists. Before calling, gather these three things:

  1. The Diagnostic Log: Run haspdinst.exe -info > hasp_log.txt
  2. Your License Number: (Found on the dongle sticker or original email).
  3. Windows Event Log: Search Event Viewer → Windows Logs → Application → Look for "Sentinel" or "Error 18."

CSI support will likely issue a license file replacement or an RMA for a faulty dongle if they detect hardware failure.

5. Fix for Network License

Error 18 with network license means SAP2000 cannot contact the license server.

2. Corrupted Sentinel HASP Driver

The HASPUserSetup.exe driver allows Windows to talk to the USB license dongle (or software license). If this driver is old, partially uninstalled, or corrupted by a failed update, the license pool becomes invisible to SAP2000.