subscribe to the RSS Feed

Saturday, May 19, 2012

Internet Explorer 6.0: Internet Explorer may appear to stop responding when requesting many objects

By TechSupport


SUPPORT PROBLEM: Internet Explorer may appear to stop responding when requesting many objects

Applications Supported:

COPYRIGHT NOTICE: (c) 2007 Microsoft Corporation. All rights reserved.

SUPPORT SOLUTION:
When Microsoft Internet Explorer makes many requests for
objects, it may stop responding (hang). Requests to the current
Web server may not be completed, and the Internet Explorer window displays an
arrow-hourglass pointer.When this problem occurs, images may not
appear as expected, and a message may appear in the status bar at the bottom of
the window that there are a certain number of “items remaining”, or it
may say “Done”.This problem may occur if Internet Explorer sends many
HTTP requests, and then aborts many of those
requests. When this problem occurs, HTTP requests to the same Web server do not
succeed.Note When you use other Web servers, HTTP requests work
correctly.Download information
2, ‘resolution’);
Internet Explorer 6 SP1 for Windows XP, Windows 2000, Windows NT, and Windows Millennium Edition
3, ‘resolution’);

The following file is available for download from the Microsoft Download Center:Collapse this imageExpand this imageDownload
the q818506.exe package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=6AD4034B-22DF-4100-B211-5CF7E0EAC5E1&displaylang=en)

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 

(http://support.microsoft.com/kb/119591/
)
How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
Internet Explorer 6 for Windows Server 2003
3, ‘resolution’);

The following file is available for download from the Microsoft Download Center:Collapse this imageExpand this imageDownload
the WindowsServer2003-KB818506-x86-ENU.exe package
now.
(http://www.microsoft.com/downloads/details.aspx?FamilyID=680efe51-bb4f-48c0-95b4-bff050265c8a&DisplayLang=en)

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 

(http://support.microsoft.com/kb/119591/
)
How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
File information
3, ‘resolution’);
Windows Server 2003 Version
4, ‘resolution’);
Non-Windows Server 2003 Version
4, ‘resolution’);
Microsoft has
confirmed that this is a problem in Microsoft Internet Explorer 6 Service Pack
1.
Typically, when Internet Explorer aborts an HTTP request,
the page no longer has to have a reference for that resource (such as an image, a
JScript (.js) file, an HTML component (.htc) file, or a Cascading Style Sheet
(.css) file). This problem may occur when you rapidly open and
close many nodes of a DHTML treeview-like control. The problem occurs more
frequently when Internet Explorer is set to look for newer versions on every
visit to the Web page because this generates more HTTP requests. (Typically, these requests are “get”
requests).Other factors that contribute to HTTP traffic may also
generate more HTTP requests. These factors include setting the cache attribute
and network latency. Network latency contributes to the problem because there
is a greater chance of aborting an HTTP request.If you raise the
connection limit per server, you can delay the problem. The problem occurs
because Internet Explorer may occasionally lose HTTP connections internally.
Because 2 is the standard connection limit for HTTP 1.1, the problem occurs
later if you raise the connection limit.Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

For File Repair and Data Recovery, visit File Repair / Data Recovery