Aspen Hysys License Checkout Failed
If the error persists despite correct network settings, the client may be reading stale configuration data from the Windows Registry.
Procedure:
Ask your IT department or lab supervisor: Is the license server powered on? If a summer storm took down the server room, no amount of clicking will help.
If the error message specifies "All licenses are in use," the solution is administrative:
Quick Diagnostic Commands (Windows):
Still stuck?
Provide:
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.
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.). Aspen Hysys License Checkout Failed
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
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
This feature describes the implementation of an Automated License Diagnostic Utility
within Aspen HYSYS to address and resolve the "License Checkout Failed" error. Feature: License Health Monitor & Auto-Repair
The "License Checkout Failed" error typically occurs due to communication gaps between the client machine and the AspenTech License Server, or services like the Sentinel LDK License Manager SLM (Software License Manager) not running. Core Functionalities One-Click Diagnostic Service
: A standalone or integrated tool that checks the status of essential licensing services (e.g., Sentinel LDK License Manager
). If a service is found to be stopped, the utility provides a "Start/Restart Service" button to restore connectivity. SLM Configuration Validator : Automatically verifies that the SLM Configuration Wizard
is pointing to the correct server address or localhost. It should highlight mismatched version numbers or expired trial tokens. Port Connectivity Ping
: Tests communication over default licensing ports (such as TCP/IP ports used by FlexNet or SLM) to identify if a firewall is blocking the checkout request. License Reservation Alert
: If the failure is due to all seats being occupied or reserved for specific user groups (Error -101/147), the tool will display the current user list and estimated "check-in" times to improve transparency. User Experience (UX) Direct Troubleshooting
: Instead of a generic "Failed" popup, the error message includes a "Run Diagnostics" Visual Status Indicators : A dashboard showing: Service Status : Green (Running) / Red (Stopped). Server Reachability : Successful ping to the license server. License Availability : Number of seats currently free in the pool. Technical Requirements Permissions
: The utility must request administrative rights to restart Windows Services ( services.msc Compatibility If the error persists despite correct network settings,
: Supports both standalone and network (floating) license configurations. user guide for this diagnostic utility? Fixing common licensing errors - Ansys Optics
The "License Checkout Failed" error in Aspen HYSYS usually indicates a communication breakdown between your computer and the Software License Manager (SLM) or the license server. Below are the primary methods to resolve this, categorized by their cause. Method 1: Configure the Host Connection
If the SLM cannot find your computer on the network, you may need to manually point the software to your local machine or server. Set Environment Variable:
Right-click This PC or My Computer > Properties > Advanced System Settings. Go to Environment Variables. Under System Variables, click New. Set Variable name to LSHOST.
Set Variable value to your computer name (or the IP address/name of your license server). Restart HYSYS to check if the connection is established. Method 2: Verify License Availability (SLM Configuration)
A failed checkout often occurs if the SLM is not looking in the right place for your license file or if "local keys" are being ignored. Update SLM Settings:
Open the aspenONE SLM License Manager (found in the AspenTech folder in your Start menu).
Click the Configure button to launch the SLM Configuration Wizard.
Under Advanced Settings, ensure the box for "Ignore local keys" is unchecked. Click Apply Changes. Method 3: Reset the License Service
Sometimes the license server service simply needs a manual refresh to "check out" the features correctly. Restart the Sentinel RMS Service:
Search for Services.msc in the Windows Start menu and open it. Locate Sentinel RMS License Manager. Right-click and select Restart.
Alternatively, use loadls.exe (found in C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT) to "Remove" and then "Add" the server again. Method 4: Troubleshoot "All Licenses in Use"
If the error specifically mentions that licenses are in use, it is likely a token/seat capacity issue. If the error message specifies "All licenses are
Check Token Usage: HYSYS uses a token-based system. Ensure no other instances of HYSYS, Aspen Plus, or EDR are running on your machine or others in your network pool that might be exhausting the available seats.
VPN Check: If you are working remotely (e.g., as a student or employee), ensure your VPN is active. The license checkout will fail immediately if the software cannot reach the campus or company network where the server resides. Method 5: Address Database Corruption
In some versions (like V12 or V14), database errors can trigger a generic "license checkout failed" message. Clear the Database Instance: Navigate to C:\ProgramData\AspenTech\APED V[YourVersion]. Run the DeleteDBInstance.bat file as an Administrator.
Wait for the command prompt to finish and close automatically. Relaunch HYSYS, and it will attempt to restore the database.
For further help, you can consult official documentation like the SLM License File Installer Guide or contact AspenTech Support.
Are you using a standalone license on your own machine, or are you connecting to a university or company network server? Software License Manager (SLM) License File Installer
If the quick fixes fail, follow this tiered methodology.
Occasionally, a computer crashes while HYSYS is open, leaving a "phantom" license checked out on your local machine that prevents a new checkout.
Not all "Checkout Failed" errors are equal. Your specific error message (check the Details button) tells you the root cause.
| Error Message Subtext | Likely Cause | | :--- | :--- | | "No such feature exists" | Wrong license file or product version mismatch. | | "Cannot connect to license server" | Network issue, firewall blocking port, or server down. | | "License server machine is down or not responding" | DNS resolution failure. | | "All licenses are in use" | No concurrent seats available. | | "The license file has been corrupted" | Corrupted local trust cache. | | "User/host not authorized" | User is not in the license server's inclusion list. |
Let’s fix each of these.
If you manage the license server, try these diagnostic commands.