nowickim
Posts: 3
Joined: Mon Jun 25, 2012 8:21 pm

Files in use showing the actual updater program

We have built an installer that includes updater.exe as a service so that we can bypass the need to elevate permissions for Windows XP, Vista, 7, etc. We are using the updater in manual mode so that our program calls the updater each time it runs. Our program calls updater /justcheck and then if the exit code is zero we re-run updater with /checknow and then exit our program.

All of this works fine whether the user is admin or non-admin. The problem is that when updater runs and finds an update, it goes to install the update we get a "Files in use" window that shows the updater.exe is in use.

If you look at the attached screenshot you'll see the error. You'll also see that in the taskbar you can see the installer running but you can also see the updater running (in the taskbar it shows "Installing updaes for...". I think this is because the installer is trying to copy over updater.exe which is running at the time.

What am I doing wrong?

Attached to this post is the screenshot as well as the AIP files for the installer and the update. Please help!
Attachments
Files in use error.JPG
Files in use error.JPG (132.78 KiB) Viewed 2507 times
SmartEyeUpdater.aip
(10.65 KiB) Downloaded 329 times
SmartEye.aip
(47.33 KiB) Downloaded 326 times
nowickim
Posts: 3
Joined: Mon Jun 25, 2012 8:21 pm

Re: Files in use showing the actual updater program

Two other notes on this:

1. If I End Task on updater.exe the "Files in use" problem goes away and the installer completes successfully

2. I'm currently using Advanced Installer 9.7. We'll be upgrading our maintenance plan tomorrow so I can upgrade to the newest version.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Files in use showing the actual updater program

Hi,

This is very strange because the updater copies itself to a temporary location from where it runs, it never runs from the install folder. It was designed like this especially for this situation to be avoided.

Can you please check its process with Process Explorer to see from where is the executable running? Also, do you get this behavior on all machines?

Best regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”