InstallAware

Hi,
I'm having a problem with getting a web update to work. After uploading a new setup file and updates.ini file, I manually execute the update. The setup indicates that an update is available, and when I click it, something downloads, but the program isn't updated. If I check for updates again, nothing happens (no popups, no indications at all). Here's what I've done:

1) deployed in initial 1.0 setup using compressed web blocks, with web updating enabled
-- Checked the Receive Application Updates box on Project Properties page
-- Indicated proper Monitor URL
-- Selected Manual update checking
-- NOTE: The initial download and setup appears to work correctly
2) I later discovered errors in my program, so I fixed them
3) Edited the original setup design:
-- changed the version number from 5.0 to 5.0.1
-- added some files to the setup
-- configured an update pack (full installation) and added the original version
-- edited the updates.ini code according to your Web Updates whitepaper to return error codes
4) Rebuilt setup with the "Change revision code automatically" option under project settings checked
-- I did not change the output filename
5) Uploaded the newly created setup exe and all the web blocks to the server
-- NOTE: These files all had the same name as the original setup deployment
6) Manually clicked the "Check for Updates" shortcut in the start menu (created by me)
-- DID NOT UPDATE PROGRAM PROPERLY

Thoughts? -John

Dear John,

For what you tell me, everything seems correct, but of course there is an error somewhere.
I use the same without any problem.

Are your update effectively downloaded?
If true, have you tried to execute it (manually copying it ) on the target machine. your app will be updated?

Alternatively, could you please send me a very simple project that replicates the issue?

Regards

Francesco,
At least I had the steps right. I thought that maybe I had to rename the update file to something different from the original setup name. Perhaps I made a mistake when I altered the updates script. I'll go back through it and see if I can determine what the problem might be. I'll try to build a simple test to recreate it if I get stumped.

Thanks, John

Hi again,
Could this problem have anything to do with a change in the User Account Control levels between updates?

The first time I deployed the setup I had the Requested Elevation Level set to "Elevate Administrators Only (highest available)". I changed it to "Never Elevate (as Invoker)" for the update, which I read was the best choice for allowing the user to install updates without administrator privileges (please correct me if I'm wrong about that).

- John

Dear John,

... probably the "Elevation Level" could be the reason.
I suppose that you can easly verify it. Try to see if the same happens executing the setup with an OS that don't have UAC.

Anyway, using "Never Elevate (as Invoker)" could not work properly ... if your update requires Admin privileges ( ... the update makes System modifications?).

Let me know.

Regards

Francesco,
How can I tell if the update (or initial install for that matter) makes System modifications? What qualifies as a System mod?

John

Dear John,

please refer to my reply with your other topic.
http://www.installaware.com/forum/viewt ... 684#p32684

Regards