Endless "Computing space requirements..."
Updated: 24 Sep 2010 | 11 comments
Hi experts!
A customer comlains that our setup stucks "for ages" during "Computing space requirements...". For it's an upgrade the UI only shows two dialogs (Welcome, Start Installation). The massive delay occurs after the Start Installation dialog has been left.
According to Windows Installer log a massive delay occured between two WiseCleanup actions. Any ideas how to interpret it resp. how to better analyze it?
Aktion 10:33:24: Welcome_Dialog. Dialog created Aktion 10:33:33: ApplicationRunning. Dialog created MSI (c) (9C:50) [10:33:37:976]: Doing action: CheckFilesInUse Aktion 10:33:37: CheckFilesInUse. Aktion gestartet 10:33:37: CheckFilesInUse. MSI (c) (9C:50) [10:33:37:976]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CheckFilesInUse' MSI (c) (9C:50) [10:33:38:007]: Creating MSIHANDLE (67) of type 790542 for thread 6480 MSI (c) (9C:F8) [10:33:38:007]: Invoking remote custom action. DLL: C:\DOCUME~1\brese\LOCALS~1\Temp\MSI872.tmp, Entrypoint: g0 MSI (c) (9C!20) [10:33:39:133]: PROPERTY CHANGE: Modifying OLINUSE property. Its current value is '1'. Its new value: '0'. MSI (c) (9C:F8) [10:33:40:976]: Closing MSIHANDLE (67) of type 790542 for thread 6480 Aktion beendet 10:33:40: CheckFilesInUse. Rückgabewert 1. Aktion 10:33:41: Welcome_Dialog. Dialog created Aktion 10:33:42: Start_Installation_Dialog. Dialog created MSI (c) (9C:50) [10:52:03:626]: Doing action: WiseCleanup Aktion 10:52:03: WiseCleanup. Aktion gestartet 10:52:03: WiseCleanup. MSI (c) (9C:50) [10:52:03:626]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'WiseCleanup' MSI (c) (9C:50) [10:52:03:657]: Creating MSIHANDLE (68) of type 790542 for thread 6480 MSI (c) (9C:6C) [10:52:03:657]: Invoking remote custom action. DLL: C:\DOCUME~1\brese\LOCALS~1\Temp\MSI879.tmp, Entrypoint: Cleanup MSI (c) (9C:6C) [10:52:03:657]: Closing MSIHANDLE (68) of type 790542 for thread 6480 Aktion beendet 10:52:03: WiseCleanup. Rückgabewert 1. MSI (c) (9C:50) [11:32:35:799]: Doing action: WiseCleanup Aktion 11:32:35: WiseCleanup. Aktion gestartet 11:32:35: WiseCleanup. MSI (c) (9C:50) [11:32:35:846]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'WiseCleanup' MSI (c) (9C:50) [11:32:35:878]: Creating MSIHANDLE (69) of type 790542 for thread 6480 MSI (c) (9C:2C) [11:32:35:878]: Invoking remote custom action. DLL: C:\DOCUME~1\brese\LOCALS~1\Temp\MSI88F.tmp, Entrypoint: Cleanup MSI (c) (9C:2C) [11:32:35:878]: Closing MSIHANDLE (69) of type 790542 for thread 6480 Aktion beendet 11:32:35: WiseCleanup. Rückgabewert 1. Aktion 11:32:37: Cancel. Dialog created MSI (c) (9C:50) [11:38:17:830]: Doing action: WiseCleanup Aktion 11:38:17: WiseCleanup. Aktion gestartet 11:38:17: WiseCleanup. MSI (c) (9C:50) [11:38:17:830]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'WiseCleanup' MSI (c) (9C:50) [11:38:17:846]: Creating MSIHANDLE (70) of type 790542 for thread 6480 MSI (c) (9C:A8) [11:38:17:846]: Invoking remote custom action. DLL: C:\DOCUME~1\brese\LOCALS~1\Temp\MSI890.tmp, Entrypoint: Cleanup MSI (c) (9C:A8) [11:38:17:846]: Closing MSIHANDLE (70) of type 790542 for thread 6480 Aktion beendet 11:38:17: WiseCleanup. Rückgabewert 1. Aktion beendet 11:38:17: Welcome_Dialog. Rückgabewert 2. MSI (c) (9C:40) [11:38:17:846]: Doing action: User_Exit Aktion 11:38:17: User_Exit. Aktion gestartet 11:38:17: User_Exit. MSI (c) (9C:40) [11:38:17:846]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'User_Exit' Aktion 11:38:17: User_Exit. Dialog created MSI (c) (9C:E4) [11:38:17:861]: Note: 1: 2262 2: ReserveCost 3: -2147287038 MSI (c) (9C:E4) [11:38:17:861]: Note: 1: 2205 2: 3: _RemoveFilePath Aktion beendet 11:38:19: User_Exit. Rückgabewert 2.
gestartet=started, beendet=completed, Rückgabewert=Return value
Thanks in advance
Ben
discussion Filed Under:
Comments
Which version of Wise are you
Which version of Wise are you creating your install with?
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Wise Installation Studio 7.0 SP1
Sorry, I forgot that important information... Wise Installation Studio 7.0 SP1 (7.3.0.250)
Forgot to ask..
What operating system is your client testing on, and what operating system(s) have you tested on?
If the client is running on Vista or Windows 7, have they tried running the install "As administrator", as the nature of the problem suggests a lack of permissions to "clean up" and therefore a long timeout until the process aborts and the install can continue.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
XP SP3
No, it's XP SP3:
Does the target computer have
Does the target computer have Windows Installer version 4.5? After we began distributing Windows Installer 4.5 with our product, we also began to experience this. The only solution is to cancel the installation and restart it until it works. It seems to be a bug in Wise with Windows Installer 4.5. I think it has been discussed here before.
Obviously WI 4.5
As you can see in my last post both Windows Installer properties 'VersionMSI' and 'VersionHandler' contain the value '4.05'. I have checked it on my own PC: '4.05' in the log file corresponds with '4.5.xxxx.yyyyy' version of msiexec.exe. So, I would indeed say that Windows Installer 4.5 is installed.
I appreciate JohanH's observation but I actually need an official statement I could present to our custormer. Nevertheless, I will try to let the customer test with Windows Installer versions lower than 4.5.
No official statements here
This is a user forum run by users for other users.
If you want an official statement, you will need to open a call with Symantec support and discuss this matter direct with them, as no-one in these forums is a Symantec employee (unless their tag states "Symantec Employee").
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
I see - no official
I see - no official statement.
Can anyone remember how the discussion mentioned by JohanH ended? Was there only the workaround suggested to 'restart it until it works'? Or perhaps an appropriate fix for Windows Installer 4.5 was discovered?
Here: https://www-secure.syma
Here:
https://www-secure.symantec.com/connect/forums/cos...
Link to Wise statement?
EdT,
you write in the thread specified by JohanH 'Wise confirm that this looks like it's a problem with Windows Installer 4.5'. Do you have a link to that statement?
No I don't
This discussions goes back over a year, and most likely I received this input via a personal email.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Would you like to reply?
Login or Register to post your comment.