Adler32 validation errorSolved

I am having a problem with wyupdate. All update files have been uploaded to the server. The only time we see this problem is when the client is trying to download the all.to.<version> file. From my testing, it seems that wyupdate is not downloading the entire file. It gets about 5% of the way through then gives the error. I tore apart the wyserver.wys file and confirmed the adler32 checksum for the all.to.<version> file that is on the server. I can download the file with any web browser without fail. The only time it fails is when wyupdate is trying to download it. the all.to.<version> file is quite large, 633 MB, but I can't see that being an issue. Can anyone offer any help?

, edited

This is the error from the server:

Event code: 3001 Event message: The request has been aborted. Event time: 12/20/2016 4:08:35 PM Event time (UTC): 12/21/2016 12:08:35 AM Event ID: 65e23fd8dd6f4fe58d556450592550e2 Event sequence: 15 Event occurrence: 3 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/ROOT/updates/smartdr-27-131267484775207554 Trust level: Full Application Virtual Path: /updates/smartdr Application Path: C:\updates\smartdr\ Machine name: xxxxxxxxxxxxProcess information: Process ID: 2684 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Exception information: Exception type: HttpException Exception message: Request timed out.

Request information: Request URL: http://xxxxxxxxxxxxx/updates/smartdr/SelectUpdate.aspx?update=smartdr.001.001.003.to.001.001.005.wyu&pKey= Request path: /updates/smartdr/SelectUpdate.aspx User host address: xxxxxxxxxxxxxxx User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITY\NETWORK SERVICE Thread information: Thread ID: 23 Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: False Stack trace:

If any one has any information, I would be much appreciative.

The web service that serves up the file was timing out because the execution timeout was set to default 110 seconds. File was too large to download in this time.If anyone else has this issue, the solution was to add this to the web.config:

<system.web> <httpRuntime executionTimeout="10000" /></system.web>