Unable to automatcially update virus database

[X]

Since the last update of Avast my system is unable to automatically update the virus database, each morning I receive the red box error notice stating an error occurred.  However I am able to update if I do it manually.  Is there a fix for this? I've attached the Avast error log file, hopefully it will provide some clues.

[TedNelly]

Have you tried a repair of Avast
Start/Control Panel/Add Remove Programs/Avast/Change remove
Scroll down to Repair ( You must be online to do this) /Reboot

[Lisandro]

Each morning I receive the red box error notice stating an error occurred.

Just change (or add) AlwaysConnectedWaitSeconds value into the [InetWD] section of avast4.ini file.
You could set the number of seconds to wait before attempting to update. The default is 30 but it may not be enough in some DSL systems. In this case, you can try increasing this e.g. to 60 (1 minute). That should be enough.

More details here: http://forum.avast.com/index.php?board=2;action=display;threadid=1647

[DavidR]

Interesting reading in your Log the detections of the Outpost Pro anti-spyware plug-in signature database files.

The plug-in is from Lavasoft and is based on AdAware, so if you have AdAware and or any other anti-spyware tools this plug-in could be redundant, not only that it scans lots of files on boot and as such avast will also scan those files so your boot times could be very long. I have long since disabled this plug-in as I have adequate anti-spyware protection in the form of AdAware, Spybot S&D, SpywareBlaster, even thought they are only set to on-demand on my system. I also use an alternative to IE (firefox or opera) that with activeX, BHOs and being integrated into the OS is highly susceptible to malware.

[X]

Just home for lunch and see I have replies, thanks to everyone! 

Have you tried a repair of Avast

No I haven't, I will try this if the other suggestions do not fix my issue.

Just change (or add) AlwaysConnectedWaitSeconds value into the [InetWD] section of avast4.ini file.

Thank you I will try this tonight when I'm home from work for the evening!

Interesting reading in your Log the detections of the Outpost Pro anti-spyware plug-in signature database files.

The plug-in is from Lavasoft and is based on AdAware, so if you have AdAware and or any other anti-spyware tools this plug-in could be redundant, not only that it scans lots of files on boot and as such avast will also scan those files so your boot times could be very long. I have long since disabled this plug-in as I have adequate anti-spyware protection in the form of AdAware, Spybot S&D, SpywareBlaster, even thought they are only set to on-demand on my system

Excellent suggestion, sounds like my system is configured similarly to yours!  I also have Spybot S&D as well as SpywareBlaster so I will disable this as well and see if it shortens my boot times any.  Thanks for speaking up!

[DavidR]

Your welcome, I think you will see a difference the Scanned count: figure in standard shield detailed view for me is less than 100 after the avast icon stops rotating after boot.

[X]

Ok took a little extra time to look at my avast4.ini file. 

This is what I see in the file for [InetWD]:

[InetWD]
UseRAS=0
AssumeAlwaysConnected=1

I'm assuming the part I've highlighted in red is what I'm supposed to change but it's already set to "Assume Always Connected", should I still change it to read

AlwaysConnectedWaitSeconds

and change the value to 60?  Just want to make sure before I change the value. 

[Lisandro]

AssumeAlwaysConnected=1
is a different setting then AlwaysConnectedWaitSeconds.
You need to add this:
AlwaysConnectedWaitSeconds=60

So, your avast4.ini file will have these two lines:
AssumeAlwaysConnected=1
AlwaysConnectedWaitSeconds=60

Boot 

[X]

Thanks Tech!  The line's been added, now we'll see if she updates correctly tomorrow morning. 

[Lisandro]

Thanks Tech!  The line's been added, now we'll see if she updates correctly tomorrow morning. 

You don't have to wait until tomorrow... just boot 

[X]

D'oh!  Of course I coulda rebooted!   

Anyway it didn't update this morning so I'll be trying the repair next.  In case it helps, I did a screen print of the error message I've been receiving when it fails to automatically update and have attached it.

[Lisandro]

Anyway it didn't update this morning so I'll be trying the repair next.  In case it helps, I did a screen print of the error message I've been receiving when it fails to automatically update and have attached it.

Do you use any firewall?
Can you download servers.def file (http://files.avast.com/iavs4x/servers.def) and replace the one here C:\Program Files\Alwil Software\Avast4\Setup\servers.def ?

[DavidR]

Anyway it didn't update this morning so I'll be trying the repair next.  In case it helps, I did a screen print of the error message I've been receiving when it fails to automatically update and have attached it.

This looks like the firewall (which one ?) blocking avast.setup rather than the original problem of:

12/22/2005 11:41:25 PM   SYSTEM   1856   Function setifaceUpdatePackages() has failed. Return code is 0xC0000142, dwRes is C0000142. 
12/22/2005 11:41:25 PM   SYSTEM   1856   An error has occured while attempting to update. Please check the logs.