Compaq Visual Fortran Software Intel Visual Fortran Composer XE v.2011.0.104 The Intel Visual Fortran Composer XE 2011 is a comprehensive set of software development tools that includes the following components: Intel Fortran Compiler, Intel Math. Valid license from Compaq required for possession, use or copying. The Compaq Fortran message catalog file was not found on this system. This error has.

I have a named-user license for Intel Fortran that used to work, but is now giving me the error message copied below when I try to compile. I had to do an offline installation of my license because my company is behind a proxy that requires a password, and the Intel Software Manager doesn't allow me to enter a proxy password. I'm not sure what changed that let to the errors.

I am using the same computer, so my license file shouldn't need to be updated as far as I can tell. Any help would be greatly appreciated.

1>Compiling with Intel(R) Visual Fortran Compiler 16.0 [IA-32]. 1>hello.f90 1>Error: A license for Comp-FW is not available now (-1). 1>A connection to the license server could not be made. You should 1>make sure that your license daemon process is running: both an 1>lmgrd.exe process and an INTEL.exe process should be running 1>if your license limits you to a specified number of licenses in use 1>at a time.

Also, check to see if the wrong port@host or the wrong 1>license file is being used, or if the port or hostname in the license 1>file has changed. 1>License file(s) used were (in this order): 1> 1. Trusted Storage 1> 2. C: Program Files (x86) Common Files Intel Licenses COM_W__FOR_XXXX-XXXXXXXX.lic 1> 3.

C: Program Files (x86) Common Files Intel Licenses USE_SERVER.lic 1> 4. C: Program Files Common Files Intel Licenses 1> 5. C: Program Files (x86) IntelSWTools compilers_and_libraries_2016 windows bin ia32 *.lic 1>Please visit if you require technical assistance. 1>ifort: error #10052: could not checkout FLEXlm license.

If it doesn't, I suggest you visit and download the Java package appropriate for your version of OS X. Dsdt editor mac.

Okay, so, good news is that it's not a MAC address issue. First of all, have you reinstalled the program recently?

If so, what version did you install? Secondly, check that your license file is located in C: Program Files (x86) Common Files Intel Licenses. I tried to send you an email containing your license file; hopefully it worked. My end of the system seemed to be behaving strangely so I don't know whether it worked; check that the serial number mentioned in the mail matches yours.

If you do use the license I sent you, keep your old one tucked away in your documents folder or something, just in case. Thirdly, make sure you don't have any other license files (from evaluations or whatever) in these directories: 1> 1. Trusted Storage 1> 2. C: Program Files (x86) Common Files Intel Licenses COM_W__FOR_XXXX-XXXXXXXX.lic 1> 3.

C: Program Files (x86) Common Files Intel Licenses USE_SERVER.lic 1> 4. C: Program Files Common Files Intel Licenses 1> 5. C: Program Files (x86) IntelSWTools compilers_and_libraries_2016 windows bin ia32 *.lic They could clutter things up and confuse the license system.

If you have other licenses in there, remove them. Thank you for resolving the MAC address question. I didn't see an email with a new license file, but I'm pretty sure the one I have is current because it matches what I see in the Intel registration center when I log in. I only have one other license file in the directories that you listed. It is the one named 'USE_SERVER.lic'. It basically just points to my own computer as the host with the default port number.

I'm pretty sure this was an old attempt to use a floating license before it became clear that I had a named user license. I am working with my tech support here to get that file deleted, as I am not an admin on my system. I will let you know if that helps. In the meantime, I did notice that I have two versions of Intel Fortran installed. One is Composer XE 2011 SP1, and the other is Intel Parallel Studio XE 2016. It appears that the 2016 version was a trial that has expired, but my Visual Studio 2013 is still pointing to it when I try to compile (when I go to Visual Studio -> Help-> About, it lists the 2016 version). As confirmation, I ran ifort.exe on the command line with each of the versions.