We just upgraded our Quartus license from Standard to Pro. The license file is detected, so can open Quartus Pro, but compiles for any Arria 10 part fail - with an error saying: Warning(292000): FLEXlm software error: Version of vendor daemon is too old. and a statement: Error(119013): Current license file does not support the 10AS066H1F34E1HG device. Go to the Self-Service Licensing Center on the Intel FPGA website to manage your licenses (https://mysupport.altera.com/AlteraLicensing/license/index.html).
We have upgraded the license daemon to to Version V188.8.131.52 build 245043 x64_n6. (current version on the Intel website.) but still cannot build with the Arria10 family.
Which version of Quartus Pro are you using?
'We have upgraded the license daemon to to Version V184.108.40.206 build 245043 x64_n6. ' - - - - since you have upgraded it already it should have worked.
now check the environmental variable setting whether it is pointing to correct version of Quartus Pro?
Hi - thank you for the suggestion. It does not solve the problem. The license is being found. I can open the Quartus version. I can pass analysis and synthesis. It does not fail until the fitter. The failure is the same as noted in the original post above. Thanks. Jen
I am using Quartus Pro 19.1.0 build 240 03/26/2019.
In case it matters - I do have some older versions of Quartus installed on my PC - to support some of my older products. The oldest one is 12.1sp1. The other versions work, and I can build successfully. (17.0, 18.0, and 12.1). Thanks. Jen
'now check the environmental variable setting whether it is pointing to correct version of Quartus Pro?' ---- Have you confirmed it?
Can you please check uninstalling & reinstalling the Quartus Pro 19.1?
I am looking forward to listen you.
I uninstalled 19.1 and installed 19.2, but it did not fix the failure.
The error is the same:
Error(119013): Current license file does not support the 10AS066H1F34E1HG device. Go to the Self-Service Licensing Center on the Intel FPGA website to manage your licenses (https://mysupport.altera.com/AlteraLicensing/license/index.html).
Please '4.4. Configuring the License Manager Server ' from link below,
Can you provide the project file (Tool menu-> Archive Project) for replication?
Yes we have configured the license server using 4.4 and verified the versions of the alterad daemon and the lmgrd daemon.
Lmgrd is: lmgrd v220.127.116.11 build 176543 x64_n6 - Copyright (c) 1988-2015 Flexera Software LLC. All Rights Reserved.
Alterad is: (alterad) FlexNet Licensing version V18.104.22.168 build 245043 x64_n6
And attached please find the archive for the project I am trying to build.
Of note - another engineer made a different empty project to verify and he got the same failure on his machine.
I am the Altera-dedicated FAE covering this account and the customer still has the same problem. It happens on multiple machines and even with Quartus 19.2. Here is the info about daemons the customer has upgraded to:
- Regarding versions for the license daemons:
- Lmgrd is: lmgrd v22.214.171.124 build 176543 x64_n6 - Copyright (c) 1988-2015 Flexera Software LLC. All Rights Reserved.
- Alterad is: (alterad) FlexNet Licensing version V126.96.36.199 build 245043 x64_n6
I also looked at their license file and that looked fine. I had another customer experience a similar issue but that got resolved when they upgraded the license daemons. Is there something else with the FlexLM software that they need to change?
May I know the operating system which you are using?
please check the supported operating system,
Could you provide the screenshot of error?
Hi Jen & Steve,
My apology for coming back late as I just came back from a long vacation + public holiday.
For your case, the daemon version used was 188.8.131.52 and I assumed you've downloaded from here : https://www.intel.com/content/www/us/en/programmable/support/support-resources/download/licensing/daemons.html and upgraded. Please confirm.
At this point, I am suspecting there are some conflict during the license authentication. Can you follow below KDB:
There some some numbers of users resolved exact issue by updated the daemon. That's the reason I would want to to test with mentioned KDB. Let me know the outcome and we will see what to do next.
Intel Customer Support