Aspen — Hysys License Checkout Failed Link

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

: Supports both standalone and network (floating) license configurations. user guide for this diagnostic utility? Fixing common licensing errors - Ansys Optics

The "Aspen HYSYS License Checkout Failed" error typically occurs when the software cannot communicate with the AspenONE SLM (Software License Manager) to verify authorization. Common Causes

Server Connectivity: The computer cannot reach the license server due to network issues, incorrect IP/hostname settings, or being disconnected from a required VPN/campus network. Aspen Hysys License Checkout Failed

Service Failures: The Sentinel RMS License Manager or Aspen SLM service is not running on the host or server machine.

Token Exhaustion: A "token leak" in some versions (e.g., v14.5 or v15.0) can cause tokens to remain checked out even after the application closes, eventually exhausting the pool.

Environment Configuration: The LSFORCEHOST or LSHOST environment variables may be missing or pointing to the wrong machine.

Version Mismatch: The license file may be outdated and not support the newer version of HYSYS being launched. Troubleshooting Steps Verify Server Configuration Open the AspenONE SLM License Manager from the Start menu.

Click Configure and ensure the correct server name or IP address is listed.

If the local machine is the server, ensure it is listed as localhost or by its specific computer name. Restart Licensing Services Open Windows Services (services.msc). Locate Sentinel RMS License Manager and Aspen SLM Service. Right-click and select Restart. Set Environment Variables

If the system cannot retrieve servers, manually add an environment variable. Go to System Properties > Advanced > Environment Variables.

Under System Variables, create a new variable named LSHOST and set its value to your license server's hostname. Address Token Leaks

For users on affected versions (v14.5+), an IIS reset may be required to flush the Process Data REST cache and release stuck tokens. Check Network Access

Ensure you are connected to your organization’s VPN if working remotely, as most institutional licenses require a direct network handshake.

Check that firewall ports (typically TCP 5093 for Sentinel RMS) are open.

When Aspen HYSYS displays a "License Checkout Failed" error, it typically indicates a communication break between your local workstation and the Sentinel RMS or SLM (Software License Manager) server. This can be caused by network interruptions, incorrect environment variables, or server-side restrictions. Immediate Troubleshooting Steps This feature describes the implementation of an Automated

The "Retry" Method: If the software has been inactive for a period, a temporary timeout can occur. Try opening the file and clicking Retry three or four times; users often find that the connection re-establishes after multiple attempts.

Check Your Network: For users on university or company networks, ensure you are connected to the VPN or specific network (like Ivanti) required to reach the license server. If you are using a local license, try disconnecting from the internet entirely before launching to see if it bypasses network-check conflicts. Common Technical Solutions 1. Set the 'ls host' Environment Variable

A frequent cause is that the system cannot identify the license server's location. You can manually point HYSYS to the right place:

Right-click This PC or My Computer > Properties > Advanced System Settings. Click Environment Variables. Under System variables, click New. Variable name: ls host

Variable value: Enter your computer name (if local) or the server's IP address/hostname.

Restart HYSYS and check the "Subnet Servers" list in the SLM tool. 2. Configure the SLM License Manager

If your organization uses a dedicated network license, you must manually add the server to the SLM configuration: Open the AspenONE SLM License Manager from the Start menu.

Click Configure and enter the Server Name or IP (e.g., ://yourdomain.com). Click Add Server and then Apply Changes. 3. Address Firewall Blocks

Firewalls can block the communication ports (typically port 5053 or other dedicated ports) used by the license manager.

The "License Checkout Failed" error in Aspen HYSYS typically indicates that the software cannot verify a valid license from the Software License Manager (SLM)

. This is often due to server connection issues, missing environment variables, or expired license files. Common Fixes for "License Checkout Failed" Check Server Connection & VPN

: Ensure you are connected to your organization's network or active VPN. Many institutional licenses require a direct connection to the license server. Update the "LS_HOST" Environment Variable Open regedit

: If the license server isn't found, you may need to manually point the software to it: Right-click My Computer Properties Advanced system settings Environment Variables System variables , create a variable named

Set the value to the name or IP address of your license server. Run SLM License File Installer : If you have a local license file, use the AspenTech SLM License File Installer to re-install or schedule a future license. Reset the SLM Configuration SLM Configuration Wizard

(found in the AspenTech start menu folder) to re-input the server details and ensure the registry is correctly updated. Run as Administrator

: Occasionally, administrative privileges are required for the SLM to update local registry keys or access the Properties Database Manager Check Token Availability

: If your institution uses a token-based system, all available licenses may be in use by other users. Try waiting or asking colleagues to close unused sessions. Troubleshooting Steps Summary Potential Resolution Verify Network Ensure VPN or LAN connection to the server is active. Check SLM Status

Open the SLM License Manager to see if the server status is "Connected". Variable Check Verify that the system environment variable matches your server. Version Match

Ensure your SLM version is compatible with your HYSYS version; older license managers may not support newer software.

If these steps do not resolve the issue, you can search for technical tips and submit support tickets through the AspenTech Support Center University of Alberta

Are you using a standalone (local) license or a network-based license from a company or university server?

5. Advanced Resolution: Cleaning Stale Registry Entries

If the error persists despite correct network settings, the client may be reading stale configuration data from the Windows Registry.

Procedure:

  1. Open regedit.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager.
  3. Look for keys related to AspenTech or ASPLED_LICENSE_FILE.
  4. Verify that the paths match the current server environment variables.
  5. Additionally, check HKEY_CURRENT_USER\Software\AspenTech for user-specific overrides that might point to incorrect locations.

Long-term fixes and best practices

  • Central monitoring: run license usage monitoring and alerts to detect exhaustion early.
  • High-availability for license servers: use redundancy or failover where vendor supports it.
  • Document and version-control license configuration: LM_LICENSE_FILE settings, hostnames, port numbers.
  • Use DNS CNAMEs for license servers so underlying hosts can be changed without client reconfiguration.
  • Enforce NTP time sync across license hosts and clients.
  • Maintain an inventory of node-locked host-IDs and re-host policies before hardware changes or VM cloning.
  • Automate license checkout logging and periodic audits to detect misuse or leaks.
  • Establish support contact and escalation with AspenTech or the license vendor and retain license file backups.

6. Preventative Measures

To minimize downtime caused by license failures, organizations should implement the following:

  • Redundant Servers: Configure a Triad (Primary, Secondary, Tertiary) license server setup to ensure automatic failover.
  • Monitoring: Implement a script or monitoring tool to ping the license server port and alert IT if the service stops responding.
  • Documentation: Maintain a static IP address for the license server to avoid DNS resolution issues.
  • Startup Automation: Configure the FlexNet service to restart automatically upon server reboot.

2. Licensing Architecture Overview

AspenTech utilizes FlexNet Publisher (formerly FLEXnet), the industry standard for software licensing. The system comprises three primary components:

  1. The Client (HYSYS.exe): The software application installed on the user's machine.
  2. The License File (*.lic): A text file containing encryption keys, expiration dates, feature versions, and hostID information.
  3. The License Manager (lmgrd/AspenTech): A daemon running on the license server that reads the license file and manages the pool of available tokens.

When HYSYS starts, it queries the license manager for a specific "feature" (e.g., aspenone.hysys.plant). If the manager validates the request against the encrypted license file, a token is "checked out," allowing the software to run.