Getting "failed the Adler32 validation" errorAnswered

Hi, we are seeing a strange issue with our updates using wyUpdate. Everything was working fine for many many years until a couple of days back. Since then, we are getting this error while downloading the update i.e. the “*.wyu” file.

To rule out any issues we have checked the following:

  1. The updates on the server are unchanged since the last 4 months. Clients were able to download these files 3 days back and since then all of them are getting this same error for the same updates that were working fine earlier.
  2. We also replaced the latest updates with older versions as we have separate folders as backups for older updates. Even then, these updates which worked fine in earlier days are failing with this error now.

Our installer which was working hasn't changed in years. The same installer and then the update to the installer version was working without issues. All of a sudden, the updates are now failing with adler checksum violation issue. 

Any pointers will be really helpful as we have a lot of clients who are stuck now on this.

Thank you. 

Answer

Hello,

Use the forum search to see if this problem has been posted before.

Here you can see the same problem and the solution. Follow the thread;

https://wyday.com/forum/t/1571/failed-the-adler32-validation/

Hi, 

Had seen that answer. It does not apply in our case. In our case

  1. The updates were working perfectly fine on all the client PCs and our test machines.
  2. Then, updates started to fail on all the machines from a particular day. There were no changes to the update files like the missing files mentioned in the earlier answer. 
  3. We are wondering if the adler validation logic is to blame here i.e. is it getting incorrectly computed (not sure about this though).

We tried to build wyUpdate from the source and bypassed the Adler validation check. The updates were installed fine after that. However, we would like to understand why the Adler validation check has started failing all of a sudden.

Thank you.

Answer

If something MITM the connection or if someone modified the files on the server, then yes, you'll get that error.

Rebuild your updates and reupload them. And don't replace or modify single update items.

Hi Wyatt,

We tried uploading the updates to the server again. That failed as well. 

Regarding MITM possibility, we see this happening to all users from different cities accessing the updates over different ISPs. 

Wondering what else could be to blame here.

Rebuild the updates. THEN reupload the rebuilt updates (including the *.wys file)

Rebuilt the updates and uploaded all the updates to server, including the *.wys file. Still getting the same error :(

Reply
Discard post