This has been popping up on me the last few days. It’s the auto update that is not working,manual updates seem to work though.
Any ideas on how to resolve the issue?
As I recall automatic updates stopped working for you 2 months ago also.
May we seen the last part of your setup log showing the errors at this time (not the whole thing just the last part)?
18:40:59 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:40:59 nrm/gen InvalidateCurrent: invalidated server ‘Download67 AVAST server’ from ‘main’
18:40:59 nrm/gen SelectCurrent: selected server ‘Download4 AVAST server’ from ‘main’
18:40:59 min/pkg GetPackages - set proxy for inet
18:40:59 nrm/int SYNCER: Type: no proxy
18:40:59 nrm/int SYNCER: Auth: no authentication
18:40:59 dbg/int while trying to get file ‘servers.def.vpu’, error 0x20000004 has occured, try 71
18:41:16 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:41:16 nrm/gen InvalidateCurrent: invalidated server ‘Download4 AVAST server’ from ‘main’
18:41:16 nrm/gen SelectCurrent: selected server ‘Download39 AVAST server’ from ‘main’
18:41:16 min/pkg GetPackages - set proxy for inet
18:41:16 nrm/int SYNCER: Type: no proxy
18:41:16 nrm/int SYNCER: Auth: no authentication
18:41:16 dbg/int while trying to get file ‘servers.def.vpu’, error 0x20000004 has occured, try 72
18:41:33 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:41:33 nrm/gen InvalidateCurrent: invalidated server ‘Download39 AVAST server’ from ‘main’
18:41:33 nrm/gen SelectCurrent: selected server ‘Download62 AVAST server’ from ‘main’
18:41:33 min/pkg GetPackages - set proxy for inet
18:41:33 nrm/int SYNCER: Type: no proxy
18:41:33 nrm/int SYNCER: Auth: no authentication
18:41:33 dbg/int while trying to get file ‘servers.def.vpu’, error 0x20000004 has occured, try 73
18:41:50 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:41:50 nrm/gen InvalidateCurrent: invalidated server ‘Download62 AVAST server’ from ‘main’
18:41:50 nrm/gen SelectCurrent: selected server ‘Download40 AVAST server’ from ‘main’
18:41:50 min/pkg GetPackages - set proxy for inet
18:41:50 nrm/int SYNCER: Type: no proxy
18:41:50 nrm/int SYNCER: Auth: no authentication
18:41:50 dbg/int while trying to get file ‘servers.def.vpu’, error 0x20000004 has occured, try 74
18:42:07 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:42:07 nrm/gen InvalidateCurrent: invalidated server ‘Download40 AVAST server’ from ‘main’
18:42:07 nrm/gen SelectCurrent: selected server ‘Download59 AVAST server’ from ‘main’
18:42:07 min/pkg GetPackages - set proxy for inet
18:42:07 nrm/int SYNCER: Type: no proxy
18:42:07 nrm/int SYNCER: Auth: no authentication
18:42:07 dbg/int while trying to get file ‘servers.def.vpu’, error 0x20000004 has occured, try 75
18:42:24 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:42:24 nrm/gen InvalidateCurrent: invalidated server ‘Download59 AVAST server’ from ‘main’
18:42:24 nrm/gen SelectCurrent: selected server ‘Download43 AVAST server’ from ‘main’
18:42:24 min/pkg GetPackages - set proxy for inet
18:42:24 nrm/int SYNCER: Type: no proxy
18:42:24 nrm/int SYNCER: Auth: no authentication
18:42:24 dbg/int while trying to get file ‘servers.def.vpu’, error 0x20000004 has occured, try 76
18:42:41 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:42:41 nrm/gen InvalidateCurrent: invalidated server ‘Download43 AVAST server’ from ‘main’
18:42:41 nrm/gen SelectCurrent: selected server ‘Download64 AVAST server’ from ‘main’
18:42:41 min/pkg GetPackages - set proxy for inet
18:42:41 nrm/int SYNCER: Type: no proxy
18:42:41 nrm/int SYNCER: Auth: no authentication
18:42:41 dbg/int while trying to get file ‘servers.def.vpu’, error 0x20000004 has occured, try 77
18:42:58 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:42:58 nrm/gen InvalidateCurrent: invalidated server ‘Download64 AVAST server’ from ‘main’
18:42:58 nrm/gen SelectCurrent: selected server ‘Download58 AVAST server’ from ‘main’
18:42:58 min/pkg GetPackages - set proxy for inet
18:42:58 nrm/int SYNCER: Type: no proxy
18:42:58 nrm/int SYNCER: Auth: no authentication
18:42:58 dbg/int while trying to get file ‘servers.def.vpu’, error 0x20000004 has occured, try 78
18:43:15 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:43:15 nrm/gen InvalidateCurrent: invalidated server ‘Download58 AVAST server’ from ‘main’
18:43:15 nrm/gen SelectCurrent: selected server ‘Download78 AVAST server’ from ‘main’
18:43:15 min/pkg GetPackages - set proxy for inet
18:43:15 nrm/int SYNCER: Type: no proxy
18:43:15 nrm/int SYNCER: Auth: no authentication
18:43:15 dbg/int while trying to get file ‘servers.def.vpu’, error 0x20000004 has occured, try 79
18:43:32 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:43:32 nrm/gen InvalidateCurrent: invalidated server ‘Download78 AVAST server’ from ‘main’
18:43:32 min/gen SelectCurrent: unable to find any suitable server in ‘main’
18:43:32 dbg/int while trying to get file ‘servers.def.vpu’, error 0x20000004 has occured, try 80
18:43:32 min/int tried 80 servers to get file ‘servers.def.vpu’, but failed (0x20000004)
18:43:32 min/fil GetNewerStampedFile:GetFileWithRetry failed: C:\WINDOWS\TEMP_av_proI.tm~a03112\onefile, servers.def.vpu, error: 0x20000004
18:43:32 min/pkg Download servers.def, servers.def.vpu failed with error 0x20000004.
18:43:47 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:44:02 min/pkg ERROR:HttpGetWinsock, WinsockTcpConnect() returned 0x00002AF9
18:44:02 nrm/gen InvalidateCurrent: invalidated server ‘Download78 AVAST server’ from ‘main’
18:44:02 min/gen SelectCurrent: unable to find any suitable server in ‘main’
18:44:02 dbg/int while trying to get file ‘servers.def’, error 0x20000004 has occured, try 1
18:44:02 min/int tried 1 servers to get file ‘servers.def’, but failed (0x20000004)
18:44:02 min/fil GetNewerStampedFile:GetFileWithRetry failed: C:\WINDOWS\TEMP_av_proI.tm~a03112\onefile, servers.def, error: 0x20000004
18:44:02 min/pkg Tried to download servers.def but failed with error 0x20000004.
18:44:17 min/gen Err:Cannot connect to download78.avast.com (unknown:80).
18:45:02 nrm/pkg Transferred files: 0
18:45:02 nrm/pkg Transferred bytes: 0
18:45:02 nrm/pkg Transfer time: 0 ms
18:45:02 vrb/fil NeedReboot=false
18:45:17 min/gen Return code: 0x20000004 [Cannot connect to download78.avast.com (unknown:80).]
18:45:17 min/gen Stopped: 12.12.2006, 18:45:17
Interesting … the log looks just about identical to the one you posted two months ago.
Perhaps valuable help might be forthcoming from kubecj of the avast team to explain the log and the recurrent nature of the the problem.
Thanx for having a look anyways.
Please try the
proxycfg -d
command and also check that avast! is configured to use direct connection (no autodetection or proxy configured in Program Settings…/Updates (Connections)/Proxy…).
The log means what it says. No connection to outside world for avast.setup. Most possibly misconfigured firewall/proxy.
Please explain how to use the code… proxycfg -d
The firewall is configured properly,but I do not know how to configure the/a proxy.
daddymo3
are you still seeing the automatic update error popping up or has it just gone away?
Chocholo was asking you to run that command in a command line (oldspeak MS-DOS) window. It would display whether you have a proxy or direct connection to the Internet.
One other question …
when the automatic update error was occurring did you make any change to your network configuration between the automatic update error pop-up and your successful manual update?
yes, I am still seeing the error.
sorry don’t know how to run a comand line in DOS.
direct connect,no proxy,at least that’s what I have it set to.
Start → Run… → cmd
You’ll see a comand line in DOS, then type in: proxycfg -d
Press Enter.
daddymo3
sorry to persist … but could you please answer my “one other question” above?
Many thanks.
Sorry for not responding…No changes were made to anything.It was working before I went on vacation,one week later,not working.
I’ll get back to you later in regards to the DOS thing.
daddymo3
thanks for your reply - it was rather what I expected it to be.
May I ask the favor of an update from you in a few more days on whether this problem is continuing.
My best guess (I could be wrong - it would certainly not be the first time) is that the problem you are experiencing will go away in a few more days. It may come back again in a month or two - not easy to predict.
I look forward to your update.
Why you think it will go away in a few days?
Gremlins ;D
To update troubles, basically, check:
-
If the servers.def file is corrupt or 0KB (C:\Program Files\Alwil Software\Avast4\Setup\servers.def).
You can try and download the servers.def file, http://files.avast.com/iavs4x/servers.def and replace the one in the avast setup folder. -
If your subscription allows the update right now (i.e., if it is not expired).
-
If your firewall settings and allow avast.setup to connect.
If you’re not sure, just turn off your firewall (to be sure the update failure is not due to it).
Maybe you should ‘remove’ avast.setup entry, try to update, receiving a new alert from the firewall, allowing it and checking it to remember. -
Check your proxy settings into avast!:
Left click the avast icon > Settings
Update (Basic) > Details > Proxy
Make sure your browser is not set to “Work Offline” (this option is generally in the File menu).
If it doesn’t help, try switching from “Auto-detect” to “No proxy” (I’m assuming you’re not connecting to the Internet via proxy).
You can run proxycfg -d in a DOS window to make your computer connect direct, without proxy. You can run proxycfg -h for help.
Tech,
I know you are not a developer of avast but … just applying some logic.
The user has stated - this time round on the problem and almost exactly 2 months ago for the exact same problem that manual VPS updates work fine.
If manual updates work fine (and the user has told us that no changes are made between startup and performing a successful manual update) then how:
can the servers.def file be corrupted?
can the firewall permissions be preventing access for the automatic update but not the manual update?
can a proxy (that the user says this time and last time does not exist) only affect the automatic update?
daddymo3
Why do I think it might just go away?
Because you told us that you did nothing and the problem just started happening.
Because you had an identical problem exactly 2 months ago and although you followed Tech’s advice to re-download the servers.def file I doubt that really did anything to fix the problem then and …
see my comments here:
http://forum.avast.com/index.php?topic=25511.msg208686#msg208686
It can. It does. avast will download the entire file, something happens, the download get corrupted…
I see the parent application, any different rule, a firewall update…
Well… I think not.
Sorry Tech, but your suggestions - to me - stretch credibility.
can the servers.def file be corrupted?It can. It does. avast will download the entire file, something happens, the download get corrupted…
Sorry, if the user can do a manual update … I’m not buying that story.
can the firewall permissions be preventing access for the automatic update but not the manual update?I see the parent application, any different rule, a firewall update…
It is the same application in avast doing the connection for both, parent application is irrelevant … can’t buy that one either.
I’m not here to share credibility. If there is a problem, there is a problem.
Neither I’m defending avast. Just I don’t know what is happening. The only difference between manual and auto updates should be that avast.setup is spawned directly by the application from which you invoked the update. In the auto update case, however, avast.setup is executed by ashServ.exe, the avast service. The service runs under the LocalSystem account, i.e., not under the account the user is currently logged on.
This changed in the latest build. In the previous versions, all avast.setup’s were being executed by aswUpdSv.exe - the ‘avast iAVS4 Control Service’. This service is used only when invoking manual updates from non-administrative accounts.