Software Deployment

First, you'll want to post in the correct forum, 'Package Development'. Please don't re-post: a moderator will probably move the thread.

Second, where in the sequence do you have the standard action RemoveExistingProducts?

Thanks for your reply.

I have that entry in InsallUISequnce table with the sequence number 6599 and I also tried with setting 5617.

Try to please the RemoveExistingproducts sequence between the InstallValidate action and the InstallInitialize action. In this case, the installer removes the old applications entirely before installing the new applications.

Please refer the link for correct placement of sequence.

http://msdn.microsoft.com/en-us/library/windows/desktop/aa371197(v=vs.85).aspx

You really want to take the RemoveExistingProducts entry out of InstallUISequence and put it in InstallExecuteSequence. Otherwise any silent install will not execute it. And like MahendraKumar said, schedule it between InstallValidate and InstallInitialize.

PJ

Thanks for your reply PJ.

Sorry I miss spelled the table name. I kept RemoveExistingProducts in InstallExecuteSequence only. I also set the sequence between InstallValidate and InstallInitialize. I set the property some thing like this RemoveExistingProducts = 1455. But when I ran the msi it completely uninstall the application and wouldn't install the newer version.

Please help me.

Thanks,
Sanjay

To me those sequence numbers mean nothing by themselves, only in relation with other actions' sequence numbers :-) What does the install log tell you? Is the MSI finishing successfully?

I set the property some thing like this RemoveExistingProducts = 1455This is enough to tell me that you should stop what you're doing and, before you do anything else, [Y A W N] read and digest Phil Wilson's "The Definitive Guide To Windows Installer".

Thanks,

Could you please tell me what is wrong I am doing while setting the sequence.

Do you know the difference between the sequences and the significance of the sequence numbering?

My point was (is), if you don't know, then you should stop now and learn the fundamentals before you end up in deeper water than you are now.

Thanks,

I am very new for this technology and recently I have started working on this.

But by seeing the InstallExecuteSequence table I could figure out that, installer engine triggers each and every action based on the sequence number. Suppose that the action InstallValidate and InstallInitialize having the sequence number 1400 & 1501 irrespectively , while running the MSI first InstallValidate will get trigger and than InstallInitialize and if we set any action like RemoveExistingProducts = 1455 it will trigger after the InstallValidate then InstallInitialize fires.
Please correct me if I am wrong.

Regards,
Sanjay

Looks like you figured out the meaning of the sequence correct!

[;)]

But still I have not found the solution for the main thread. Could you please tell me what else I need to modify in order to complete the major upgrade properly.

Does the newer msi got installed correctly? You can post the log file.
To find out the issue,
1. On a clean machine, try installing old app
2. Uninstall it using Product Code
3. Check what doesn't get removed (related registries and files)
4. Install new msi (which DOESN'T contain upgrade functionality).
5. Take a log to see if it causes any issues, reg permissions etc