PDA

View Full Version : Suite install hangs when it is rerun



kmoulton
08-02-2012, 11:55 AM
Sometimes following a suite installation, the GUID(s) pertaining to the suite installation are not removed from the temp directory. (This seems to be more common on Win 7 x86, and XP)

If a GUID is not removed and it has an "_isxxxx" file (where x is some hexadecimal number), it will cause the install when it is run again to hang at the progress dialog.

This appears to happen because the install looks for this file to determine which dialog it should start on. It seems to look at "ISCurrentPage" to determine where it should start. Typically, "ISCurrentPage=InstallationProgress" .

I am currently getting around this issue by deleting the "_is*" files inside the first sub folder under the temp directory following the install.

This can be easily reproduced by cancelling during the progress dialog part of the install on Win 7 x86. However, it can also happen on a completed install, or an install that was interrupted and has issues.

Is this a known issue? Is there a better way to do this?

It appears that the suite technology expects this GUID to remain in place for a reboot, but that it should be removed after a normal install finishes.

joshstechnij
08-09-2012, 05:12 PM
The files used by a suite in the temp folder are indeed intended to support resuming a suite install if a reboot is necessary. These files should only be left on a machine in this case. In any other case (canceling, successfully completed install, or failed to install) these files should be removed as the suite process exits.

It is possible that these files are left behind that the suite is not exiting properly. Normally, if a log is generated when the suite is launched, one of the last log entries should be "State manager: cleaning up state info", assuming that a reboot was not requested in some manner (which would be noted earlier in the log and would also be indicated by the final system exit code also in the log). If the suite process was forcibly killed (through Task Manager or some other means) or crashed before it had a chance to cleanly exit, these files would be left behind and the behavior you are seeing when trying to relaunch can occur.

Note that if this does happen, the installer can actually be canceled after relaunching and exited normally (the finish page will be displayed after cancel is confirmed) which will also clean up the temporary files.

If possible, we would recommend trying to log a scenario where this occurs and provide the log along with reproduction steps which would allow us to try reproducing the issue.

kmoulton
08-28-2012, 01:16 PM
This appears to happen with Win 7 x86 and Win XP SP3. It does not happen with Win 7 x64, Newer workstation operating systems, or server operating systems.

For Example, here is the end of the debug log for Win 7 x 64:


8-28-2012[10:24:03 AM]: No ARP information provided in setup.xml, skipping register/unregister ARP info
8-28-2012[10:24:03 AM]: Engine: parcel operations completed, sending completed event to UI
8-28-2012[10:24:03 AM]: UI DLL: Get Install Mode: 0
8-28-2012[10:24:03 AM]: Engine: property 'ISInstallStatus' value now 'IDS_INSTALL_SUCCESS'
8-28-2012[10:24:03 AM]: Engine: property 'ISParcelStatus' value now ''
8-28-2012[10:24:03 AM]: Engine: property 'ISCurrentPage' value now 'PrerequisitesComplete'
8-28-2012[10:24:03 AM]: Engine: property 'ISCurrentPage' value now 'PrerequisitesComplete'
8-28-2012[10:36:37 AM]: UI DLL: Executing user custom action > {Open MAIN_INSTALL_EXE}
8-28-2012[10:36:37 AM]: UI DLL: Opening 'C:\Accounting\12.1.27.1\AccountingServer\Install\Main\setup.exe'
8-28-2012[10:36:37 AM]: UI DLL: Get Install Mode: 0
8-28-2012[10:36:37 AM]: Engine: property 'ISCurrentPage' value now 'PrerequisitesComplete'
8-28-2012[10:36:37 AM]: Engine: property 'ISCurrentPage' value now 'PrerequisitesComplete'
8-28-2012[10:36:38 AM]: Engine: property 'ISCurrentPage' value now 'PrerequisitesCanceled'
8-28-2012[10:36:38 AM]: UI DLL: Shutting down
8-28-2012[10:36:38 AM]: Engine: all operations completed, final status: 0
8-28-2012[10:36:38 AM]: Original exit status: 0x00000000, final exit status: 0x00000000
8-28-2012[10:36:38 AM]: State manager: cleaning up state info

Here is the end of the debug log for Win 7 x86:


8-28-2012[08:42:05 AM]: No ARP information provided in setup.xml, skipping register/unregister ARP info
8-28-2012[08:42:05 AM]: Engine: parcel operations completed, sending completed event to UI
8-28-2012[08:42:05 AM]: UI DLL: Get Install Mode: 0
8-28-2012[08:42:05 AM]: Engine: property 'ISInstallStatus' value now 'IDS_INSTALL_SUCCESS'
8-28-2012[08:42:05 AM]: Engine: property 'ISParcelStatus' value now ''
8-28-2012[08:42:05 AM]: Engine: property 'ISCurrentPage' value now 'PrerequisitesComplete'
8-28-2012[08:42:05 AM]: Engine: property 'ISCurrentPage' value now 'PrerequisitesComplete'
8-28-2012[08:44:57 AM]: UI DLL: Executing user custom action > {Open MAIN_INSTALL_EXE}
8-28-2012[08:44:57 AM]: UI DLL: Opening 'C:\SmokeTest\CurrentBuild\Accounting\AccountingServer\Install\Main\setup.exe'
8-28-2012[08:44:57 AM]: UI DLL: Get Install Mode: 0
8-28-2012[08:44:58 AM]: Engine: property 'ISCurrentPage' value now 'PrerequisitesComplete'
8-28-2012[08:44:58 AM]: Engine: property 'ISCurrentPage' value now 'PrerequisitesComplete'
8-28-2012[08:44:58 AM]: Engine: property 'ISCurrentPage' value now 'PrerequisitesCanceled'
8-28-2012[08:44:58 AM]: UI DLL: Shutting down

As you can see the final cleaning up of the State manager did not occur in Win 7 x86. This leads to the GUID being left around and it also appears to be causing the App Crash error dialog that is generated by the operating system to display. See Attached file.

Is there any way to force the State manager to clean up? I am currently deleting the GUID if it is left behind, but I have been unable to get rid of the App Crash error.

joshstechnij
08-30-2012, 03:33 PM
We've tried reproducing this crash on an XP and Windows 7 machine and have not seen any issues. Can you provide steps to reproduce this behavior or a sample project that reproduces the behavior (does this crash happen with any project or just one; if just one project, is that project using the suite billboard support)?

Regarding the state information, it is cleaned up by the suite engine after the suite has started to shut down. If something goes wrong before the cleanup runs, there won't be any way of getting it cleaned up automatically.

Karthika
09-26-2016, 01:37 PM
Sometimes following a suite installation, the GUID(s) pertaining to the suite installation are not removed from the temp directory. (This seems to be more common on Win 7 x86, and XP)

If a GUID is not removed and it has an "_isxxxx" file (where x is some hexadecimal number), it will cause the install when it is run again to hang at the progress dialog.

This appears to happen because the install looks for this file to determine which dialog it should start on. It seems to look at "ISCurrentPage" to determine where it should start. Typically, "ISCurrentPage=InstallationProgress" .

I am currently getting around this issue by deleting the "_is*" files inside the first sub folder under the temp directory following the install.

This can be easily reproduced by cancelling during the progress dialog part of the install on Win 7 x86. However, it can also happen on a completed install, or an install that was interrupted and has issues.

Is this a known issue? Is there a better way to do this?

It appears that the suite technology expects this GUID to remain in place for a reboot, but that it should be removed after a normal install finishes.

Even in WIndows 7 64 bit , we are getting this error, not always. But again, how exactly can we reproduce this issue?