IE cannot open the site...Operation aborted

[Anonymous]

I've been trying to search the web for an answer to this
problem. It seems like a lot of people are experiencing
it, but nobody knows how to fix it.

When I try to access SOME sites, I get the following
message:

Internet Explorer cannot open the internet site "...."
Operation Aborted.

The weird thing is that the page actually loads behind
this error. However, it will not let me interact with the
site until I acknowlege the error. But if I acknowlege
the error, the website goes away. If I fiddle with the
back and forward buttons, I can cometimes coax it into
functioning normally. The site it occurs on all the time
for me is http://pittsburghpenguins.com

But that is not the only site it occurs on, and probably
has nothing to do with that site itself.

Any Ideas? Thanks in advance.

 

[JR]

not sure that it will help, but worth a try:
Click tools/internet options/settings/view objects
In this folder, delete everything that does not
say "Installed"....
This solution seems to work in case you have a corrupt
plugin that is used on some but not all websites.
Let me know if it did any good for you.

 

[Guest]

Thanks for the advice, but it didn't seem to change
anything. I am still getting the same error.

 

[anonyomous]

It didn't really help, but thanks for trying. Any other
ideas?

 

[Frank Saunders, MS-MVP IE/OE]

I've been trying to search the web for an answer to this
problem. It seems like a lot of people are experiencing
it, but nobody knows how to fix it.

When I try to access SOME sites, I get the following
message:

Internet Explorer cannot open the internet site "...."
Operation Aborted.

The weird thing is that the page actually loads behind
this error. However, it will not let me interact with the
site until I acknowlege the error. But if I acknowlege
the error, the website goes away. If I fiddle with the
back and forward buttons, I can cometimes coax it into
functioning normally. The site it occurs on all the time
for me is http://pittsburghpenguins.com

But that is not the only site it occurs on, and probably
has nothing to do with that site itself.

Any Ideas? Thanks in advance.

Check for a file named HOSTS with no extension (not Hosts.sam). It may be a
hidden file. Open it with Notepad and remove any line referencing the site.
Or, rename HOSTS to OLDHOSTS

--
Frank Saunders, MS-MVP IE/OE
http://www.fjsmjs.com
Reply to Newsgroup. I won't answer email
Protect Your PC
http://www.microsoft.com/security/protect/

 

[ffdixon]

Like many people, I've read all the posts on this topic without much
help. Why was IE 6 giving cryptic 'Operation Aborted' messages?

I had to solve this problem for a client and, in our case, here's what
was going on.

We had a questionnaire that was a series of 12 web pages. Each time
the user went to the next question, at random times IE would pause in
loading the page, then show the 'Operation Aborted' dialog. It would
occur sometimes on questions 2, 8, and 9, other times on questions 5,
9, and 10, and so on.

I copied all the pages to a local server and tried to reproduce the
problem. No luck, every page would load. The error only occurred
when loading the pages from a remote server. A race problem
perhaps...

When clicking 'Ok' to the error dialog, IE would either display a
blank page or display the standard 'unable to load the page from the
server message' in the page. Clicking IE's refresh button would load
the page fine. Strange.

Upon reloading the page, I noticed IE give the following JavaScript
error when rendering the page

'FerantDHTMLWondow' is undefined

The pages used a large JavaScript library (see http://www.ferant.com/)
to do DHTML windows. The JavaScript line near the top

setTimeout('help = new FerantDHTMLWindow(params);',500);

This line says after 0.5 seconds, instantiate a new
FerantDHTMLWindow() object.

I removed this line and the 'Operation aborted' errors went away. The
latency of loading the pages over the Net triggered a race condition
between page loading and instantiating the FerantDHTMLWindow() object.

The solution that we choose in the end was to increase the timeout
from 500 to 1500 milliseconds. I don't know if this helps others, but
it solve the problem for us.