Get below error when try to launch Ensight in ANSYS 19.0 on Linux by running {INSTALLATION_PATH}/ansys_inc/v190/CEI/bin/ensight102 This is EnSight Client 10.2.3(b) (12/4/2017) build: 54808 ANSYS_R19 —- — ——- ====== Running on computer: XXXXXXXX getenv(CEI_HOME) returned [/ansys_inc/v190/CEI] Couldn’t find a valid slim8.key license file in the standard locations. Please check your environment variables as indicated in the Getting Started manual and make sure you have a valid slim8.key license file installed and that slimd8 is running if using a floating license. Can’t initialize licensing: license_initialize: Unable to determine license server type (error code 0).
-
-
April 5, 2023 at 2:32 pmFAQParticipant
It’s a known issue in R19.0, should be fixed in R19.1 and future releases. 3 options to resolve the issue, Option #1 is recommended: Option #1 (recommended): Set environment variable AWP_ROOT190 to {INSTALLATION_PATH}/ansys_inc/v190, e.g. for Bash Shell: export AWP_ROOT190=/ansys_inc/v190 The licensing autodetection code properly looks for SLiM then tries the ANSYS license manager, and do other changes for ANSYS customers, including part options, background changes, ANSYS R19 branding, etc. Option #2 (should work but not recommended): Set environment variable ENSIGHT10_LM to ansys, e.g. for Bash Shell: export ENSIGHT10_LM=ansys It forces Ensight to look for ANSYS license manager only but no SLiM. And if AWP_ROOT190 is not set, EnSight won’t have the other changes that we’ve done for ANSYS customers, including part options, background changes, ANSYS R19 branding, etc. Option #3 (should work but not recommended); Set environment variable ENSIGHT_ANSYS_VERSION to 19.0, e.g. for Bash Shell: export ENSIGHT_ANSYS_VERSION=19.0 The licensing autodetection code properly looks for SLiM then tries the ANSYS license manager. But if AWP_ROOT190 is not set, EnSight won’t have the other changes that we’ve done for ANSYS customers, including part options, background changes, ANSYS R19 branding, etc. In addition, it could potentially cause problems for R19.1 and subsequent versions.
-
Introducing Ansys Electronics Desktop on Ansys Cloud
The Watch & Learn video article provides an overview of cloud computing from Electronics Desktop and details the product licenses and subscriptions to ANSYS Cloud Service that are...
How to Create a Reflector for a Center High-Mounted Stop Lamp (CHMSL)
This video article demonstrates how to create a reflector for a center high-mounted stop lamp. Optical Part design in Ansys SPEOS enables the design and validation of multiple...
Introducing the GEKO Turbulence Model in Ansys Fluent
The GEKO (GEneralized K-Omega) turbulence model offers a flexible, robust, general-purpose approach to RANS turbulence modeling. Introducing 2 videos: Part 1 provides background information on the model and a...
Postprocessing on Ansys EnSight
This video demonstrates exporting data from Fluent in EnSight Case Gold format, and it reviews the basic postprocessing capabilities of EnSight.
- When I am trying to launch Fluent, the GUI is stuck at this message. Host spawning Node 0 on machine “abcd-pc” (win64) There is no error. Same problem in serial mode I am not connected to VPN.
- How many cores are supported with a single or multiple ANSYS HPC pack?
- Unable to save project: Access to the path is denied. Error message is “Access to the path “X:….” is denied”.
- Question: Trying to install and seeing Mount Directory Error “Cannot locate file for media #::1…”
- Q: How do I set the license server from my client machine?
- Tutorial:: Remote Solve Manager Tutorial: Configuring an Advanced ANSYS RSM Cluster (ARC) R18
- Failover feature ‘Discovery – Level 1’ is not available
- Are Ansys versions compatible with one another ?
- How do I configure RSM to send a solve to a remote machine (no scheduler)?
- Unable to start the Geometry or Mechanical Editor (Linux)
© 2024 Copyright ANSYS, Inc. All rights reserved.