This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
I combed through the logs and saw a myriad of issues. Amongst them was the following:
Note: 1: 2205 2: 3: MsiAssembly
MSI (s) (04:E4) [06:42:02:932]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ?
MSI (s) (04:E4) [06:42:18:595]: Disallowing installation of component: {A2F25182-0BE0-410A-A9EB-C0CC2260EF3F} since the same component with higher versioned keyfile exists
That would be the 1603 error.
Because this was a re-install, it looked like everything did not get cleaned out with the removal tool based on that msg. I decided to just install the client to whittle down the logs and see if the other issues were just red-herrings.
The Client install failed. Went to the logs. I noticed that the old registry looked to be deleted and i now still had file mis-matches.
I checked the environment variables and sure enough, i had typo'd the Temp file name when i was trying make sure it was in synch with what existed.
After that, the client installed fine, then the template, and now everything else.
It appears that when installing 8.5.3 as a bundle (either client and template together (or more)) the registry does not get cleared.
Single-threaded installs were the key to successful re-installation.
Feedback response number WEBB96NHKT created by ~Wei Lopniter on 04/11/2013