.EXE Was Not Replaced On New Install - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

rkulp
Posts: 48
Joined: Mon Feb 26, 2007 10:50 pm

.EXE Was Not Replaced On New Install

Consider the following: Version x.x.1 is being replaced by version x.x.2 using a complete install package, not an upgrade. The two versions should have different GUIDs. On all but one computer, the version x.x.1 exe file is replaced by the version x.x.2 exe. However, on this computer running XP Professional the old exe remained. I could not find an explanation. So, I removed the old program and did a new install. Still the old exe appeared. Next, I verified that the exe in the install package was correct and tried again. No luck. Finally, I just did a copy of the new exe into the application directory on the XP computer. Any suggestions on how to debug this behavior? No user has complained about difficulties installing new versions or if this has occurred to them. The only thing I can think of is failing to change the GUID when the build number was changed, buit I have never failed to heed the warning before. Is there any other way this could happen?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: .EXE Was Not Replaced On New Install

Hi,

I'm not sure why you encountered this behavior. Can you please send us a verbose log of the install process which shows this problem to support at advancedinstaller dot com so we can investigate it.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
canhuth
Posts: 241
Joined: Thu Jun 19, 2008 9:03 am

Re: .EXE Was Not Replaced On New Install

rkulp wrote:Consider the following: Version x.x.1 is being replaced by version x.x.2 using a complete install package, not an upgrade. The two versions should have different GUIDs. On all but one computer, the version x.x.1 exe file is replaced by the version x.x.2 exe. However, on this computer running XP Professional the old exe remained. I could not find an explanation. So, I removed the old program and did a new install.
Do these .exe files have version information in them? If so, post that information here, esp. from the problematic machine.

After you removed the "old program", did you remove the installation folder with that .exe file too? The deinstall might have thought "well, I didn't place that file here, so I certainly won't remove it!".

These might be related:

http://www.advancedinstaller.com/forums ... hilit=amus
http://www.advancedinstaller.com/forums ... ode#p19260
http://www.advancedinstaller.com/forums ... ode#p19259



With best regards

Clemens Anhuth
Last edited by canhuth on Mon Sep 29, 2008 2:35 pm, edited 1 time in total.
rkulp
Posts: 48
Joined: Mon Feb 26, 2007 10:50 pm

Re: .EXE Was Not Replaced On New Install

Thank you both for your responses. I don't think it is possible to reproduce this as the old version exe is no longer on the problematic computer. Both exe files had version information which was correct. It may take a few days to reconstruct the situation. I have to find a version of the old exe and install it on the computer then try again.
rkulp
Posts: 48
Joined: Mon Feb 26, 2007 10:50 pm

Re: .EXE Was Not Replaced On New Install

I was in luck. I found a complete install package for the old version on another computer. I used Add/Remove programs to uninstall the later version but the desktop shortcut did not disapper. I installed the older version anyway and it executed the newer version. So, I uninstalled again and the shortcut was still on the desktop. I tried to run it and was unable to initialize the first screen (the splash screen showed). I then ran a registry cleaner but that did not reveal any errors associated with this install or program. The app dir in program files was still there with all the install files. I moved that to the recycle bin and did a fresh install of the older program, started it and verified it was indeed the older program. Finally I did a verbose install and verified that the older program was actually there. I'll send in the log to support.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: .EXE Was Not Replaced On New Install

Hi,

The log you sent contains multiple lines which look like this:

Code: Select all

MSI (s) (88:70) [09:49:59:859]: Disallowing uninstallation of component: {32944DCF-55B1-4A05-A122-C017189E2E91} since another client exists
MSI (s) (88:70) [09:49:59:859]: Disallowing uninstallation of component: {98584376-1CF6-49DF-A949-5B286328D86D} since another client exists
MSI (s) (88:70) [09:49:59:859]: Disallowing uninstallation of component: {B4F65233-8EB6-4D6C-A11C-6335DFA44F14} since another client exists
MSI (s) (88:70) [09:49:59:859]: Disallowing uninstallation of component: {6AB70E7A-51CA-46E4-9F18-01EE151174E5} since another client exists
Basically, another product uses the same components, therefore they cannot be removed. How did you create the project you sent? Did you copy another AIP file and then modified it?

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
rkulp
Posts: 48
Joined: Mon Feb 26, 2007 10:50 pm

Re: .EXE Was Not Replaced On New Install

There are some components that are in use by another program. I had put them in a different folder in Program Files so, in reality, duplicate copies exist. As I see it, these are my choices: 1) create a common folder that contains all common components for all applications; 2) put all common components in the GAC.
Which is better? Why does this not happen in Vista but does in XP?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: .EXE Was Not Replaced On New Install

Hi,
As I see it, these are my choices: 1) create a common folder that contains all common components for all applications; 2) put all common components in the GAC.
Which is better?
If multiple products use the same components, it is recommended to install these components in a common location (for example in "Program Files\Common Files"). If the components have the same names and GUIDs in all packages, Windows Installer will use a reference count to handle them (increase it when a new package tries to install the components and decrease it when an install package tries to uninstall the components).
Why does this not happen in Vista but does in XP?
The behavior should be the same on all OS versions. Perhaps there was a problem on your XP machine or some elements in your package are conditioned by the OS version.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
rkulp
Posts: 48
Joined: Mon Feb 26, 2007 10:50 pm

Re: .EXE Was Not Replaced On New Install

I have created the common files folder and moved all the dlls to that folder. I have attempted to delete them from the applications folder but to no avail. When the install package is run the common files folder is created and the dlls are properly loaded. I had them privately installed to the common files folder (on assemblies page so I presume they are registered to that folder). On uninstall, they are removed or not, as appropriate.
However, they are also installed in AppDir. Nothing I have done has kept them from being also installed there. Also, if they are manually removed from the AppDir the program won't run. So, I am clearly missing something.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: .EXE Was Not Replaced On New Install

Hi,
However, they are also installed in AppDir. Nothing I have done has kept them from being also installed there. Also, if they are manually removed from the AppDir the program won't run.
Please note that first you should unregister the files from the installation folder (uninstall all packages which registered them there). After that, you should make sure that your Advanced Installer project is not configured to install the common files in the installation folder. Also, you should modify your application so it knows to retrieve the files from the "Common Files" folder instead of the installation folder.

Finally, you should test the modified package on a clean machine.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
rkulp
Posts: 48
Joined: Mon Feb 26, 2007 10:50 pm

Re: .EXE Was Not Replaced On New Install

[quote="Please note that first you should unregister the files from the installation folder (uninstall all packages which registered them there). After that, you should make sure that your Advanced Installer project is not configured to install the common files in the installation folder."[/quote]

I did each of those things.

[quote= "Also, you should modify your application so it knows to retrieve the files from the "Common Files" folder instead of the installation folder. "[/quote]

I'm not sure exactly how to do this in VS2005 but am sure I can find out.

[quote= "Finally, you should test the modified package on a clean machine." [/quote]

Finding a clean machine may be difficult.

Thanks, Cosmin.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: .EXE Was Not Replaced On New Install

Hi,
Finding a clean machine may be difficult.
Please note that you can use a virtual machine (its easier to manage and you don't need another computer). Let me know what are the results of your tests.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”