We created an InstallShield .wil log file and ran this through the InstallShield log analyzer to generate both a detailed.mht and summary.mht report file. Also, we captured the setupai.log file. These were then zipped (along with .ism file) and placed at http://www.gwinst.com/i4xx/InstallLogs (right click save as on "FailedInstallLog-4-10-2011.zip"), and can be viewed by anyone interested in this.
Our question is, eactly what is causing the installation to fail and show this alert?
We have a clue, shown below, yet do not understand log files well enough to know if this is related to the problem. The below .wil snippet talks about component 'inet_usb_installer_32bitOsCpu'. However, the installshield .ism file has "Not VersionNt64" set as the condition on this component. And we are on a 64bit (windows 7) computer, so we would not expect activity from this component.
09684: (Unknown): DIFXAPP: ENTER: CleanupOnSuccess()
09685: (Unknown): DIFXAPP: 'Component' is 'inet_usb_installer_32bitOsCpu'
09686: (Unknown): DIFXAPP: 'ComponentId' is {..5927CEE4D36D}
09687: (Unknown): DIFXAPP: ERROR 0x2 encountered while opening
DIFxApp key for component '{..5927CEE4D36D}'
09688: (Unknown): DIFXAPP: RETURN: CleanupOnSuccess() 1603 (0x643)
09689: (Unknown): CustomAction MsiCleanupOnSuccess returned actual
error code 1603 (note this may not be 100% accurate if translation
happened inside sandbox)
Our fundamental problem is we are not very good at reading log files.
p.s. If it is not obvious what is happening here, and it takes someone some time to figure this out, we would be willing to pay them to help us.
Edited by gwein, 11 April 2011 - 06:13.
