In Microsoft Internet Information Services (IIS) 6.0, the value in the ETAG field is unexpectedly updated when you modify a metabase property.

Note A Web server that is running Microsoft Windows Server 2003 Service Pack 1 (SP1) returns a response to clients. This response includes an ETAG value. A Web server also returns an ETAG value to clients when you have installed the hotfix that is described in the following Microsoft Knowledge Base article:

Back to the top

This problem occurs if you modify one or more of the following metabase properties in IIS 6.0:

•	HttpPics
•	DefaultDoc
•	DefaultDocFooter
•	EnableDocFooter
•	ScriptMaps
•	MimeMap
•	EnableDefaultDoc
•	AspCodePage
•	AspEnableApplicationRestart

If the FTP Publishing Service, the Simple Mail Transfer Protocol (SMTP) service, or the Network News Transfer Protocol (NNTP) service is installed on a computer that is running IIS 6, IIS 6 monitors the metabase and updates the value in the ETAG field when one of the properties that is listed in this section are modified.

Back to the top

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To install this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or a later Windows Server 2003 service pack installed on the computer.

Restart requirement

You do not have to restart the 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.

Microsoft Windows Server 2003 Itanium-based Editions

   Date         Time   Version        Size     File name     Platform
   ------------------------------------------------------------------
   19-Jul-2005  19:42  6.0.3790.2490  622,592  Infocomm.dll  IA-64

Microsoft Windows Server 2003 x64 Editions

   Date         Time   Version        Size     File name
   --------------------------------------------------------
   19-Jul-2005  19:42  6.0.3790.2490  338,944  Infocomm.dll     

Microsoft Windows Server 2003 for x86-based computers

   Date         Time   Version        Size     File name
   --------------------------------------------------------
   19-Jul-2005  02:47  6.0.3790.2490  235,520  Infocomm.dll 

Back to the top

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 2.

Back to the top