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

Installation Problems with Parallel Studio XE 2016

Han_L_1
Beginner
2,032 Views

The installation program (setup.exe) terminates itself without finishing the installation. That is to say the Intel installation program never gets to the welcome page. I have attached logs for examination. Please send aid. 

0 Kudos
9 Replies
Kevin_D_Intel
Employee
2,032 Views

Sorry to hear you experienced installation issues. We will look at the attached logs and let you know what actions to take. Stay tuned....

0 Kudos
TimP
Honored Contributor III
2,032 Views

It seems to my uneducated glance that it thinks you are running on a 32-bit Windows OS but it can't determine the version.  Is it a supported OS according to https://software.intel.com/sites/default/files/managed/52/53/PSXE-2016-beta-releasenotes.pdf ?  As it implies there, to run on Windows XP you apparently must drop back to psxe 2015.  Maybe some of the components of 2016 can be installed individually alongside 2015.

If you have the Cluster edition, the MPI in 2016 will not support 32-bit Windows, even a current one, as documented in that reference.

0 Kudos
Kevin_D_Intel
Employee
2,032 Views

Your case involves a WMI failure that I just learned occurs when the underlying OS is not supported. The error signature in your log suggests you may be running Windows XP. The earlier similar report is here, https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/594464

If you are using Windows XP or another unsupported version then you need to upgrade to a supported version of Windows* to install the Parallel Studio XE 2016 release. Please refer to the Intel Visual Fortran Compiler 16.0 for Windows* Release Notes for Intel Parallel Studio XE 2016 for details on the supported versions of  Windows*.

Our apologies the confusing and inconvenience

0 Kudos
Han_L_1
Beginner
2,032 Views

My situation is very similar to the one you linked, but I receive no feedback from the program at all. Not even an installation failure message. My operating system is Windows 8.1 and runs on a x64 architecture. I also noticed that when the program queries to determine the system specifics the query fails, but I don't know why. 

0 Kudos
Kevin_D_Intel
Employee
2,032 Views

Thank you for the clarification about your OS. That's valuable information. I will update the Installation Developer and let you know what I hear back.

(Internal tracking id: DPD200375682)

(Resolution Update on 12/01/2015): This defect is fixed in the Intel® Parallel Studio XE 2016 Update 1 Release (PSXE 2016.1.051 / CnL 2016.1.146 - Windows)

0 Kudos
TimP
Honored Contributor III
2,032 Views

The VTune support team started another round of working with me in attempting to install 2016 on win8.1.  It turns out there are several blocking issues which didn't interfere with earlier versions, but cause the setup to fail when installing any combination including VTune.  Buried in the 24MB log there are references to stale psxe 2015 components.  Those references may be inaccurate; for example, the indication that 2015 update 2 was still installed was triggered by remaining uninstalled .msi from 2013 and 2015 beta.  Then stale 2015 update 1 .msi produced an indication of inability to clean up 2015.  The most recent XE2015 versions appear to uninstall cleanly from Add/Remove Programs, but it will be difficult to see older bad entries when current ones are active.

Some of these can be resolved by using file explorer to remove stale .msi components from \windows\installer\ :

Enter e.g. \windows\installer as text in the folder bar.  This gets around \installer being hidden.

Preferably, use View Add Columns  to add authors and subject .  Subject will help you know which entries authored by Intel are relevant to psxe.  If you blow away an Intel driver by mistake, the Intel Driver Update Utility can help you recover.

In the search box, try subject: vtune and subject: XE 2015 etc. (look for additional entries similar to the ones you find)

for any stale .msi which comes up, you can try to uninstall (right click on the date).  Chances are it is already uninstalled, so you must remove it.

No one has explained why this problem is so bad with the combination of win8.1 and psxe 2016, when it doesn't interfere with earlier versions.  Even with win10 it seems easier to recover.  Not all psxe 2016 components work on Win10; some improvements may come in 2016 update 1. Then I may look for the win10 upgrade from win8 if it remains available.

Another group of installation issues you will see discussed in other threads has to do with updating Intel and Microsoft tools leaving stale entries in System Environment Variables path.  In those cases, the setup should complete, but you will need to remove duplicate and obsoleted path entries in order to run.  None of the install/uninstall scripts appear to clean up these entries.

 

0 Kudos
Kevin_D_Intel
Employee
2,032 Views

@Kirito - The installation developer who analyzed your logs says your case still relates to the WMI service and the behavior you experienced relates to an issue with that service on your system. He advised referring to the following article about the WMI service diagnostic and solutions how to resolve issues with that: https://technet.microsoft.com/en-us/library/ff406382.aspx

On this page, as advised in the opening, it is recommend you run the WMI Diagnosis Utility first.

Once it appears the WMI service is functioning, then can re-try the Intel Compiler installation again.

Keep me posted and let me know if you have any questions or further problems.

0 Kudos
TimP
Honored Contributor III
2,032 Views

Certain Windows maintenance utilities, such as System Mechanic, perform routine automatic WMI repairs.  This happens nearly as frequently as (but quicker than) registry repairs.
 

0 Kudos
Kevin_D_Intel
Employee
2,032 Views

@Kirito - If you have not already resolved the WMI service matter on your system and installed Parallel Studio XE 2016 then you could instead consider installing the Parallel Studio XE 2016 Update 1 release. The Update 1 installation was altered to avoid problems experienced in the initial release involving the dependency on the result of the WMI request. In Update 1, the installer can now continue even in the case of a non-working WMI service.

0 Kudos
Reply