Can't compile for x64 anymore after applying Parallel Studio 2016 update 1

[bronxzv]

I was succesfully building several projects with Intel C++ 16.0 Build 10250815 (installed with parallel_studio_xe_2016_setup.exe) for both Win32 and x64 target platforms.

After upgrading to the Intel C++ compiler 16.0 Build 20151021 (installed with parallel_studio_xe_2016_update1_setup.exe) I can't compile for x64 targets anymore (Win32 is all OK though).

I get this error message for all files I tried to compile for an x64 platform (as defined in the Configuration Manager):

>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\PlatformToolsets\Intel C++ Compiler 16.0\Microsoft.Cp.x64.Intel C++ Compiler 16.0.targets(344,5): error MSB6006: "icl.exe" exited with code -1073741819.

I'll be glad to know if there is a known fix / workaround for this issue, the only one I see ATM will be to revert back to the previous version (Parallel Studio 2016 initial release)

[TimP]

Intel C++ depends on a Visual Studio and Microsoft SDK installation. 

I would have thought, if you were using VS2010, that it would remain configured when you upgrade ICL, but I think there you did require an X64 installation option within the C++ support option, regardless of 32- or 64-bit Windows.  I don't remember if you needed Administrator priviledge to work with VS2010.

I think VS2012 Pro and VS2013 Community did automatically configure C++ X64 when installed on 64-bit Windows.  Again, one would hope that upgrading Intel C++ doesn't require a change.

VS2015 has changed several times; if you use that (Community, Pro, or Enterprise required), you should assure that you are upgraded to 2015.1 menu, including C++ and 10240 SDK (if so, those will show in the modify menu you can reach from Windows Add/Remove programs).  There was probably some adjustment in psxe 16.0.1 to accommodate or require updates in VS2015 if you are using that.

It seems that MSB6006 might be caused by several things; problem reading license file, or problem accessing your file system (permission, file busy).  So there a several details you may need to fill in if it continues to be a problem.

[bronxzv]

Tim P. wrote:

Intel C++ depends on a Visual Studio and Microsoft SDK installation. 

I would have thought, if you were using VS2010, that it would remain configured when you upgrade ICL,

I'm using VS2010 and it worked well for all my updates of Parallel Studio 2015 from the initial release to update #5.

It also works again well when I revert back to Parallel Studio 2016 initial release, after uninstalling 2016 update #1

Tim P. wrote:

So there a several details you may need to fill in if it continues to be a problem.

I'm working on a Windows 10 Pro (64-bit) PC (Core i7 6700, 16 GB RAM) with these packages installed:

Microsoft Visual Studio 2010
Version 10.0.40219.1 SP1Rel
Microsoft .NET Framework
Version 4.6.01038 SP1Rel

Installed Version: Professional

Microsoft Office Developer Tools   01018-587-3959691-70031
Microsoft Office Developer Tools

Microsoft Visual Basic 2010   01018-587-3959691-70031
Microsoft Visual Basic 2010

Microsoft Visual C# 2010   01018-587-3959691-70031
Microsoft Visual C# 2010

Microsoft Visual C++ 2010   01018-587-3959691-70031
Microsoft Visual C++ 2010

Microsoft Visual F# 2010   01018-587-3959691-70031
Microsoft Visual F# 2010

Microsoft Visual Studio 2010 Team Explorer   01018-587-3959691-70031
Microsoft Visual Studio 2010 Team Explorer

Microsoft Visual Web Developer 2010   01018-587-3959691-70031
Microsoft Visual Web Developer 2010

Critical Update for Microsoft Visual Studio 2010 Professional - ENU (KB2938807)   KB2938807
This critical update is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this critical update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2938807.

Crystal Reports Templates for Microsoft Visual Studio 2010  
Crystal Reports Templates for Microsoft Visual Studio 2010

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2529927)   KB2529927
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2529927.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2542054)   KB2542054
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2542054.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2548139)   KB2548139
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2548139.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2549864)   KB2549864
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2549864.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2635973)   KB2635973
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2635973.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2890573)   KB2890573
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2890573.

Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB3002340)   KB3002340
This hotfix is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/3002340.

Intel® Advisor XE 2016 Update 1  
Intel® Advisor XE 2016 Update 1, (build 435351), Copyright © 2009-2015 Intel Corporation. All rights reserved.

Intel® Inspector XE 2016 Update 1  
Intel® Inspector XE 2016 Update 1, (build 434495), Copyright © 2009-2015 Intel Corporation. All rights reserved.

Intel® Parallel Studio XE 2016 Composer Edition for C++ Windows*   Package ID: w_comp_lib_2016.1.146
Intel® Parallel Studio XE 2016 Update 1 Composer Edition for C++ Windows* Integration for Microsoft* Visual Studio* 2010, Version 16.0.98.2010, Copyright © 2002-2015 Intel Corporation. All rights reserved.
* Other names and brands may be claimed as the property of others.

Intel® VTune™ Amplifier XE 2016 Update 1  
Intel® VTune™ Amplifier XE 2016 Update 1, (build 434111), Copyright © 2009-2015 Intel Corporation. All rights reserved.

Microsoft Visual Studio 2010 Professional - ENU Service Pack 1 (KB983509)   KB983509
This service pack is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/983509.

Microsoft Visual Studio 2010 SharePoint Developer Tools   10.0.40219
Microsoft Visual Studio 2010 SharePoint Developer Tools

Security Update for Microsoft Visual Studio 2010 Professional - ENU (KB2644980)   KB2644980
This security update is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this security update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2644980.

Security Update for Microsoft Visual Studio 2010 Professional - ENU (KB2645410)   KB2645410
This security update is for Microsoft Visual Studio 2010 Professional - ENU.
If you later install a more recent service pack, this security update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2645410.

[mecej4]

MSBuild wrote:
>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\PlatformToolsets\Intel C++ Compiler 16.0\Microsoft.Cp.x64.Intel C++ Compiler 16.0.targets(344,5): error MSB6006: "icl.exe" exited with code -1073741819.

Among other things, MsBuild seems to be interpreting a 32-bit return code from icl.exe as a 64-bit value; the decimal error code (-1073741819), expressed in hex, is FFFFFFFF C0000005. The real return code is probably the well-known C0000005 (access-violation), and the FFFFFFFF is an artifact of sign-bit extension from 32 to 64 bits. You might learn a bit more about the error if you issued the command to ICL directly and looked at the output.

[bronxzv]

mecej4 wrote:

Among other things, MsBuild seems to be interpreting a 32-bit return code from icl.exe as a 64-bit value; the decimal error code (-1073741819), expressed in hex, is FFFFFFFF C0000005. The real return code is probably the well-known C0000005 (access-violation), and the FFFFFFFF is an artifact of sign-bit extension from 32 to 64 bits. 

Hi mecej4,

Thank you for your analysis, indeed it looks like an access-voliation error (i.e. application crash) since no human readable diagnostic is reported although ICL features such messages for a lot of different cases

mecej4 wrote:

You might learn a bit more about the error if you issued the command to ICL directly and looked at the output.

I tried to call ICL 64-bit directly (its path on my system is C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2016.1.146\windows\bin\intel64\icl.exe)

and I got this error "icl: error #10114: Microsoft Visual C++ not found in path"

It's not clear for me (from the command line in VC++ and from icl /help) how to fix this issue.

I have also tried to start a simple project from scratch and it's the same problem, all OK with 32-bit ICL and the 0xC0000005 error with 64-bit ICL.

If someone experience the same issue I'll be glad to hear about it.

Now, since I have to do useful work again next week I have reverted back to the previous release (Build 21050815) and it works well.