Problem installing latest MKL

[Gabriel_Toro]

I am using the latest Parallel Studio XE Professional Edition for Fortran Windows. I am using the Visual Studio 2013 Shell that comes with it (installed with an earlier version). When trying to install the latest update for the MKL librarier, I am getting the following message:

Installation can continue; however, Integration(s) in Microsoft Visual Studio* components willnot be installed because they require that a supported Microsoft Visual Studio* be installed. Refer to the Release Notes for a list of the required Microsoft Visual Studio*.

After I continue, nothing gets installed. What's going on? Do I need another version of Visual Studio? Is the earlier MKL still there or was it removed?

I would appreciate any suggestions.

[Kevin_D_Intel]

I'm not sure why you are receiving that message. That appears where the minimum Microsoft Visual Studio prerequisite has not been met; however, VS 2013 Shell should satisfy the internal check.

What “earlier version” did you install when you installed VS 2013 Shell?
And just to confirm, you installed VS2013 Shell, the Fortran compiler and the MKL from this “earlier version”, correct?
When you say you are “using the latest”, does that mean Parallel Studio XE 2017 Update 2?

As the messages says, you can continue the installation without satisfying the minimum VS requirement, but it should result in installation of elements from the package.

When you say “nothing gets installed”, where are you looking when making that judgment?

I don’t know what earlier versions of PSXE you had installed, but by default the installation does not uninstall previous installed components unless such selections are made under the customize installation menu.

Multiple versions of a major release install side-by-side into versioned directories, for example:
 
PSXE 2017 Update 1: C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2017.1.143\windows\mkl
PSXE 2017 Update 2: C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2017.2.187\windows\mkl

We can try inspecting installation logs if you want to provide those. Those are found in the %TEMP% directory (just drop %TEMP% in the file explorer address bar) under a folder with a name starting with pset_ and ending with your username. If you will zip up the folders for install attempts send those then I will forward them to me then I can forward them to installation Development team.

[Gabriel_Toro]

Kevin,

Thanks for your response. I will try to answer your questions to the extent I can (in bold text).

What “earlier version” did you install when you installed VS 2013 Shell?   Not sure. I have been using PSXE for several years, installing every update that comes around.
And just to confirm, you installed VS2013 Shell, the Fortran compiler and the MKL from this “earlier version”, correct? Yes. I install or update everything.
When you say you are “using the latest”, does that mean Parallel Studio XE 2017 Update 2?  Yes

As the messages says, you can continue the installation without satisfying the minimum VS requirement, but it should result in installation of elements from the package.

When you say “nothing gets installed”, where are you looking when making that judgment?

Here is the sequence I get from the MKL Update 2 installation wizard:

1. The Integration(s) in Microsoft Visual Studio* components cannot be installed.
Installation can continue; however, Integration(s) in Microsoft Visual Studio* components will not be installed because they require that a supported Microsoft Visual Studio* be installed. Refer to the Release Notes for a list of the required Microsoft Visual Studio*.

2. No components selected to install (and Install button is grayed out). Pressed Cancel.

3. Intel(R) Math Kernel Library 2017 Update 2 for Windows* setup was interrupted. To install this program at a later time, please run the installation again. Click the Finish button to exit the Intel® Software Setup Assistant.

I don’t know what earlier versions of PSXE you had installed, but by default the installation does not uninstall previous installed components unless such selections are made under the customize installation menu.

Multiple versions of a major release install side-by-side into versioned directories, for example:
 
PSXE 2017 Update 1: C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2017.1.143\windows\mkl
PSXE 2017 Update 2: C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2017.2.187\windows\mkl

I see both folders exist, along with the 2016 versions. More surprisingly C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2017.2.187\windows\mkl contains more than 2000 files, occupying ~1 GB 

We can try inspecting installation logs if you want to provide those. Those are found in the %TEMP% directory (just drop %TEMP% in the file explorer address bar) under a folder with a name starting with pset_ and ending with your username. If you will zip up the folders for install attempts send those then I will forward them to me then I can forward them to installation Development team.  Doing "C:\>dir /s pset_*"  does not shown any directory with that name. Any other idea where those logs may be?

It looks like I am not the only person having trouble with Update 2 (and I had similar trouble installing other tools [Inspector?], which I have not mentioned until now). Will a new Update 2 be released?  Is update 2 being pulled?  Or maybe these issues should be resolved with tech support instead of using this form.

Thanks,

Gabriel

[Kevin_D_Intel]

Sounds like you have done some upgrades already and MKL 2017 Update 2 is already installed. Prior to trying this MKL specific update, had you already done an upgrade installation for PSXE 2017 Update 2 earlier?

How are you launching these upgrades?  Are you downloading files from the IRC or are using the Intel Software Manager to start these upgrades?

