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

Intellicensecache folder and IRMAGENT.LOG file

Mick_Pont
Beginner
515 Views

For years I've been plagued by a folder which appears from time to time when I use the Intel Fortran compiler on Windows. The folder is named Intellicensecache and I've never figured out the conditions under which it appears (though it's obviously something to do with the license for the compiler).

The trouble is that I end up with multiple copies of this folder, all in different places, which pollute my source code tree and sometimes end up getting copied to places where they shouldn't.

Today for the first time I've noticed the appearance of a file named IRMAGENT.LOG which contains a few lines to do with Intel Software Management (I can't remember the exact wording because I'm temporarily off the machine).

Does anyone know how to avoid these folders and files appearing? Are they supposed to be temporary files which are accidentally not being cleaned up for some reason? I wouldn't mind so much if they appeared always in the same place, but as I mentioned they seem to pop up anywhere at random.

Mick Pont

0 Kudos
9 Replies
Steven_L_Intel1
Employee
515 Views
Yes, this is related to the Intel Software Manager. I know I asked the developers before if there was a way to relocate the files, and they said no, but this is the first I have heard of them going in multiple locations. I will inquire and see what I can find.
0 Kudos
TimP
Honored Contributor III
515 Views
irmagent appears in my c:\temp since I changed the Windows configuration to put all temp files there. It doesn't clean up automatically, but the same file is re-used each time.
0 Kudos
mecej4
Honored Contributor III
515 Views
Mick Pont: By any chance, do you set TEMP to a directory within the current project while building and testing the project?
0 Kudos
Mick_Pont
Beginner
515 Views
mecej4: No - I don't touch TEMP - it's defaulting to C:\Users\mick\AppData\Local\Temp
0 Kudos
Steven_L_Intel1
Employee
515 Views
The developers tell me that these files are created in the TEMP folder, so something is apparently changing the definition of TEMP. I was also told that you can delete or rename the files: \Intel\Intel Software Manager\intelremotemonagent.exe \Intel\Intel Software Manager\intel64\intelremotemonagent.exe and reboot. and this will disable the functionality completely. (You'll still be able to compile.) You may have to repeat the "delete" after updating the compiler.
0 Kudos
Mick_Pont
Beginner
515 Views
Thanks for the info Steve - perhaps something is messing with TEMP in my build environment, although if it is I can't see it (our build system is fairly complicated, using a mixture of cygwin/GNU make/shell scripts etc. but I can't see TEMP being set anywhere). Also, I can't locate a file named intelremotemonagent.exe anywhere on my machine. I'm using Intel(R) Visual Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 13.0.1.119 Build 20121008 My machine does have a folder named c:\Intel but all it contains is another folder named Logs which contains files like IntelControlCenter.log. Otherwise, under "C:\Program Files\Intel" and "C:\Program Files (x86)\Intel", no executables with the word "agent" as part of their name.
0 Kudos
Steven_L_Intel1
Employee
515 Views
Ugh - the forum ate part of my text. Look in C:\Program Files (x86)\Common Files\Intel\Intel Software Manager
0 Kudos
Mick_Pont
Beginner
515 Views

It turned out the problem was not with environment variable TEMP, but TMP. And the problem was that I have various batch files which dynamically change TMP to point at different directories, and those were the directories that Intellicensecache was appearing in.

So - in the end the fix was simple - I just changed all my batch files to use a temporary name other than TMP

Thanks for the help.

Mick

0 Kudos
Steven_L_Intel1
Employee
515 Views

Thanks for coming back and giving us the resolution.

0 Kudos
Reply