IFLangService revisted

[Brian_Francis]

Hi Steve,

I am using XE 12 with Visual Studio. I recently installed the latest 16 release of Fortran and VS 2015. After doing so, I have run into some difficulties building my application using VS 2010 with Fortran 12. One was the /MP issue discussed earlier. This was easily solved by editing the vfproj files. I now have no issues building my application from within VS 2010.

I use devenv.exe in a batch file to automate the build of many different sln files. For example:

"%VC100_COMPILER%\Common\IDE\DEVENV.EXE" part1.sln /build "Release|Win64" /out build.log
"%VC100_COMPILER%\Common\IDE\DEVENV.EXE" part2.sln /build "Release|Win64" /out build.log
...

I now get the following warning repeated many times in my log file for each solution built:

Package 'Intel.Fortran.IFLangService.IFLangServicePackage, IFLangService, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null' failed to load.

This problem was discussed in an earlier thread, now closed. Is there a solution to this problem?

Thanks,
Brian.

[Steven_L_Intel1]

There may be an issue with the PATH environment variable. How do you establish the environment to run your batch file?

[Brian_Francis]

Hi Steve,

I started a Windows command shell and called devenv.exe as shown earlier. I get multiple IFLangServicePack warnings in the log file. Here is the System Properties > Advanced > Environment Variables > System variables PATH setting:

%INTEL_DEV_REDIST%redist\intel64_win\mpirt;
%INTEL_DEV_REDIST%redist\intel64_win\compiler;
%INTEL_DEV_REDIST%redist\ia32_win\mpirt;
%INTEL_DEV_REDIST%redist\ia32_win\compiler;
C:\ProgramData\Oracle\Java\javapath;
C:\Program Files (x86)\Intel\Composer XE 2011 SP1\redist\intel64\mkl;
C:\Program Files (x86)\Intel\Composer XE 2011 SP1\redist\ia32\mkl;
%F_EM64T_REDIST12%redist\intel64\mpirt;
%F_EM64T_REDIST12%redist\intel64\compiler;
%F_IA32_REDIST12%redist\ia32\mpirt;
%F_IA32_REDIST12%redist\ia32\compiler;
C:\Program Files (x86)\Intel\iCLS Client\;
C:\Program Files\Intel\iCLS Client\;
%SystemRoot%\system32;
%SystemRoot%;
%SystemRoot%\System32\Wbem;
%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;
C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;
C:\Program Files\Perforce;
C:\Program Files (x86)\Perforce;
C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;
C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;
C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;
%USERPROFILE%\.dnx\bin;
C:\Program Files\Microsoft DNX\Dnvm\;
C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;
C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\

I agree there is a PATH problem. I count 12 Intel directories before we even get to the system folders. Yikes! Another 4 after that (but probably not compiler related). This is on a new Windows 10 computer that is about a month old and still relatively clean.

Brian

[Steven_L_Intel1]

You need to call ifortvars.bat with the appropriate arguments (IA32 | Intel64) [VSxxxx] from your script, otherwise the VS files won't be in PATH.

You can remove the following entries:

C:\Program Files (x86)\Intel\Composer XE 2011 SP1\redist\intel64\mkl;
C:\Program Files (x86)\Intel\Composer XE 2011 SP1\redist\ia32\mkl;
%F_EM64T_REDIST12%redist\intel64\mpirt;
%F_EM64T_REDIST12%redist\intel64\compiler;
%F_IA32_REDIST12%redist\ia32\mpirt;
%F_IA32_REDIST12%redist\ia32\compiler;

[Brian_Francis]

Hi Steve,

Running ifortvars.bat resulted in a "Cannot determine the location of the VS Common Tools Folder". Took a while, but I found that the problem was that VC 10 vcvarsall.bat was failing because "C:\Windows\System32\reg.exe" was not being found. A proposed solution to that problem was to shorten the PATH, so I removed the 6 entries you suggested, rebooted, and now ifortvars.bat runs cleanly.

However, still getting the IFLangServicePack warning (5 times repeated) at the start of the build.

The PATH after calling ifortvars.bat is as follows:

