Software Archive
Read-only legacy content
17061 Discussions

VTune beta remove fails, license key problem?

TimP
Honored Contributor III
759 Views

When I attempt to clean up my installation by running the beta cluster studio setup with remove option, it proceeds normally until it reaches the VTune phase, which quits with message:

Intel(R) Parallel Studio XE 2015 Beta Update 1 for Windows* OS Setup Wizard ended prematurely because of an error(s).
  Windows Installer failed to configure product:
    Error message: Error 1. Could not open key: 2.  System error 3.  Verify that you have sufficient access to that key, or contact your support personnel.  
    Error code: 1603
    Product code: 2F85EC1F-C9BE-424B-826C-581F8EFA760D
    Module name: ps_he_cli.msi

Is it possible I am not permitted to remove it on account of expiration of beta license?

I suppose it's also possible there is a block on my internet connection.

I found that I had copies of Download directory for several past installations, including VTune XE 2013 updates 15 and 17, in a non-standard location, which may have interfered with VTune updates.    I removed those Download folders by brute force.

The amplxe-tmp-Tim and amplxe-log-Tim folders were created during attempted removal, but ended up empty.

I am attempting to attach the pset log which appears to match the quoted product code.

0 Kudos
5 Replies
TimP
Honored Contributor III
759 Views

I paid for a copy of "Special Uninstaller" and used it to remove the beta and beta update 1 copies of VTune.  Then the parallel studio beta setup was able to report completion of uninstall.

Special Uninstaller doesn't see the copies of VTune updates 15 and 17 which the installer for the latter says are both installed.

0 Kudos
Feilong_H_Intel
Employee
759 Views

Hi Tim,

Thank you for your log file.  I'm escalating this issue to our installation team.  Will get back to you once I hear from them.

Thanks.

0 Kudos
TimP
Honored Contributor III
759 Views

I think "Special Uninstaller" followed by Microsoft Fix It may have taken care of the beta installation. 

Using "SU" to remove the XE 2013 copy of VTune doesn't alter the situation where updates 15 and 17 are reported still present and blocking their removal.

Microsoft Fix It says a product code is needed to work on the XE2013 installation.  How do we find out that code?

0 Kudos
Feilong_H_Intel
Employee
759 Views

Hi Tim,

A developer in engineering team replied me earlier.  He provided two solutions for you to uninstall your existing products, in case that uninstallation doesn't work somehow.  He also noted that, it is allowed to run installer for removal when a license is expired.

You could try one of the following solutions:

  1. Run Intel Parallel Studio XE 2015 Beta Update 1 (w_psf_b_2015.0.0.013) installer and try do repair.  After that re-run the installer to remove the product.
  2. Run Intel VTune Amplifier XE 2015 Beta Update 1 (w_amplxe_bu_2015.1.009)  and proceed with install option.  Product components shall be detected as installed so try to remove or add some component and finish installation.  After that rerun installer to remove the product.

If your VTune Amplifier XE 2013 Update 15 or 17 doesn't uninstall properly, you may also try one of the above solutions (with Update 15 or 17 installer).  Hope this helps.

If you want to pursue the IPS XE 2015 beta update 1 uninstallation issue, please provide all installer logs located under %temp%\pset_tmp_PSF2015_<username>.  The developer needs them to investigate the issue further.

Thanks.

0 Kudos
TimP
Honored Contributor III
759 Views

I believe I got this all cleared up.  I had to use "Special Uninstaller" followed by Microsoft Fix It to remove cleanly the parallel studio beta, which SU detected.  Then point SU at the VTune XE 2013 installation, and remove that.  Then run the Parallel Studio XE 2013 SP1 update 2 installer, which apparently I had used some time in the past ( and then updated to VTune update 17).  Having done all this, the current 2015 cluster studio was able to perform a full installation (which did not remove all the 2013 components which are expected to be disabled by installing 2015).

0 Kudos
Reply