Error with licensing

[Haunter]

Hi!

I tried to run a simulation on quartus lite. I have installed the license path, and I did so correctly.

I really, really need help with this.

here's the last few snippits of when I am running the simulation:

**** Generating the ModelSim .do script ****

C:/Users/hunte/OneDrive/Documents/Quartus/ReTest/simulation/qsim/ReTesting.do generated.

Completed successfully.

**** Running the ModelSim simulation ****

c:/intelfpga_lite/22.1std/questa_fse/win64//vsim -c -do ReTesting.do

Unable to checkout a license. Make sure your license file environment variable (e.g., LM_LICENSE_FILE)

is set correctly and then run 'lmutil lmdiag' to diagnose the problem.

Unable to checkout a license. Vsim is closing.

** Error: Invalid license environment. Application closing.

Error.

Here's when I ran that lmutil lmdiag:

Microsoft Windows [Version 10.0.22621.2283]
(c) Microsoft Corporation. All rights reserved.

C:\Users\hunte>c:/intelfpga_lite/22.1std/questa_fse/win64//vsim -c -do ReTesting.do
Reading pref.tcl

# 2021.2

# ReTesting.do
# invalid command name "ReTesting.do"
Questa> lmutil lmdiag
# lmutil - Copyright (c) 1989-2019 Flexera. All Rights Reserved.
# FlexNet diagnostics on Thu 9/21/2023 16:26
#
# -----------------------------------------------------
# License file: C:\Users\hunte\Downloads\LR-137492_License.dat
# -----------------------------------------------------
# "intelqsimstarter" v2024.01, vendor: mgcld, expiry: 20-sep-2024
# vendor_string: 6D43F86F
# uncounted nodelocked license, locked to ethernet address "90784122d283" starts: 21-sep-2023, expires: 20-sep-2024
#
# This is the correct node for this node-locked license
# -----------------------------------------------------
#
# Enter <CR> to continue: "intelqsimstarter" v2024.01, vendor: mgcld, expiry: 20-sep-2024
# vendor_string: 6D43F86F
# uncounted nodelocked license, locked to ethernet address "90784122d283" starts: 21-sep-2023, expires: 20-sep-2024
#
# This is the correct node for this node-locked license
# -----------------------------------------------------
Questa> CR
Bad pointer access... Closing vish.
writing stack trace to vish_stacktrace.vstf

C:\Users\hunte>

here's that stacktrace:

# Current time Thu Sep 21 16:26:26 2023
# Program = vish
# Id = "2021.2"
# Version = "2021.04"
# Date = "Apr 14 2021"
# Platform = win64

Exception c0000005 has occurred at address 4017c560. Traceback:
# 0 0x4017c560: '<unknown (@0x4017c560)>'
# 1 0x66605226: 'TclInvokeStringCommand + 0xc6'
# 2 0x66607103: 'TclNRRunCallbacks + 0x63'
# 3 0x66607103: 'TclNRRunCallbacks + 0x63'
# 4 0x66608974: 'Tcl_EvalEx + 0xa34'
# 5 0x666091a8: 'Tcl_Eval + 0x38'
# 6 0x6660a4f0: 'Tcl_GlobalEval + 0x30'
# 7 0x401aba22: 'Mtirpc_Init + 0x235a2'
# 8 0x401ae6c4: 'Mtirpc_Init + 0x26244'
# 9 0x40775810: 'Tclsqlite3_Init + 0x1c000'
# 10 0x5965257d: 'BaseThreadInitThunk + 0x1d'
# 11 0x5a54aa68: 'RtlUserThreadStart + 0x28'
StackWalk failed 0
# End of Stack Trace

[sstrell]

So the path for LM_LICENSE_FILE is set up correctly in your environment variables?

[AR_A_Intel]

Hello

Welcome to INTEL forum. Could you help re-confirm your environment variable setup again? You need to set your LM_LICENSE_FILE environment variable to point to the license that Intel provides. c:\intel\license.dat or something similar.

You can refer to link on how to set environment variable.

To make this entry, you may perform a windows Search for "System Variables" and then click on "Edit the System Environment Variables" and then click "Environment Variables". Be aware that you must add the entry in System variables, not user variables.

https://www.intel.com/content/www/us/en/docs/programmable/683472/21-4/environment-variables.html          

Specifying the License for the Questa

https://www.intel.com/content/www/us/en/docs/programmable/683472/21-4/specifying-the-license-for-the-software.html   

[AR_A_Intel]

We have not heard from you and I hope that my last note clears up this matter. I will now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.