Checking for updates failer

Hi,

I have a project I have been building and am adding the wyUpdate into it. When my login form (which has the .NET control on it) opens it checks for an update but it reads 'Failed to check for updates' and the error is 'wyUpdate ended before the current update step could be completed.'. I ran the wyUpdate.exe and it read 'the latest version is already installed.

Is there anything I can check to see what might be causing this issue?

Thanks in advance.

Stephen

Yes, make sure "wyUpdateLocation" is set, also make sure you don't have another instance of wyUpdate running somewhere in the background.

Hi,

Thanks for the reply. The property says 'wyUpdate.exe' and that is all.

Is this correct?

Only if wyUpdate.exe is in the same directory as your app. I don't know. That's the firs thing you have to check.

Yes it is in the same directory.

  1. Open task manage and kill all other instances of wyUpdate.
  2. Explicitly set the full path to wyUpdate.exe using the wyUpdateLocation property.

Have done this but still the same issue.

Do you have multiple users on the system? Log off all other users and try again.

Are you using the AutomaticUpdater in some funky way?

Hi,

Not that I am aware of.

I have rebooted my pc and the same issue persists.

I have the control sitting on a login form and in the forms load event I am calling

Me.AutomaticUpdater1.wyUpdateLocation = Application.StartupPath & "\" Me.AutomaticUpdater1.ForceCheckForUpdate()

When I run the updater in the directory it says there are no updates and checks everything fine.

Can you give me some trouble shooting steps please as I have started releasing this to users and would like the updater in place rather than generating new installs.

Thanks in advance.

Don't call ForceCheckForUpdate. Just let the AutomaticUpdater handle the update checking (because, after all, that what the AutomaticUpdater does -- automatically update your app). Only use the DaysBetweenChecks and WaitBeforeCheckSecs properties.

OK. I have done this but it does nothing (it displays no checking text etc at all). It displays nothing at all. I set days to 0 because i would like it to check everytime at the moment while I am getting this working.

Thanks.

OK. I have done this but it does nothing (it displays no checking text etc at all). It displays nothing at all. I set days to 0 because i would like it to check everytime at the moment while I am getting this working.

Right, when there's nothing to update, it doesn't bother the user at all. (Do you really want the AutomaticUpdater to bother your user and then say "Oops, looks like there's nothing to see here."?)

To be honest yes I would like it to at least say The software is up to date. So apart from compiling an update is there any way to tell it is working?

Yes, handle all the events. The "UpToDate" event, in particular, is the event you're looking for.

And it still does not work. Disappointing product.

You need to be more specific. What "does not work"? Are you getting an error? If so, what? Did you handle all of the events, or just some? Did you add breakpoints so you could see which events were being called? Is something not behaving as expected? Then you need to tell me what you are doing, what you expect, and what is happening.

Unfortunately the AutomaticUpdater isn't magic (not yet, at least). You need to tell use what you're doing and the errors you're getting if you want us to provide useful help.

If you don't want to figure out how the AutomaticUpdater works, then just use wyUpdate in standalone mode. wyUpdate in standalone mode tells you what's happening in plain English. No need to handle events.

Reply
Discard post