Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Crazyfroggy on September 01, 2004, 08:57:00 PM
-
Hi,
I've just reinstalled my laptop (IBM T23) with Win XP Pro SP1a then SP2 (from the admin version, the Big One).
When the system boots, the resident agent doesn't start and says "AAVM has encountered an RPC error". :-\When I start Avast! manually, everything goes fine. ???
Can you help me ?
Cheers
-
Generally, RPC errors are corrected by Control Panel > Add/Remove applications > avast > repair function.
If this does not work, try uninstall/boot/install/boot ;)
-
I also had this happen, it was due to a windows service not being loaded on startup, but the fact that it effected Avast is really bad as it could be used to prevent avast from being effective on the machine.
I borrowed a firends connection to get a big download, and when I booted up to the desktop I had this error in avast, along with no connectivity. Well I had disabled the dhcp service as I never use it normally, and when I enabled it everything was fine. However due to Avast's dependency on rpc, AVAST FAILED due to rpc not being able to contact the dhcp service.
The fact that Avast depends on RPC is a very possible local security exploit.
-
Hi,
I've just reinstalled my laptop (IBM T23) with Win XP Pro SP1a then SP2 (from the admin version, the Big One).
When the system boots, the resident agent doesn't start and says "AAVM has encountered an RPC error". :-\When I start Avast! manually, everything goes fine. ???
Can you help me ?
Cheers
Just a thought, did you use a stand alone version of XP for the re-install or IBM's disc?
IBM are not alone in making some modifications to firmware inside their machines that can cause problems if their own restore/system discs aren't used.
This link also reports that IBM are advising not to install SP2 until it has produced a customised version.
http://news.bbc.co.uk/1/hi/technology/3557952.stm
-
The fact that Avast depends on RPC is a very possible local security exploit.
What do you mean?
Can you rephrase, please? ::)
-
Thank you all,
Technical - I've tried repair Avast!->reboot : doesn't really work. I'll do a clean install tonight.
Bitzenzeus, I think you may have it right, I will reenable my DHCP services shall the clean install failed.
Inthewildteam, I did a clean install of WinXP (not from the IBM CDS or recovery partition) then reinstalled all IBM utilities at the top of it. Everything works fine but I'll document myself a bit more on the IBM/SP2 issues. Thanks for the info.
I just wanted to THANK YOU very much indeed for your help. I will keep the forum posted tonight.
Cheers
-
The fact that Avast depends on RPC is a very possible local security exploit.
What do you mean?
Can you rephrase, please? ::)
Don't roll your eyes at me 8)
I've already brought up this issue in a previous thread, as described in my message, if you can cause rpc hang, even by preventing the automatic loading of a service needed that is called apon by rpc, avast doesn't work correctly, and this dependency on rpc could be a local security issue.
To be effective in the security field you have to see both sides of the issue
-
This is ridiculous. The whole thing is caused by the absolutely unsuitable error message "encountered an RPC error". In fact, in 99.999% cases, this is not related to RPC. It's simply caused by the fact that the avast service is not running (or working). Again, not the RPC service, the "avast! antivirus" service.
avast per se does not use any "RPC" (remote-procedure) functionality...
Vlk
-
This is ridiculous. The whole thing is caused by the absolutely unsuitable error message "encountered an RPC error". In fact, in 99.999% cases, this is not related to RPC. It's simply caused by the fact that the avast service is not running (or working). Again, not the RPC service, the "avast! antivirus" service.
avast per se does not use any "RPC" (remote-procedure) functionality...
Vlk
Thanks for posting Vlk... I felt not able to understand all technical concepts here.
-
This is ridiculous. The whole thing is caused by the absolutely unsuitable error message "encountered an RPC error". In fact, in 99.999% cases, this is not related to RPC. It's simply caused by the fact that the avast service is not running (or working). Again, not the RPC service, the "avast! antivirus" service.
avast per se does not use any "RPC" (remote-procedure) functionality...
However I can reproduce this error when I want to just by preventing the dhcp service from loading automatically with a cat5 cable plugged into my network card, but otherwise Avast works fine.
-
Hi guys,
Thank you very much for your help, just did a clean install and Avast is now running like a charm. ;D
I've read some comments regarding RPC. FYI, on my machine, RPC is completely disabled and I never reenabled it. In my case, it's not the cause of the error msg.
Thanks again
-
*
Crazyfroggy - glad you got it fixed and Welcome to the forums! :)
*
-
On my machine, RPC is completely disabled and I never reenabled it.
We must be talking about different things.
Without RPC you won't have even Windows starting or working. RPC is a vital service, if you shut it down, your computer will shut down ;)
-
Technical
It's disabled on my computer to and this baby is humming! :)
-
Again, RPC Locator is not the same as RPC.
Remote Procedure Call (RPC) Locator manages the RPC name service database and is different from Remote Procedure Call (RPC), which provides the endpoint mapper and other miscellaneous RPC services.
Without RPC you do not have Windows. Just try to stop it... ;D
-
Here you'll have a list of windows services:
http://www.blackviper.com/WIN2K/servicecfg.htm
Remote Procedure Call (RPC)
This service is rather vital. Practically everything depends on this service to be running. This is also the only service that you should not (and will not) disable via the Services MMC. If you do, your computer may (will) become unbootable AND you cannot place this service back to automatic to fix it. Leave it on Automatic and do not change it. If, for whatever reason, the service became disabled and you can no longer boot your system, please read the information here for a way to fix it.
Recent virus activity has prompted me to post additional information regarding Remote Procedure Call and automatic shutdowns. Please ensure you read all the information I have available to ensure you are not affected by this latest internet threat.
Default 2000 Server: Automatic
Default 2000 Pro: Automatic
Safe Setting: Automatic
Dependencies (what service Remote Procedure Call (RPC) needs to function properly):
None
What other services require Remote Procedure Call (RPC) to function properly:
Background Intelligent Transfer Service
COM+ Event System
System Event Notification
Background Intelligent Transfer Service
Distributed Link Tracking Client
Distributed Transaction Coordinator
Message Queuing
Fax Service
IIS Admin Service
FTP Publishing Service
Simple Mail Transport Protocol (SMTP)
World Wide Web Publishing Service
Indexing Service
IPSEC Policy Agent
Logical Disk Manager
Logical Disk Manager Administrative Service
Logical Disk Manager Administrative Service
Message Queuing
Messenger
Network Connections
Print Spooler
Fax Service
TCP/IP Print Server
Protected Storage
IIS Admin Service
FTP Publishing Service
Simple Mail Transport Protocol (SMTP)
World Wide Web Publishing Service
Message Queuing
Wireless Configuration
Removable Storage
RIP Listener
Routing and Remote Access
Task Scheduler
Telephony
Fax Service
Remote Access Auto Connection Manager
Remote Access Connection Manager
Internet Connection Sharing
Remote Access Auto Connection Manager
Telnet
Windows Installer
Windows Management Instrumentation
Wireless Configuration
As you can see, windows won't work without it... ;D
Remote Procedure Call (RPC) Locator
Manages the RPC name service database. I have not found a reason to keep this service running. However, if something on your network breaks after you disable this service, put it back to manual. About 1.2 MB of RAM is in use with this service.
Default 2000 Server: Manual
Default 2000 Pro: Manual
Safe Setting: Manual
Dependencies (what service Remote Procedure Call (RPC) Locator needs to function properly):
Workstation
What other service require Remote Procedure Call (RPC) Locator to function properly:
None
-
Thank you Technical.
By changing my settings for Remote Procedure Call (RPC) Locator from Disabled to Manual, you've fixed a problem that has plagued me for a long time. See this Thread (http://forum.avast.com/index.php?board=9;action=display;threadid=6957;start=15).
Apparently this service isn't needed as long as everything is perfect however, When a problem arrises this service is needed to repair the individual program or service.
I wil be informing microsoft of this finding and see what they have to say. Since MS is aware of a problem, but didn't have an answer, Technical should get a paycheck from them. ;D
-
Technical should get a paycheck from them. ;D
Who will be the first of the list? ;D
I think patience will all the time... we could give up before we discover the error.
Well, at least, avast forums are being useful for the users 8)