Building a solution on a remote computer using TFS results in ifort: error #10310: Failed to enable trusted storage check..

[Nathan_K_]

When I trigger a new build for our solution from my development machine in the TFS Build Visual Studio integration, a licensing error prevents the Fortran projects in the solution from succeeding on the build machine:

ifort: error #10310: Failed to enable trusted storage check for licensing: WARNING: Enable Trusted Storage failed (flexnet error code 21). Trusted Storage based license could not be supported

Other project types build okay.

I can build the solution okay on my development machine. If I log in to the build computer and build the solution from the Visual Studio IDE or from the command line using devenv.com, the Fortran projects in the solution build okay and there is no licensing error. I am not using a  trial license on the build machine; I am using an activated product license. When logging into the build machine to build the solution I am using the same UAC used by automated TFS build controller.

I am using the following development tools:

Team Foundation Server (TFS) 2010

Development Machine: Microsoft Visual Studio Premium 2013 Version 12.0.30110.00 Update 1

Build Machine: Microsoft Visual Studio Premium 2013 Version 12.0.30110.00 Update 1

Build Machine Operating System: Windows Server 2012 R2 Standard, 64-bit (x64)

Intel(R) Visual Fortran     Package ID: w_fcompxe_2013_sp1.2.176
Intel(R) Visual Fortran Composer XE 2013 SP1 Update 2 Integration for Microsoft Visual Studio* 2013, 14.0.0086.12

What should I do about this licensing error to successfully build of my solution on a remote computer using TFS build?

[Steven_L_Intel1]

I've been told that the following will fix this. Let me know if it works (or doesn't).

On the Windows Server system, open a Fortran Command Prompt window (Start > All Programs > Intel Parallel Studio XE 2013 > Command Prompt > Parallel Studio XE with Intel Compiler XE 14.0 > Intel 64 Visual Studio 2013 Mode,

Type the command:

runas /user:administrator "ifort /v"

It will prompt you for the administrator password - enter it. You can substitute some other account with administrator privilege (I think). This will install the licensing service.

[Nathan_K_]

Steve, no running the command

/runas /user:<administrator domain>\<admin user name> "ifort /v"

did not resolve the licensing issue. When I ran this command in the "Intel 64 Visual Studio 2013 Mode" console  another console window briefly popped up and completed before I could read what occurred. After running the command I triggered a new build and verified that I still get the licensing error.

If I look at the running services, I see that there are two FlexNet services running on the build machine:

Name	Status	Startup Type	Log On As
FlexNet Licensing Service	Running	Automatic	Local System
FlexNet Licensing Service 64	Running	Automatic	Local System

Anything else I can try?

[Steven_L_Intel1]

Can you run the compiler from the build environment command window normally? (Just an "ifort -v" will do.)

I am going to move this to the licensing forum - the folks there have more experience with issues such as this.

[Nathan_K_]

When I log into the build environment I can build my solution without the license issue in the Visual Studio IDE. I can also build it okay from the command line using devenv.com. However, when  the Team Foundation Server tries to run devenv.com in an automated build process on the build machine, I get the licence error.

When I launch the Intel 64 Visual Studio 2013 Mode console in the build environment and run the command:

ifort -V

I get the following output:

Intel(R) Visual Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 14.0.2.176 Build 20140130
Copyright (C) 1985-2014 Intel Corporation.  All rights reserved.
ifort: command line warning #10155: ignoring option '/V'; argument required

ifort: command line error: no files specified; for help type "ifort /help"

If I use a lower case v, I  get the following output:

Intel(R) Visual Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 14.0.2.176 Build 20140130
Copyright (C) 1985-2014 Intel Corporation.  All rights reserved.
ifort: command line warning #10006: ignoring unknown option '/v'

ifort: command line error: no files specified; for help type "ifort /help"

[Steven_L_Intel1]

Ok - let's see if some of the licensing folks have an idea.

[Nathan_K_]

I had to open an issue with Intel Premiere Support to resolve this problem. 

The problem was the enviroment variable INTEL_LICENSE_FILE on the build computer was set to a series of paths like as follows:
C:\Program Files (x86)\Common Files\I ntel\Licenses;C:\Program Files\Common Files\Intel\Licenses;C:\PROGRA~2\Intel\COMPOS~1\bin\ia32

Changing this environment variable on the build machine to point to the complete license filepath (C:\Program Files (x86)\Common Files\Intel\Licenses\<licenseFileName>.lic) allowed the automated build triggered from my development machine to find the license file and build the solution successfully.

For some reason (unknown to me), when running in the automated build context, the licensing software does not properly parse this environment variable and chooses an incorrect filename for the license file. Building in  other contexts, such as when remoting into the build machine and building manually, the same environment variable is parsed okay and the correct license file is found.

It is not obvious how to tell what is going wrong when this licensing issue happens. I spent a lot of time making wild guesses and being frustrated. Eventually from the support interaction I learned that you can specify another enviroment variable, INTEL_LMD_DEBUG and set it to a log file (c:\license_debug.txt). After reading the log file after getting the issue it was easy to see was going wrong with the license file name being incorrectly read from INTEL_LICENSE_FILE.

[Hung_D_]

We ran into the same issue when we upgrade from Parallel Studio XE with Intel Compiler XE 14.0 SP1 to Parallel Studio XE with Intel Compiler XE 14.0 SP2 Update2

We have our continuous integration system running under a different user that is not an administrator account which runs the install.

When we completed the install, it looks like the installer created a new license file which is only accessible by administrators (the install user). The solution for us was to modify the permissions of the license file to allow the continuous integration user to read the new intel license file.