C:\Program Files (x86)\Intel\Composer XE 2011 SP1\bin\ia32;
C:\Program Files (x86)\Intel\Composer XE 2011 SP1\redist\ia32\compiler;
C:\Program Files (x86)\Microsoft F#\v4.0\;
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VSTSDB\Deploy;
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\;
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN;
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools;
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319;
C:\WINDOWS\Microsoft.NET\Framework\v3.5;
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\VCPackages;
C:\Program Files (x86)\HTML Help Workshop;
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools;
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin;
C:\Program Files (x86)\Intel\Composer XE 2011 SP1\redist\ia32\mkl;
C:\Program Files (x86)\Intel\Composer XE 2011 SP1\redist\ia32\compiler;
C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64_win\mpirt;
C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64_win\compiler;
C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32_win\mpirt;
C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32_win\compiler;
C:\ProgramData\Oracle\Java\javapath;
C:\Program Files (x86)\Intel\iCLS Client\;
C:\Program Files\Intel\iCLS Client\;
C:\WINDOWS\system32;
C:\WINDOWS;
C:\WINDOWS\System32\Wbem;
C:\WINDOWS\System32\WindowsPowerShell\v1.0\;
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;
C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;
C:\Program Files\Perforce;
C:\Program Files (x86)\Perforce;
C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;
C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;
C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;
C:\WINDOWS\system32\config\systemprofile\.dnx\bin;
C:\Program Files\Microsoft DNX\Dnvm\;
C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;
C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;
Z:\src\utils\exec\Release;
C:\Program Files (x86)\Vim\vim74;
C:\cygwin\bin;
C:\Program Files (x86)\Intel\Composer XE 2011 SP1\redist\ia32\mpirt;

Thanks,

Brian.

[Steven_L_Intel1]

Interesting. Would you please add /log to the devenv command and show me the output?

[Brian_Francis]

Hi Steve,

I ran the following two commands and have attached the log files.

"C:\Program Files (x86)\Intel\Composer XE 2011 SP1\bin\ifortvars.bat" ia32 vs2010 > ifortvars.log
"%VC100_COMPILER%\Common7\IDE\DEVENV.EXE" tools\src\tools.sln  /build "Release|Win32" /out devenv.log

483515

483516

483516

[Steven_L_Intel1]

No, that's not what I asked for. I want you to add /log to the devenv,exe line. If you want to capture the output to a file, fine, but I need /log to appear on the command line.

[Brian_Francis]

Here you go.

483519

[Steven_L_Intel1]

Perfect - that's what I needed. Thanks - I will send this on to the developers. On the face of it it looks very much like that old problem. Issue ID is DPD200378469.

[fourreal]

If I understand this post correctly, this may be an issue with the 2016 release of the Fortran Composer.  I am running Intel Parallel Studio XE Update 4 Composer Edition on a build machine for TFS, and I am having the same issue as described in this post.  Whatever happened to this issue?  Is there an update to the Composer that fixes the problem?

[Kevin_D_Intel]

Yes, it appears perhaps to be related to the PSXE 2016 release. The OP indicates the message occurred when building using VS 2010 and Intel Fortran 12.0; however, the appearance coincided with installing VS2015 and Intel Parallel Studio XE 2016, and 16.0.0 appears in the message. In the OP's case it appears this did not impact a successful build.

There is no update within the internal tracking issue that Steve filed. I inquired w/Development about a current status.

If you want to collect the same /log details that Steve described earlier and attach that to a reply then I will add it to the internal tracking issue for our Developers to also investigate.

[fourreal]

Thanks for your response.  Here is the log file that resulted.  I would appreciate it if you add it to the internal tracking issue.

[Kevin_D_Intel]

Thank you for the log. I do not see the same set of errors in your log as the OP's log.

Do you see the same error as reported in post #1?

Based on your log, it looks like your message is of the form:

LegacySitePackage failed for package IFLangServicePackage:IFLangService: Object reference not set to an instance of an object; System.NullReferenceException: Object reference not set to an instance of an object Intel.Fortran.IFLangService.IFLangServicePackage

In the OP's case, the build appears successful. Is it successful in your case?

I think it is best to submit a separate report for your instance (see internal tracking id below) in case it does not share the same underlying cause. I referred our Developers to the earlier submitted internal id within the new tracking case. I will add any info from you for the questions above.

(Internal tracking id: DPD200417657 - Updated 03/26/2017 - This tracking id has been closed as a duplicate of the earlier cited id: DPD200378469)

[Kevin_D_Intel]

@fourreal - Development indicates the condition you experienced can happen after multiple installation/uninstallation of packages on one system.

They asked if you could remove the following directories and check if the condition disappears:

C:\Users\<user_name>\AppData\Local\Microsoft\VisualStudio
C:\Users\<user_name>\AppData\Roaming\Microsoft\VisualStudio