Software Deployment

Hi jebodis,
this could happen, if the uninstall is scheduled after the install (this is the default with quiete a few MSI authoring tools) and then removes a file wich has the same name in both versions.
have you allready inspected the MSI's with ORCA?
If not, please get ORCA and install it.
Load the MSI in ORCA and go to the 'InstallExecuteSequnce' table.
Sort the table alphabetcally and look for 'RemoveExistingProducts' line. Highlight it.
Sort the table by the sequence column and find the highligted row.
Make sure, that sequence of 'RemoveExistingProducts' is right before 'InstallValidate'.
Regards, Nick

Hi nheim,

thanks for your answer, but it doesn't work.

Before posting my problem, i already placed "RemoveExistingProduct" between "InstallValidate" and "InstallInitialize".
Than i placed it before "InstallValidate", but the file is still being ignored.

Msi Setup displayes for some seconds "RemoveExistingProduct" with a string looking like a Registry entry, but than does
"InstallValidate". After this, msi is really deleting everything of the package. Than the new package is being installed,
except this single file.
Regards, jebodis

Hi jebodis,
maybe, there is a check for the presence of this file early in the sequence.
Get a look at the 'DrLocator', 'AppSearch' and 'Signature' tables for entries.
Also look for conditions in the 'Components' table.
Regards, Nick

the first 3 tables are empty and the components table has no conditions

;(

Where is the file located?
Check if the msidbComponentAttributesPermanent Attribute bit has been set for the component holding the file preventing the file from being removed during uninstall.

It is located in the programm's folder.

I'll check your tip, but the file is not being prevented from uninstalling, it is prevented from reinstalling AFTER the uninstall.

-> Bit is not set

Do a verbose log during install and see if it tells you anything why it isn't installed.

Hi jebodis,
one last step: How many features does the MSI have (feature table)? Do you have entries in the condition table?

And then, guessing must have an end, if we want this bring to a glory end!
Please log the installation as AngelD suggested and search in the logfile for the occurence of the file and component which belongs to the file.
For easier log-reading, use 'WiLogUtl.exe' from the SDK.
Regards, Nick

Hi,
sorry for my long absence.

I tried a lot of things with this file.
I placed it in a new component and a new Feature and made it the root Feature, but nothing helped.
Than i changed the install place for the component (and than setup installed it !!). To get it at the right place, i placed a "moveFile" in the component, but it didn't worked ;(

As final i logged the installation process, but didn't found any errors related to the file.

In the "states" window of WinLogUtil.exe the file has following attributes: Installed: Absent; Request: Local; Action: Null

I don't understand why Action is null (it should be local i guess), because the feature holding the file is marked as "always install this feature".

@nheim: 16 Features ; no conditions

any further ideas ?

Sorry to resurrect an old thread, but I'm having this exact same problem. I'm wondering if the original poster found a solution to the problem.

Hi Silvain,
please log the installation, load the log file to an ftp service like senduit and post the link here.
Regards, Nick

The faulty file is UCD03.dll. Senduit.com is blocked where I work. I found another website, I'm not sure if it works well...

Here's the log file for a fresh install (not upgrading from a previous version already installed):

http://www.keepandshare.com/doc/view.php?id=1022103&da=y


Here's the log file for an upgrade, when version 1.0.1 is already installed:

http://www.keepandshare.com/doc/view.php?id=1022104&da=y


Thanks.

Hi Silvain,
it could be the "migrate feature states" action. Decrease the attribute on the upgrade table entries by 4 to disable it.
Are the feature list of the old and new apps the same?
Which file are we talking about exactly, here?



MSI (s) (80:D4) [09:46:05:139]: Doing action: MigrateFeatureStates
Fin de l'action 09:46:05 : SetODBCFolders. Valeur renvoyée : 1.
MSI (s) (80:D4) [09:46:05:139]: Migrating feature settings from product(s) '{C0688194-E0D8-45D5-B215-04B82E4B458C}'
MSI (s) (80:D4) [09:46:05:139]: MigrateFeatureStates: based on existing product, setting feature 'VDM' to 'Local' state.
MSI (s) (80:D4) [09:46:05:139]: MigrateFeatureStates: based on existing product, setting feature 'Complete' to 'Local' state.
Début de l'action 09:46:05 : MigrateFeatureStates.


Regards, Nick

try installing the new msi over the old by below command

msiexec /i <msipath> REINSTALL=ALL REINSTALLMODE=amuos

I decreased the attributes of the entries in the upgrade table by 4 (from 673 to 669). The same file is still missing (UCD03.DLL) when I try to upgrade from a previous version (1.0.1). The features are the same as I used the old WSI from version 1.0.1 and just changed the product code and a few files.

I'm using Wise Package Studio 7.0 SP3.

shweta_kar: The REINSTALL=ALL does not work because the product, the new msi, was never installed on the computer.