Avast start up problem

[Vlk]

Thanks.

What is the reported version of the VPS file (the virus DB)?

Also, could you actually try to delete the VPS file (<avast4>\data\400.vps) and invoke the iAVS update? I'd like to be sure that the VPS file is not corrupted in any way...

Thanks,
Vlk

[Tommycat]

What is the reported version of the VPS file (the virus DB)?

Do you mean this?
(current version 0309-6)

[Tommycat]

Ok i think i've done something wrong.
I deleted 400.vps and then try to update.
Vps was allready up to date it said, so i thought that maybe i should restart my computer.
So i did.
Now avast doesn't work at all.
I tried to manually open ashserve but then i get no icon.

[Vlk]

No problem. You can download the file here: http://cat.asw.cz/~vlk/400.vps . That's the correct version so you don't have to try the update trick any more...

Thanks
Vlk

[Tommycat]

Ok thx it works again!
If the problem happends again i will report it here.
Thx for your help so far!!!

[Lisandro]

If the problem happends again i will report it here.

Thanks Tommycat for your patience...  
Thanks Vlk for your wisdom  

[Tommycat]

Ok i have terrible news  :'(
Avast on-acces didn't work today
Just when i wanted to post here to say that all was great  
Here is the log hope it helps

aswServ 000781035 ms: Calling avworkInitialize
aswServ 000038781 ms: Calling avworkInitialize
aswServ 000045012 ms: Calling avworkInitialize
aswServ 000175539 ms: Calling avworkInitialize
aswServ 000254256 ms: Calling avworkInitialize
aswServ 000313334 ms: Calling avworkInitialize
aswServ 000339547 ms: Calling avworkInitialize
aswServ 000396472 ms: Calling avworkInitialize
aswServ 000433168 ms: Calling avworkInitialize
aswServ 000436214 ms: *** avworkInitialize FAILED!! Error code is 42003
aswServ 006647846 ms: Calling avworkInitialize
aswServ 003031892 ms: Calling avworkInitialize
aswServ 004367216 ms: Calling avworkInitialize
aswServ 004388777 ms: Calling avworkInitialize
aswServ 004406674 ms: Calling avworkInitialize
aswServ 004426856 ms: Calling avworkInitialize
aswServ 000038278 ms: Calling avworkInitialize
aswServ 000044363 ms: Calling avworkInitialize
aswServ 000036968 ms: Calling avworkInitialize
aswServ 000045352 ms: Calling avworkInitialize
aswServ 000038801 ms: Calling avworkInitialize
aswServ 000037657 ms: Calling avworkInitialize
aswServ 000038951 ms: Calling avworkInitialize


But i don't think it's such a problem because it didn't happen for 10 days or so but i hope there is a solution.

Thx Rob

[Vlk]

Please upgrade to ver. 4.1.280. It has some extra mechanisms that could help to prevent this problem...

Vlk

[Tommycat]

It allready is ver. 4.1.280

[Chriz]

I'm having a similar startup problem as well. The avast! tray icon shows a red sign over it. If I double-click on it, i get an error message (see attached image):

"avast!: The AAVM subsystem detected a RPC error."
"The operation could not be completed."

I had first tried with the Spanish version, now with the English version. I get the same error message with both of them.

The log viewer shows the following entries in the "Error" category:

12.10.2003 20:16:27   NT AUTHORITY\SYSTEM   540   AAVM - initialization error: AavmStart: avworkInitialize failed, 0000A413.  
12.10.2003 21:36:26   NT AUTHORITY\SYSTEM   544   AAVM - initialization error: AavmStart: avworkInitialize failed, 0000A413.  

I'm using the latest version (downloaded today), and even registered as home user, and entered the registration code.

I'm running an Windows 2000 Professional (Spanish) on an Athlon with 128 MB of RAM.

Startup and manual scanning both seem to work fine; it's the resident shield that doesn't start.

Need more info?

[Lisandro]

I suggest a search for RPC error in avast! foruns.
Lots of foruns have discussed this in the past.
Like Vlk, version 4.1.280 must work ok with them.
Are the RPC service starting automatically with the OS?
What firewall and spyware were installed?

[Chriz]

I suggest a search for RPC error in avast! foruns.
Lots of foruns have discussed this in the past.
Like Vlk, version 4.1.280 must work ok with them.
Are the RPC service starting automatically with the OS?
What firewall and spyware were installed?

Hum, I *did* search for "rpc error" before I posted; no results were returned.

I did not know RPC was a separate service; I'll check if it is being started as soon as I get back to that computer.

I'm not using any firewall/spyware software (however, ZoneAlarm has been recently uninstalled on that computer).

Thanks for the quick reply. I'll post as soon as I have details.

Chriz.

[Chriz]

Well, I checked and the RPC service is running. Another service, called "RPC Locator" was not started, but starting it does not make any difference. I still get the same error.

Regards,
Chriz

[Lisandro]

Well, I checked and the RPC service is running. Another service, called "RPC Locator" was not started, but starting it does not make any difference. I still get the same error.

Regards,
Chriz

I don't have an English OS so I cannot find the specific service RPC Locator (I suppose it is the Alocator Remote Procedure Call and manages the data base names RPC)  
I suggest you open the properties of the "normal" RPC service and see if avast! is named as a dependent service (i.e., if avast is listed at the dependent services of RPC).
Maybe another test, try to reinstall ZoneAlarm and see if this correct the error. I have ZA too and everything is working fine with avast.  :'(

[Angelica]

Hey Guys,

I am having the same start up problem as Chris has - The RPC unable to start up issue.....Adding to that error message, I also receive a message from Visual C++ library about runtime error shut down request....  Any updares on fixes?

Are you guys having or had this problem b4?

Also Any solution yet?

Please post a response to my questions soon for I am not quite sure if avast is protecting my pc at this time........!!??

Angelica