This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- long pause on finish dialog when patch completes
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 18, 2008
01:18 PM
long pause on finish dialog when patch completes
I have a problem when I install a patch. The patch installs and then the finish dialog draws on the screen. However, the dialog is unresponsive for ~30 seconds to 1 min. Then after the dialog is responsive the user can click on the finish button but there is another delay of ~30 sec to 2min.
The MSI log file does not indicate any processes running at this time.
Note that Action start 13:14:20: SetupCompleteSuccess. starts at 13:14:20. The dialog draws shortly after that. Yet is not until 13:15:59 (according to QA) that the hour glass goes away indicating that the user can interact with the dialog.
The QA person clicked on FINISH at 13:16:00 and the hour glass ran until 13:17:55 when it finished and exited correctly.
The patch is roughly 40MB. All files are patched correctly and the application behaves correctly.
Any ideas on what I need to check to determine what is causing the delay? Is there anything I can do about this?
The MSI log file does not indicate any processes running at this time.
Action start 13:14:20: ISSetupFilesCleanup.
MSI (c) (00:18) [13:14:20:668]: Transforming table Binary.
MSI (c) (00:18) [13:14:20:668]: Transforming table Binary.
MSI (c) (00:18) [13:14:20:668]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (00:F0) [13:14:20:684]: Invoking remote custom action. DLL: C:\DOCUME~1\DEMO~1.EAR\LOCALS~1\Temp\MSI31.tmp, Entrypoint: SFCleanupEx
1: Deleting Support File: C:\DOCUME~1\DEMO~1.EAR\LOCALS~1\Temp\{AEB95804-A937-49E6-940A-37A606C16D5D}\FFControl.dll
1: Deleting Support File: C:\DOCUME~1\DEMO~1.EAR\LOCALS~1\Temp\{AEB95804-A937-49E6-940A-37A606C16D5D}\registration.dll
1: Deleting Support File: C:\DOCUME~1\DEMO~1.EAR\LOCALS~1\Temp\{AEB95804-A937-49E6-940A-37A606C16D5D}\SHLWAPI.DLL
1: Deleting Support File: C:\DOCUME~1\DEMO~1.EAR\LOCALS~1\Temp\{AEB95804-A937-49E6-940A-37A606C16D5D}\SimpleSNVD.dll
1: Deleting Support File: C:\DOCUME~1\DEMO~1.EAR\LOCALS~1\Temp\{AEB95804-A937-49E6-940A-37A606C16D5D}\WININET.DLL
Action ended 13:14:20: ISSetupFilesCleanup. Return value 1.
MSI (c) (00:18) [13:14:20:700]: Doing action: SetupCompleteSuccess
Action 13:14:20: SetupCompleteSuccess.
Action start 13:14:20: SetupCompleteSuccess.
MSI (c) (00:04) [13:14:20:700]: Transforming table Binary.
MSI (c) (00:04) [13:14:20:700]: Transforming table Binary.
MSI (c) (00:04) [13:14:20:700]: Note: 1: 2262 2: Binary 3: -2147287038
Action 13:14:20: SetupCompleteSuccess. Dialog created
MSI (c) (00:04) [13:16:13:162]: Doing action: ISSetupFilesCleanup
Action 13:16:13: ISSetupFilesCleanup.
Action start 13:16:13: ISSetupFilesCleanup.
MSI (c) (00:04) [13:16:13:193]: Transforming table Binary.
MSI (c) (00:04) [13:16:13:193]: Transforming table Binary.
MSI (c) (00:04) [13:16:13:193]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (00:B0) [13:16:13:209]: Invoking remote custom action. DLL: C:\DOCUME~1\DEMO~1.EAR\LOCALS~1\Temp\MSI32.tmp, Entrypoint: SFCleanupEx
MSI (c) (00:04) [13:17:54:429]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'.
MSI (c) (00:04) [13:17:54:429]: Note: 1: 2205 2: 3: BindImage
MSI (c) (00:04) [13:17:54:429]: Note: 1: 2205 2: 3: PublishComponent
MSI (c) (00:04) [13:17:54:429]: Note: 1: 2205 2: 3: SelfReg
MSI (c) (00:04) [13:17:54:429]: Note: 1: 2205 2: 3: Font
MSI (c) (00:04) [13:17:54:461]: Note: 1: 2727 2:
Action ended 13:17:54: ISSetupFilesCleanup. Return value 1.
Action ended 13:17:54: SetupCompleteSuccess. Return value 2.
Action ended 13:17:54: INSTALL. Return value 1.
Note that Action start 13:14:20: SetupCompleteSuccess. starts at 13:14:20. The dialog draws shortly after that. Yet is not until 13:15:59 (according to QA) that the hour glass goes away indicating that the user can interact with the dialog.
The QA person clicked on FINISH at 13:16:00 and the hour glass ran until 13:17:55 when it finished and exited correctly.
The patch is roughly 40MB. All files are patched correctly and the application behaves correctly.
Any ideas on what I need to check to determine what is causing the delay? Is there anything I can do about this?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 23, 2008
08:19 AM
Any ideas? Is there something else I can do to get more information from the log to help solve this issue?
I have the registry entries setup to enable logging with 'voicewarmup' value.
I have the registry entries setup to enable logging with 'voicewarmup' value.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 23, 2008
11:04 AM
You could try turning on the MSI debug policy and use DebugView from SysInternals to see if any additional information can be seen (use 7 for the debug policy value instead of 2). If that doesn't yield any results, the next step would likely be to start removing resources from the project to see if anything in particular causes the behavior to occur. You may try starting with removing any support files in the project. The support files cleanup does run a loop to remove any files in SUPPORTDIR, and while this should not ordinarily be an issue, removing the files from the project can at least eliminate it as a possible cause.
