17 replies to this topic

[balaji4u]

HI ,

I have some components deleted from my tree and hence i performed a major upgrade by changing the product code and package code in my installer. The major upgrade works fine but when i use the same setup to remove the contents the files are not deleted.I get the maintenence dailog and it shows the removal process but the files are never removed. What is the problem ? Can you please suggest asap.

regards,
balaji

Edited by balaji4u, 11 May 2012 - 10:50.

[Stefan Krueger]

The major upgrade should remove the component which are no longer in the new version. Does that work or does the major upgrade leave orphans behind?

[balaji4u]

After i do a major upgrade and perform the removal using the same setup all the folders are deleted but two folders are left behind in the installation directory which are not cleaned up. How to remove this?

I would like to provide some insight about my problem. The only thing that we changed in our product is the folder structure which is packaged. We added one folder and removed an exisiting folder. Now if i understand correctly the components to which these folders are associated are not changed in terms of there component codes, so i still expect a small update to copy by new folder which was newly created. But my small update failed to copy the newly created folder hence i tried to create a major upgrade. Now the major upgrade successfully copies the newly created folder but it fails to delete the component to which this newly created folder is associated. How do i handle this? . Hope the problem is clear, please let me know if you need more information.

Edited by balaji4u, 11 May 2012 - 14:10.

[Stefan Krueger]

I'm not sure I understand this:

[balaji4u]

There are two parent folders which are left behind and both the folders are present in both the setup's(New and old). Within each parent folders there are some 15 sub folders and one of the subfolder have been replaced with a new one and now on removal the whole of the parent folder remains as it is in the target system without any change. I want the complete parent folder with its sub folders to be deleted.

Edited by balaji4u, 11 May 2012 - 14:39.

[balaji4u]

I would like to simulate the scenario for you.

My Product has 12 features in the feature tree. And i have several components tied to these features. Till now we were providing minor upgrades since we were doing minor product changes basically in the exe and some dll's and minor upgrade was sufficing our requirement. Now we had to do some major folder changes in one of the components. We basically deleted one existing subfolder in one of the components and added a new sub folder to the same component. This particular component is associated with 4 features in my feature tree. I created a major upgrade item inorder to incorporate this change and on doing an upgrade my newly added folder was copied successfully onto my machine but when i used the same setup the component to which the new folders were added is not getting deleted. Even after adding the component in the RemoveFile table the component/folder is not removed. No clue whats so ever how to debug this issue. Hope the issue is clear, please provide suggestion to resolve it.

Regards,
Balaji

[MSIYER]

Post your log so that Stefan or anyone interested(me included) in your problem may go through it and suggest solutions.

[balaji4u]

Hi ,

I don't think so i can post the logs here, i am try to send a mail to you and stefan. but there seems to be server problem. I will try after sometime.

Regards,
Balaji

Edited by balaji4u, 15 May 2012 - 05:10.

[balaji4u]

Hi Stefan,

I have attached the logs for both my upgrade and removal scenarios, please check it and let me know if you can find something. I am trying it from past three days with no success.

Regards,
Balaji

Attached Files

•  Log.rar   0bytes   4 downloads

Edited by balaji4u, 16 May 2012 - 04:41.

[Stefan Krueger]

I can't download your attachment, did you delete it? Could you please upload it as zip instead of rar?

[balaji4u]

Hi Stefan,

Please find the attachement of the Install log i will upload the removal log seperately as its more than 500KB together.

Regards,
Balaji

Attached Files

•  Install.zip   356.41KB   89 downloads

[balaji4u]

Attaching the removal log. Please let me know if you are still facing problems with downloading.

Attached Files

•  remove.zip   171.44KB   125 downloads

[balaji4u]

One more recent finding, i installed win7 on one of my pc's and tried this scenario. It was a fresh system and everything works perfectly here. After major upgrade i do a removal and it perfectly removes everything without leaving any orphans, but when i use the same setup on a winxp machine i find orphans after the removal. On the winxp i cleaned the registry but still it doesn't work. Not sure whats wrong on my winxp machine.

[Stefan Krueger]

In the uninstall log I see many of these:

[Stefan Krueger]

And in the install.log:

[balaji4u]

Hi Stefan,

Thanks a lot for your time , as per your suggestion i tested it on a clean machine and it works perfectly fine now. Thanks once again.

Regards,
Balaji

[overlordchin]

Just so you understand what was most likely occurring. When you install something that is shared it adds a reference count under a GUID {xxxx-xxxxx-xxxxx-xxxxx} in the registry for that component. When you go to uninstall it; it decrements the entries by 1 and when it removes the final one it removes the actual files from the machine. When you mark something as permanent it 0's out the GUID so windows cannot see it when it is uninstalling and as such once anything has marked it as permanent it will never be removed even by something else that has it marked as shared.

You can also end up with those keys in the system causing files to remain behind if you do not uninstall something from add/remove and just manually delete the files.

These issues plagued our tests in QA for quite a while. Which consequently is why a clean machine resolves the issues.

Edited by overlordchin, 22 May 2012 - 19:23.

[balaji4u]

Hi,

You are right on what you said , but in my case non of my components where marked as shared or Permanent. Even after investigating i couldnt find out the actual reason on why this was happening on one of our machines. On a clean machine it works very well.