Uninstall hangs on ReadToRemove dialog

[dracan]

Hi. In my UI Sequence, I've added the ReadyToRemove dialog (I've put it just before the PatchWelcome). I set the condition to REMOVE="ALL". This works fine, except for when the dialogbox first appears, it hangs for a couple of minutes. I've added a tickbox to that dialog, and I can't select it or do anything else until it's finished whatever it's doing during the hang.

I've tried uninstalling via the command line so I can generate a log file, and the last thing it shows before hanging is:

Action ended 16:47:26: MigrateFeatureStates. Return value 0.

MSI (c) (F0:E8) [16:47:26:216]: Doing action: ReadyToRemove

Action 16:47:26: ReadyToRemove.

Action start 16:47:26: ReadyToRemove.

Thanks for any help with this,
Dan.

[dracan]

Actually, this is probably a more helpful log:

Action ended 11:01:27: MigrateFeatureStates. Return value 0.

MSI (c) (10:74) [11:01:27:529]: Doing action: ReadyToRemove

Action 11:01:27: ReadyToRemove.

Action start 11:01:27: ReadyToRemove.
**********
Info 2898.For MSSansBold8 textstyle, the system created a 'Tahoma' font, in 0 character set.

Info 2898.For MSSWhiteSerif8 textstyle, the system created a 'Tahoma' font, in 0 character set.

Action 11:01:27: ReadyToRemove. Dialog created

MSI (c) (10:20) [11:01:27:607]: Note: 1: 2205 2: 3: _RemoveFilePath

Action 11:01:30: CancelSetup. Dialog created

MSI (c) (10:20) [11:01:31:545]: Doing action: ISSetupFilesCleanup

Action 11:01:31: ISSetupFilesCleanup.

Action start 11:01:31: ISSetupFilesCleanup.

MSI (c) (10:20) [11:01:31:545]: Creating MSIHANDLE (10) of type 790542 for thread 11296

MSI (c) (10:24) [11:01:31:545]: Invoking remote custom action. DLL: C:\DOCUME~1\DAN~1.CLA\LOCALS~1\Temp\MSI398.tmp, Entrypoint: SFCleanupEx

MSI (c) (10:24) [11:01:31:591]: Closing MSIHANDLE (10) of type 790542 for thread 11296

MSI (c) (10:20) [11:03:08:778]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'.

MSI (c) (10:20) [11:03:08:778]: Note: 1: 2205 2: 3: BindImage

MSI (c) (10:20) [11:03:08:778]: Note: 1: 2205 2: 3: ProgId

MSI (c) (10:20) [11:03:08:778]: Note: 1: 2205 2: 3: PublishComponent

MSI (c) (10:20) [11:03:08:778]: Note: 1: 2205 2: 3: SelfReg

MSI (c) (10:20) [11:03:08:778]: Note: 1: 2205 2: 3: Extension

MSI (c) (10:20) [11:03:08:778]: Note: 1: 2205 2: 3: Font

MSI (c) (10:20) [11:03:08:778]: Note: 1: 2205 2: 3: Class

MSI (c) (10:20) [11:03:08:793]: Note: 1: 2727 2:

Action ended 11:03:08: ISSetupFilesCleanup. Return value 1.

Action ended 11:03:08: ReadyToRemove. Return value 2.

Note that I've put the "**********" to indicate where the log file ends whilst the hang is happening. The rest is written after the hang finishes. Note the times though - so the position of the "**********" may just be a log file flushing thing.

So it looks like the pause is in the SFCleanupEx dll function?

[Vincent_Kuo]

Hi,

I am facing the same problem too, Any help will be appreciated...thanks!

Best Regards,
Vincent

[dracan]

Unfortunately, I didn't get anywhere with this (even after opening an Installshield support ticket). We basically had to ship our software with that hang :mad:

[MichaelU]

Yeah, on a quick look at the log snipped you posted (which I'm not certain is a verbose log - those should help somewhat more), it looks likely that the hang is in Costing. As the Windows Installer engine performs costing as a nearly black box to us, it's hard to influence it, other than to cut back on any superfluous setup complexities.

[CODE]MSI (c) (10:24) [11:01:31:591]: Closing MSIHANDLE (10) of type 790542 for thread 11296

MSI (c) (10:20) [11:03:08:778]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'.[/CODE]