Article ID: 818408
Article Last Modified on 7/24/2007
APPLIES TO
- Microsoft Internet Explorer 6.0
- Microsoft Internet Explorer 6.0 Service Pack 1
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
If you try to copy a file that is larger than 100 megabytes (MB) to a server location by using the Web Distributed Authoring and Versioning (WebDAV) service, you receive the following error message:
You also receive the following event ID:
Event ID 14800 "Windows was unable to save data for file <file_name
>. The data has been lost. This error may be caused by a failure of your computer or network connection. Please try to save this file elsewhere.
CAUSE
This problem occurs because, during a WebDAV connection, the WinInet function does not break up the data into sufficiently small chunks. As a result, the system cannot allocate a sufficiently large block of kernel pool memory, and therefore the file-copy operation is unsuccessful.
RESOLUTION
Microsoft Internet Explorer version 6 for Windows XP
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Internet Explorer 6 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------------ 03-Mar-2003 17:24 6.0.2800.1172 33,792 Ieuninst.exe 09-Mar-2003 08:42 6.0.2800.1173 26,624 Ieupdate.exe 11-Apr-2003 18:33 4,610 Q818060.inf 11-Apr-2003 18:33 4,689 Q818060_d.inf 11-Apr-2003 18:20 6.0.2800.1187 585,728 Wininet.dll
Microsoft Windows Server 2003
If you experience this problem on a Windows Server 2003-based computer, you can install either Windows Server 2003 Service Pack 1 (SP1) or a hotfix to resolve the problem. After you install the service pack or the hotfix, you must modify the registry to enable the fix.
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
Restart requirement
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, 32-bit versions
Date Time Version Size File name -------------------------------------------------------------- 26-Oct-2004 19:56 6.0.3790.226 626,176 Wininet.dll
Windows Server 2003, Enterprise Edition for Itanium-based Systems
Date Time Version Size File name -------------------------------------------------------------- 26-Oct-2004 19:59 6.0.3790.226 1,505,280 Wininet.dll IA-64 26-Oct-2004 19:56 6.0.3790.226 626,176 Wwininet.dll x86
Additional installation instructions
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
After you install Windows Server 2003 SP1 or the Windows Server 2003 hotfix that is described in this article, you must modify the registry to enable the fix. You can enable the fix on a per user basis or on a per computer basis. To enable the fix, follow these steps:
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Locate the following per user subkey or per computer subkey in the registry.
- For per user configuration, locate the following registry subkey:
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl
Note If the
FeatureControl
subkey does not exist:- Right-click Main, point to New, and then click Key.
- Type FeatureControl as the subkey name, and then press ENTER.
- For per computer configuration, locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl
- For per user configuration, locate the following registry subkey:
- Add the
FEATURE_BUFFERBREAKING_818408
subkey.- Right-click FeatureControl, point to New, and then click Key.
- Type FEATURE_BUFFERBREAKING_818408 as the subkey name, and then press ENTER.
- Add the Iexplore.exe entry.
- Right-click FEATURE_BUFFERBREAKING_818408, point to New, and then click DWORD Value.
- Type Iexplore.exe as the entry name, and then press ENTER.
- Right-click Iexplore.exe, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Add the Svchost.exe entry.
- Right-click FEATURE_BUFFERBREAKING_818408, point to New, and then click DWORD Value.
- Type Svchost.exe as the entry name, and then press ENTER.
- Right-click Svchost.exe, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Add the
Settings
subkey and the BufferBreakingSize entry.- Right-click FEATURE_BUFFERBREAKING_818408, point to New, and then click Key.
- Type Settings as the subkey name, and then press ENTER
- Right-click Settings, point to New, and then click DWORD Value.
- Type BufferBreakingSize as the entry name, and then press ENTER.
- Right-click BufferBreakingSize, and then click Modify.
- Make sure that under Base, Hexadecimal is selected. If it is not, click Hexadecimal.
- In the Value data box, type 02000000, and then click OK.
- Quit Registry Editor.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Windows Server 2003 Service Pack 1.
Keywords: kbhotfixserver kbqfe kbwinserv2003sp1fix kbwinserv2003presp1fix kberrmsg kbqfe kbie600sp2fix kbie600presp2fix kbfix kbbug KB818408