"Failed to build update files" error.

This "freezing" behavior when building updates was an old bug in wyBuild (we've long since fixed it). What version of wyBuild are you using?

If you're already using the latest version then we'll either need the files that cause this bug to appear. Or do a remote debug.

Hello Wyatt,

Thanks for your message.

I'm using version 2.6.18.4.

The freeze we're talking about I never faced before and I deploy updates quite often.

I'm fine with sending you the files but I'm not sure it will help as the same set of files does not cause any problem on another project I created.I'm fine with a remote debug too.

Please let me know how you want to proceed and how I can help. I have a Skype account if needed.

Thanks again.

Hello again Wyatt,

I don't want to push you, can just give me a rough idea of when you will be available for the remote debug? As I said, I need to deploy a critical update and therefore need to organize things on my end.

Thanks a lot.

Before we do that, have you tried deleting those 2 new versions first, and trying to rebuild? What happens? Does it freeze? If not, try adding a new version and adding the files (being sure to exclude the wyUpdate.exe file). Does it freeze then?

>>Before we do that, have you tried deleting those 2 new versions first, and trying to rebuild? What happens?

Yes. I had already done that with 3.6.0.17. Just did that again with 3.6.0.18. Removing it from the project took like 30s and during that time, wyBuild was frozen. Then I tried to regenerate patches for 3.6.0.15 and faced the same freeze and error problem. Remember this version is the one currently in the wild and I initially had no problem to generate the patches for it.

Thanks.

Send me your project file (*.wyp) to wyatt@wyday.com and I'll take a look at it.

Sent.

We didn't find anything wrong with your project file. My advice would be to move your files to another harddrive. It sounds like your harddrive might be dying. After doing that, try again.

You might be right. I've had one sign of failure today.

Would this procedure be right:

- Move all my binaries folders to a new drive.- Move my output folder to the new drive.- Move the wyp file to the new drive.- Update the output folder in the project to the new location.- For each version remove all files and add the ones copied to the new drive

- Create new version and patches as usual.

Can I be sure I won't break my update chain with that?

Also,- I would like to take this opportunity to remove older versions. Is there any risk in removing older versions (except users with those version not being able to upgrade)?- Some intermediary versions haven't had time to be widely deployed and I would like to get rid of them too. Is there any risk in doing so ?

Would this procedure be right:

That looks about right. However you don't have to remove/re-add files to the versions. wyBuild uses relative paths so everything will work fine if you have the same folder structure.

Also, you should verify that your dying harddrive didn't corrupt your binaries. If you have a backup, you should use those instead.

- I would like to take this opportunity to remove older versions. Is there any risk in removing older versions (except users with those version not being able to upgrade)?

That's the only risk (users on those versions won't be able to update.

- Some intermediary versions haven't had time to be widely deployed and I would like to get rid of them too. Is there any risk in doing so ?

Same risk as above.

Wyatt,

You were right in all respects.

While copying the files, 4 of them (part of the last version) triggered the exact same error I had in wyBuild.

I can now generate the patches again.

Thanks for all your help.

-- Jerome

It's my pleasure, I'm glad you got it all sorted out.