Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!
26735 Discussions

Intel(R) Parallel Studio XE 2017 Update 4 Cluster Edition for Windows* Intel® Software Setup Assistant ended prematurely...

New Contributor I

Hi All,

The installation of Update 4 to PSXE 2017 failed with the message:

Intel(R) Parallel Studio XE 2017 Update 4 Cluster Edition for Windows* Intel® Software Setup Assistant ended prematurely because of an error(s).
  Windows Installer failed to configure product:
Error message: An error occured during the installation of assembly component 844EFBA7-1C24-93B2-A01F-C8B3B9A1E18E. HRESULT: 0x80073715.  
Error code: 1603
File name: amplxe_msvcrt_x64.msi

In the log file for amplxe_msvcrt_x64.msi I see:

MSI (s) (BC:CC) [15:28:14:795]: Assembly Error:The identities of the manifests are identical but their contents are different.
MSI (s) (BC:CC) [15:28:14:795]: Note: 1: 1935 2: {844EFBA7-1C24-93B2-A01F-C8B3B9A1E18E} 3: 0x80073715 4: IAssemblyCacheItem 5: Commit 6: Microsoft.VC80.CRT,type="win32",version="8.0.50727.6195",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64" 
MSI (s) (BC:CC) [15:28:14:795]: Assembly Error (sxs): Please look into Component Based Servicing Log located at %windir%\logs\cbs\cbs.log to get more diagnostic information.
MSI (s) (BC:CC) [15:28:14:795]: Product: Microsoft* Visual C++ x64 Runtime Libraries -- Error 1935. An error occured during the installation of assembly component {844EFBA7-1C24-93B2-A01F-C8B3B9A1E18E}. HRESULT: 0x80073715. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.VC80.CRT,type="win32",version="8.0.50727.6195",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64"

In the cbs.log i see errors:

2017-05-12 15:27:25, Error                 CSI    00000024@2017/5/12:19:27:25.575 (F) onecore\base\wcp\componentstore\csd_transact.cpp(1394): Error STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT originated in function CCSDirectTransaction::StageComponent expression: (null)
2017-05-12 15:27:26, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-05-12 15:27:26, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-05-12 15:28:14, Error                 CSI    00000025 (F) STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT #5052# from CCSDirectTransaction::OperateEnding at index 0 of 5 operations, disposition 2[gle=0xd015001c]
2017-05-12 15:28:14, Error                 CSI    00000026 (F) HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT) #4644# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x80073715]

But, that's about as far as I go.  Install is under Win 10 pro with VS Community 2015 Any ideas?  

0 Kudos
3 Replies

We apologize for installation failure. I do not have any information/ideas about the cause at this time. Thank you for the details you gathered. I will report the error and provide those to our Installation team.  I also anticipate they will want to inspect the PSXE specific installation logs from your system. Can you please look in your TEMP directory (in a file explorer window type %TEMP% in the address bar) for a folder with a name starting with pset_ and ending with your username. Inside there will be folders from recent install attempts - zip up the latest one corresponding to this PSXE 2017 Update 4 installation and send it to us. For privacy you can attach that to a private reply (use the Send Author a Message link) to me if you wish. Thank you.

(Internal tracking id: INST-4132)

New Contributor I

Thanks Kevin!

Since the rollback of update 4 install destroyed the existing installation, I uninstalled PSXE 2017 update 2 along with VS Community 2015.  I then upgraded to VS Community 2017 (including the needed "Desktop development with C++" component) and then installed Update 4 of PSXE 2017. This all went fine and it appears that VS Community 2017 is working as expected (although, I have yet to really test it).

Since the workstation I attempted the original update on has been around for a while with untold installs and uninstalls, I suspect that the problem lies in corruption problems on that machine, and unlikely a real problem with Update 4.  Consequently, I'm not planning on sending you the logs unless you really want them, but thank you for your help!!



Ok, thank you. I'm sorry to hear about the added work but am relieved to hear you have (or believe to) a working configuration. Let us know if you do have any other issues.