Internet Explorer cannot display the web page. Operation aborted.and frequently the well known full page display
The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.
The common factor in the problem reported involved the presence of SiteMeter code, on the blogs reported. All of my blogs, listed above, have that code too.
Given the choice of having a blog accessible only under Firefox (and trackable), or having a blog accessible under both Firefox and Internet Explorer (and not trackable), I chose the latter and removed my SiteMeter code. This was not a difficult task, I just cut the code from the widgets in the footer of each blog. And I saved the removed code, which was a good thing.
I simply edited the page element in the footer, at the bottom of the blog. Wherever your SiteMeter widget is, if you put the code into a page element, you can do the same.
<noscript><a href="http://s17.sitemeter.com/stats.asp?site=s17nitecruzr" target="_top">
<img border="0" alt="Site Meter" src="http://s17.sitemeter.com/meter.asp?site=s17nitecruzr"/></a></noscript><!-- Copyright (c)2006 Site Meter -->
and changed that to
<!-- Site Meter --> <!-- Copyright (c)2006 Site Meter -->
In the process of writing a problem report to SiteMeter, I needed an exact copy of the content of the popup error. Attempting to reproduce the error, I went back to my home blog (which I care about least, of the 3 above), and added the code back. Having reloaded the code, I reloaded the blog under Internet Explorer, and noted an oddity - no error popup.
I returned to my SiteMeter Statistics list, and observed that my visit was now visible in the visitor log. An hour later, I am now refreshing the "Who's On Your Site" display, and I see all 3 blogs represented again. Some entries include Internet Explorer, and multiple pages viewed, indicating successful loading of the blog.
> > (Update 8/2 13:00): SiteMeter states that they have resolved the problem.