My users report wyUpdate crashes when app updateSolved

I released an update to my app today. The AutoUpdater.DLL downloads the update, then when the app is relaunched to install the update wyUpdate just sits there on Extracting Files... It'll sit there forever, ...

This is a bug with the old version of AutomaticUpdater you're using (2.6.14). This was fixed in 2.6.16. You should use the latest version 2.6.18 (because other fixes were included).

It'll sit there forever, when cancel is pressed it shows the exception below.

wyUpdate shouldn't crash, unfortunately that stack trace isn't giving enough information. Can you download the latest version of wyUpdate source code, build the debug version. Include that with your app, then try to reproduce the "frozen extracting"? (Make sure you're still using the old AutomaticUpdater). Click cancel and tell me exactly what's null.

How do I fix this so users don't get this update error?

After you've found the exact crash reason, tell me and we'll fix this in wyUpdate. If you can't, we can schedule a time to remotely debug this for you.

The way to fix it for everyone is to use the newest version of the AutomaticUpdater.

>This is a bug with the old version of AutomaticUpdater you're using (2.6.14). This was fixed in 2.6.16. >You should use the latest version 2.6.18 (because other fixes were included).

Ok I'll update that now.

>wyUpdate shouldn't crash, unfortunately that stack trace isn't giving enough information. Can you download the >latest version of wyUpdate source code, build the debug version. Include that with your app, then try to>reproduce the "frozen extracting"? (Make sure you're still using the old AutomaticUpdater). Click cancel and tell >me exactly what's null.

It doesn't crash, it just shows the exception once cancel is clicked.

>After you've found the exact crash reason, tell me and we'll fix this in wyUpdate. If you can't, we >can schedule a time to remotely debug this for you.

I'll give the source debug a shot. If I can't figure it out I'll let you know.

>The way to fix it for everyone is to use the newest version of the AutomaticUpdater.

I'm assuming this will only fix it for the next round of updates? As the new .DLL will not be in place until they update to the new version ... which they can't do right now. If we can debug the wyUpdate.exe issue, does that mean it can be fixed on your end and then an update for wyUpdate.exe will be pushed down to them? If it was as simple as asking them to please use the setup.exe this time, that wouldn't be so bad, but I tried that too...

I asked one of my users to use the installer this time around, so he uninstalled my app, then reinstalled using my setup.exe (created using Inno Setup). He said even after doing that wyUpdate would still launch and close my app. He figured out he had to delete the wc folder and then it launched fine.

Should I be putting something in my install/uninstall script to delete this wc folder to avoid this issue? I'll do what I need to do on my end to make this as pain-free as possible for the users. If I have to ask them to use the setup executable on this update, that's not the end of the world I guess.

I guess I should have been paying closer attention to the AutomaticUpdater.DLL version. 😳

BTW, thanks for the quick response after hours last night! Great support! 🙂

I'm assuming this will only fix it for the next round of updates?

If you can't find (or reproduce) the cause of the crash then yes, unfortunately.

If we can debug the wyUpdate.exe issue, does that mean it can be fixed on your end and then an update for wyUpdate.exe will be pushed down to them?

Correct.

Should I be putting something in my install/uninstall script to delete this wc folder to avoid this issue?

No, if you're having the users install your app with the latest AutomaticUpdater / wyUpdate then there should be no problem. They might see a notice about a pending update. But wyupdate will cancel it as soon as it sees it doesn't match.

BTW, thanks for the quick response after hours last night! Great support!

No problem.

Hello,

I would like to add to this that several of my users have reported this same exact issue after i deployed my most recent update. I have since upgraded to the latest version, but when users who are using an older version of my app that has the 2.6.14 assembly try to update to the latest version, they get this same error as well.

Here is a screenshot of where it gets stuck:

http://www.placesscout.com/support/images/stuck-extracting-files.png

And here is that stack trace:

************** Exception Text **************System.NullReferenceException: Object reference not set to an instance of an object.at wyUpdate.frmMain.CancelUpdate(Boolean ForceClose, Boolean skipConfirmDialog)at System.Windows.Forms.Control.OnClick(EventArgs e)at System.Windows.Forms.Button.WndProc(Message& m)at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I have asked a user to record a screencast of the issue which i will post if he sends it to me.

When this happens i have to tell my users to manually uninstall the software and reinstall using the installer for the latest version, not very convenient 🙁.

Just to clarify based on the comments, this has been fixed in the most recent 2.6.18 version? Please confirm, thanks!

We're looking into this now.

We've found the bug and we're going to fix it ASAP.

I'm sorry for the trouble.

We've just released a fixed version of wyupdate (v2.6.18.2). Any users that don't have this problem won't get it. If you're still getting the problem, close wyUpdate (or crash it) then run this in a commandline window:

rmdir /s /q "%userprofile%\wc"rmdir /s /q "%appdata%\wyUpdate AU"

This will clear the AutomaticUpdater cache and thus clear out the old version of wyUpdate.

I'm truly sorry. We're making sure nothing like this happens again.

Had a similar problem (with 2.6.16), and the cache clearing seems to solve it.Thanks.

We've just released a fixed version of wyupdate (v2.6.18.2). Any users that don't have this problem won't get it. If you're still getting the problem, close wyUpdate (or crash it) then run this in a commandline window:

rmdir /s /q "%userprofile%\wc"

This will clear the AutomaticUpdater cache and thus clear out the old version of wyUpdate.

I'm truly sorry. We're making sure nothing like this happens again.

Wyatt,

I greatly appreciate your prompt help and solution to this matter. I will be sure to deploy the latest version of the assembly in my next update, so hopefully this won't happen again. Had a lot of complaints on this on lol, but glad to hear it is fixed.

Thanks again!Mark

We've just released a fixed version of wyupdate (v2.6.18.2).

Wyatt,

I upgraded my version of wyBuild using the auto-updater, and the software still reports that it is Version 2.6.18.0 in the about box. I also downloaded the installer and reinstalled wyBuild, same version.

In your comment above you noted that you released v2.6.18.2 with this bug fix, however, the current version reported after updating wyBuild is 2.6.18.0.

Can you please confirm that this this version 2.6.18.0 has the bug fix, or that perhaps something isn't getting updated properly?

Let me know, thanks!

We haven't released wyUpdate 2.6.18.2 yet. However we've already put wyUpdate 2.6.18.2 on the servers. This bug only shows up when wyUpdate self-updates to a version (under certain specific conditions). In other words, you can release your software with version 2.6.18.0 of wyUpdate until we release wyBuild 2.6.18.2.

I've the same problem with 2.6.18.0 😲 Is there now a fix for this bug? (I've also tried to clearing the cache..)

Restart your computer. Then, before running any other app, run these 2 lines:

rmdir /s /q "%userprofile%\wc"rmdir /s /q "%appdata%\wyUpdate AU"

Tell me if that helps.

no, same problem

We removed wyUpdate 2.6.18.0 from our hosting sites. Are you doing a custom self-update host?

Wyatt,

My users are still reporting problems with the auto-updater as well. Let me give you a quick synopsis:

My Software Version - AutomaticUpdater.dll Version - Customer issuesAll Versions < 2.5.0 - 2.6.14.0 - Sporadic but not widespread issues updating in older versions2.5.0 - 2.6.14.0 - Sporadic but not widespread issues updating upgrading from older versions to Version 2.5.02.5.1 - 2.6.16.0 - Many (but not all) users reported issues where updater would fail 'Extracting Updates' per my response to this thread on August 17th, 2012, 1:04 pm2.5.2 - 2.6.18.0 - Many (but not all) users reported issues where updater would fail 'Extracting Updates'. They would then force close the software. When the users opened my software again, they would get an error message saying that the auto-update failed, which i display when the automaticUpdater1_DownloadingOrExtractingFailed event is raised.

Every issue as of lately seems to be related to the extracting part of the update.

Please let me know what can be done to fix this, as i am getting constant complains and issues with the auto-updater, and in the past before 2.6.16 we never had these issues before.

Your prompt help in getting this fixed would be greatly appreciated, thanks.

Tell them to restart their computer. Them tell them to run these 2 lines:

rmdir /s /q "%userprofile%\wc"rmdir /s /q "%appdata%\wyUpdate AU"

Or you can put those lines in a batch file and have them run the batch file.

Make sure they run the batch file as their current user and as the same user that was doing the update (i.e. if they're elevating to AdminUser, then have them elevate the batch file as well -- right click, click Run As admin, etc.).

Does that make sense?

After that, the self-update will be downloaded correctly.

Until the bug is found, I upload the file manually to the ftp server.Is there a log which I can send you, that you can analyze the problem?

This bug has already been fixed.

What version is being downloaded for self-update? When wyUpdate is "frozen" on extracting, open the ""%userprofile%\wc" folder, dig down into the subfolders until you get to a "Selfupdate" folder.

Right click the InstantUpdate.exe file, click Properties. What's the version number?

hi

it is not "frozen" on extracting...My problem is that wyBuild is crashing when I click "upload updates". I can't put the files on the ftp with wyBuild...I do it manually.

Please copy and paste the full error of the crash.

this might be a uncached exception...when I start the debugger, I received the following exception:

System.IO.FileNotFoundException was unhandled Message="Die Datei oder Assembly \"AWSSDK, Version=1.4.15.1, Culture=neutral, PublicKeyToken=cd2d24cd2bace800\" oder eine Abhgigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden." Source="wybuild" FileName="AWSSDK, Version=1.4.15.1, Culture=neutral, PublicKeyToken=cd2d24cd2bace800" FusionLog="WRN: Protokollierung der Assemblybindung ist AUS.\r\nSie knen die Protokollierung der Assemblybindungsfehler aktivieren, indem Sie den Registrierungswert [HKLM\\Software\\Microsoft\\Fusion!EnableLog] (DWORD) auf 1 festlegen.\r\nHinweis: Die Protokollierung der Assemblybindungsfehler frt zu einer gewissen Leistungseinbu.\r\nSie knen dieses Feature deaktivieren, indem Sie den Registrierungswert [HKLM\\Software\\Microsoft\\Fusion!EnableLog] entfernen.\r\n" StackTrace: bei wyBuild.Uploader.UploadFiles() bei wyBuild.Uploader.RunUploadFiles() bei System.Threading.ThreadHelper.ThreadStart_Context(Object state) bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) bei System.Threading.ThreadHelper.ThreadStart() InnerException:

It looks like you've deleted or moved the update files since you've built them, and thus you won't be able to use wyBuild as an uploader until you rebuild (or replace) the files you removed.

nope..the files where there.I have more than one project...and I have the exception with all of my projects ❓

There's something wrong with your S3 settings. Can you make a simple project with a test S3 account that reproduces this problem. Send it to support@wyday.com.

what do you mean with S3 settings/account?

It looks like you have a corrupt build of wyBuild. Re-download wyBuild from our site (never use any third party to download wyBuild). Reinstall wyBuild then try again. If you still get problems then give us a detailed step-by-step on the methods you used to create the problem.

Also, don't modify any files in the wyBuild folder.

HiI've pressed the repair button from the setup - now the upload process doesn't crash anymore 😛

Thanks for your help!

Greets

What directory should be cleared for a windows service? We are using the AutoUpdater. The service is running as Local System Account.

Thanks...

This answers it pretty well: Where can I find data stored by a Windows Service running as Local System Account?