Avast 2014 IE Plugin Error: 8070000c

Avast Free Antivirus / Premium Security
1

Good day,

On a recent website, I started having issues with Avast Plug-in for IE.

In the following _watcherReady scriptblock, I receive the “Could not complete the operation due to error 8070000c.”
The stack for this error is: “Error: Could not complete the operation due to error 8070000c.\n at _watcherReady (Unknown script code:5:13)”

Error occurs at the line: avastBHO.SERPWatcherOnReadyState();

{
var _alreadyRunned = false;
setTimeout(function _watcherReady() {
if (window.document.readyState === “complete” && !_alreadyRunned) {
avastBHO.SERPWatcherOnReadyState();
_alreadyRunned = true;
} else {
timer = setTimeout(_watcherReady, 1000);
}
}, 1000);
};

Call stack:
Main frame
_watcherReady

I’m a bit disappointed by this… my current work around is to close the offending tab, clear cache and cookies, reopen the URL and THEN I am able to continue in the particular website.

For reasons, I’m predominantly using IE. However, I tested in Chrome and the issue does not present itself.

Below is the information regarding IE:

Version: 11.0.9600.17207
Update Versions: 11.0.10 (KB2962872)
Product ID: 00150-20000-00003-AA459

Avast Plugin Information:
Name: avast! Online Security
Publisher: AVAST Software a.s.
Type: Browser Helper Object
Architecture: 32-bit and 64-bit
Version: 9.0.2021.112
File date: ‎Thursday, ‎July ‎10, ‎2014, ‏‎5:34 PM
Date last accessed: ‎Today, ‎July ‎24, ‎2014, ‏‎7:34 PM
Class ID: {8E5E2654-AD2D-48BF-AC2D-D17F00898D06}
Use count: 97
Block count: 3
File: aswWebRepIE64.dll
Folder: C:\Program Files\AVAST Software\Avast

I hope this report might assist in a resolution to this issue that seems to be affected IE users exclusively.

Thank you,
Heidi

2

Heidi,

thanks for the report… We will need to reproduce it on our side.

Thank you!

3

I have exactly the same problem testing an application on IE from Visual Studio 2013.
Every time that I switch to a new page in the application I get the following error displayed:

Unhandled exception at line 20, column 13 in script block
0x800a0005 - JavaScript runtime error: Invalid procedure call or argument
If there is a handler for this exception, the program may be safely continued.

and the block containing Line 20 is:

{
var _alreadyRunned = false;
setTimeout(function _watcherReady() {
if (window.document.readyState === “complete” && !_alreadyRunned) {
avastBHO.SERPWatcherOnReadyState();
_alreadyRunned = true;
} else {
timer = setTimeout(_watcherReady, 1000);
}
}, 1000);
};

Line 20 is avastBHO.SERPWatcherOnReadyState();

Please help, this is incredibly frustrating.

4

Hi

Sorry speak German tranclate über google

remedy
You download Avast version 9.0.2019 from the following URL

http://www.oldapps.com/de/avast_antivirus.php

You install Avast version 9.0.2019

Separate Internet connection, the update can not get

Then in folder

C: \ Program Files \ AVAST Software \ Avast \

The aswWrcIEBroker32.dll Save file in another folder

Connecting to the Internet

Make update to Avast version 9.0.2021

then reboot

then Avast user interface

Setting —> Error Handling —> Avast disable self-protection

Then in folder

C: \ Program Files \ AVAST Software \ Avast \

The aswWrcIEBroker32.dll file with the backup version of Avast 9.0.2019

replace current

Then re-enable it as above Avast self protection

Internet Explorer should no longer report the error

greet

Martin

5

Hello,
I can confirm that workaround described by Nordlicht works correctly.

Samuel Cizkovsky

6

I recently needed to work with the IE Developer Tools and am now getting repeated pop-ups that avastBHO.SERPWatcherOnReadyState() is an Invalid procedure call or argument. Aside from back-leveling aswWrcIEBroker32.dll, is there another way to stop these errors?

Thanks, Norbert

7

You can always remove the Browser Protection ( AOS ) click to uninstall avast and choose change, on the following screen untick browser protection and complete with reboot.

8

This should be fixed in the 2015 version of avast!.
The problem appears to be fixed in the beta version currently being tested. :slight_smile: