Aspen Hysys License Checkout Failed
What you see: “User 'jsmith' is not included in the license file.”
Cause: The license server has an INCLUDE list (security). You aren't on it.
Fix: Your IT admin must edit the license file:
INCLUDE HYSYS_Process USER jsmith
Then reread the license file using lmreread.
Did you upgrade from HYSYS V11 to V12.1? The old license file may not support the new features.
The "Aspen HYSYS License Checkout Failed" error is rarely a death sentence; it is almost always a solvable logical break in a chain—a closed port, a stale token, a missing environment variable, or a busy server.
By following the steps in this guide—starting with the simple (restart service, reboot) and moving to the advanced (telnet tests, trust cache deletion, lmstat diagnostics)—you can diagnose the exact failure point within 15 minutes. Aspen Hysys License Checkout Failed
Final Checklist for Success:
When the error window finally disappears and HYSYS loads your simulation, you won't just have fixed a license—you'll have mastered the art of AspenTech licensing troubleshooting. Now, go converge that column.
Keywords: Aspen HYSYS license checkout failed, license server not responding, FLEXnet error, Aspen License Manager troubleshooting, HYSYS cannot obtain license.
The "License Checkout Failed" error in Aspen HYSYS typically occurs when the software cannot verify a valid license from the AspenTech Software License Manager (SLM). This can be due to network connectivity, server availability, or local configuration issues. Immediate Troubleshooting Steps
Check Connection & VPN: If you are using a network license (e.g., from a university or company), ensure you are connected to the proper network or active VPN.
Verify the License Server: Open the Aspen SLM Configuration tool and check if the license server status is active. What you see: “User 'jsmith' is not included
Wait for Initialization: On some systems, the "Sentinel RMS Development Kit" may take several minutes to load after a restart. Wait roughly 5 minutes before launching the software. Restart the Service:
Open Services (type services.msc in the Windows Start menu). Locate the Sentinel RMS License Manager. Right-click and select Restart. Common Solutions
Define Environment Variables: You can manually point HYSYS to the license server by adding a system environment variable. Variable Name: LSHOST
Variable Value: Your_Computer_Name (for local licenses) or the IP Address/Server Name (for network licenses).
Release "Stuck" Tokens: If you are using a shared token system, the error may occur because all licenses are currently in use. Ensure you have closed all other open Aspen instances (Plus, EDR, etc.).
Exclude from Antivirus: Add the AspenTech installation and common folders to your antivirus exclusion list to prevent it from blocking the licensing handshake. Advanced Support Then reread the license file using lmreread
If the issue persists, search the official AspenTech Support Center for specific error codes (e.g., Error -25 or -5) which often indicate an expired TECS agreement or corrupted license file.
Are you using a standalone local license or a shared network server? Software License Manager (SLM) - AspenTech Support Center
On the server machine (where the license resides):
Once resolved, prevent future outages with these habits:
| Practice | Why it helps | | :--- | :--- | | Document your license server IP | Keeps you independent of DNS failures. | | Set a monthly calendar reminder | Restart the license server (clears memory leaks). | | Keep a local backup license file | If the server goes down, you can switch to a node-locked trial license. | | Update Aspen License Manager | Old ALM versions may not support new OS updates (Windows 11, Server 2022). | | Disable sleep on license server | A sleeping server = a dead server for floating licenses. |