In the command-prompt window where you noted typing "dir /s", can you type the following command and paste the output into a reply: dir "C:\Program Files (x86)\IntelSWTools"

In that same command-prompt window, to get to the installation logs, you need to include %TEMP% like this: dir /s %TEMP%\pset_*

[Gabriel_Toro]

Kevin,

Thanks for the response. I had installed PSXE 2017 Update 2 from the Software Manager right before this happened.

These updates I first tried to install using Software Manager. After it did not work, I tried downloading using the links in the email announcement for Update 2.

Here is the screen output from the 1st dir command

 Directory of C:\Program Files (x86)\IntelSWTools

03/01/2017  02:23 PM    <DIR>          .
03/01/2017  02:23 PM    <DIR>          ..
02/24/2017  12:39 PM    <SYMLINKD>     Advisor
02/24/2017  12:39 PM    <DIR>          Advisor 2017
02/24/2017  11:57 AM    <SYMLINKD>     compilers_and_libraries [C:\Program Files (x86)\IntelSWTools\compilers_and_librar
ies_2017]
08/26/2015  01:24 PM    <DIR>          compilers_and_libraries_2016
08/26/2015  01:24 PM    <DIR>          compilers_and_libraries_2016.0.110
02/24/2017  12:36 PM    <DIR>          compilers_and_libraries_2017
09/06/2016  08:17 AM    <DIR>          compilers_and_libraries_2017.0.109
11/03/2016  06:55 AM    <DIR>          compilers_and_libraries_2017.1.143
02/24/2017  12:33 PM    <DIR>          compilers_and_libraries_2017.2.187
11/03/2016  06:53 AM    <DIR>          documentation_2017
02/24/2017  12:24 PM    <DIR>          ide_support_2017
02/24/2017  11:58 AM    <DIR>          imb
02/24/2017  12:38 PM    <SYMLINKD>     Inspector
02/24/2017  12:38 PM    <DIR>          Inspector 2017
02/24/2017  11:58 AM    <DIR>          mpi
10/16/2016  04:00 PM    <DIR>          parallel_studio_xe_2016.0.041
02/24/2017  11:58 AM    <SYMLINKD>     parallel_studio_xe_2017 [C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2
017.2.046]
10/28/2016  05:30 PM    <DIR>          parallel_studio_xe_2017.0.036
11/03/2016  06:56 AM    <DIR>          parallel_studio_xe_2017.1.040
02/24/2017  11:58 AM    <DIR>          parallel_studio_xe_2017.2.046
02/20/2017  10:19 AM             2,276 Performance Snapshot.lnk
02/24/2017  11:57 AM    <DIR>          samples_2017
02/20/2017  10:19 AM    <SYMLINKD>     VTune Amplifier XE

02/20/2017  10:19 AM    <DIR>          VTune Amplifier XE 2017
               1 File(s)          2,276 bytes
              25 Dir(s)  146,473,402,368 bytes free

The 2nd dir commmand found the log file. Strange because I had used dir/s from c:\). Attached is a zip file containing the contents of pset_*.

Thanks again,

Gabriel

[Kevin_D_Intel]

Thank you for the logs and directory output. From looking at those, and based on the content of the directory you showed in your previous post, it appears you successfully installed the Intel Parallel Studio XE 2017 Update 2 Professional Edition for Fortran Windows which includes the Fortran compiler, MKL, and analysis tools (Inspector, Advisor, VTune). Therefore, you already have everything of interest from Update 2 installed and tools should be ready for use. This also corroborates why the MKL installation reports there are no components to update and that you mention having problems installing other products like Advisor. Also given the parallel_studio_xe_2017 symlink shown above, your current default is the Update 2 release.

Have you tried to build an app that uses MKL to know whether that's working?

If you build under Visual Studio, you can check the default compiler under Tools > Options > Intel Compilers and Tools >  Visual Fortran > Compilers. Within the Selected Compiler selection, the version should be Intel Visual Fortran Compiler 17.0.2.187

Have you tried any of the performance analysis tools and checked their Help > About (Details tab) for versions?

As for the behavior of the MKL specific installer, the logs confirm your initial report about warning of meeting the minimum VS requirement which should not be true with VS 2013 Shell installed. I also just confirmed the same happens on my system so I'll follow this reply by submitting a defect report to our MKL installation developers.

(Internal tracking id: DPD200418419)

(Resolution Update on 03/17/2016): The issue was closed as not a defect.

[Kevin_D_Intel]

Development clarified the minimum VS requirement pre-requisite warning from the MKL installer. It occurs because the stand-alone MKL includes the C++ integrations which are not compatible/usable with the VS 2013 Shell that is detected/installed. It can be safely ignored in your scenario.