Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29236 Discussions

Older Version of Compiler Not Recognizing My Manually Generated License File (urgent)

Eric_S_4
Beginner
537 Views

Hello.  I am in urgent need of some guidance.  I recently purchased a single named-user license for Intel's Fortran Compiler for Linux.  While the baseline purchase was for the newest 2016 version of the compiler, a current project requires that I download the 2013 Update 2 version of the compiler.  I followed the online instructions for downloading and installing an older version of the compiler.  In addition, before trying the installation, I followed the instructions for registering my product and manually creating and downloading a license file based on the host ID of my target system.  When I try to install the product and point the installer to my manually generated license file, I get the following error message:

"The license file(s) you provided is not valid for this product."

I am at a loss as to what's going on.  I followed the Intel online instructions verbatim and it's not working.  I've submitted an issue to Premier, but have yet to hear back.  In the meantime, I thought I'd also drop a thread on this forum.  Any guidance would be much appreciated.

 

Thanks.

0 Kudos
3 Replies
Steven_L_Intel1
Employee
537 Views

Please use Send Author a Message (on my reply) and include or attach your license file to a private message. Please also tell me the complete filename of the older compiler you downloaded.

0 Kudos
Steven_L_Intel1
Employee
537 Views

I suspect I know the problem, based on your mention of a "target system". The license you have requires "activation" on a new system. There is a limit of three activations per license. If you took the license file and simply moved it to another system, it would not work,

There is probably another way to do this that I am not familiar with, but what will work is to install the 2016 version on the "target system" by serial number, which will activate on the new system. Then you can install the 2013 version.

0 Kudos
Steven_L_Intel1
Employee
537 Views

This problem was resolved. The underlying cause was the use of a "bonded Ethernet" setup which the licensing check of the 2013 compiler didn't understand, but more recent versions do. I was able to provide Eric with what he needed to get the 2013 compiler installed on that system.

0 Kudos
Reply