Article ID: 329459 - Last Review: November 21, 2006 - Revision: 3.4 FIX: IIS Does Not Refresh the File Cache for Non-Virtual Root Directories
This article was previously published under Q329459 On This PageSYMPTOMS When you change files in a non-virtual root (VROOT)
directory, Internet Information Services (IIS) does not flush the cache.
Therefore, client users who gain access to these pages do not see the changes.
CAUSE This problem occurs because IIS directory monitors only
VROOT directories (VROOTs that are defined in the IIS metabase). If a filter
(URL_MAP filter) changes the physical path of a file to a path that is not
defined in IIS as a VROOT path, the IIS code automatically tries to cache the
file contents. Because IIS is not monitoring the file's new directory, if the
file changes, IIS does not flush the cache to refresh the file. RESOLUTIONService Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:260910
(http://support.microsoft.com/kb/260910/EN-US/
)
How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
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 typical 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 fix has the file attributes (or later) 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 ------------------------------------------------------------ 23-Sep-2002 22:39 5.0.2195.6048 333,584 Asp.dll 23-Sep-2002 22:39 5.0.2195.3649 299,792 Fscfg.dll 23-Sep-2002 22:39 5.0.2195.5255 8,464 Ftpctrs2.dll 23-Sep-2002 22:39 5.0.2195.5255 6,416 Ftpmib.dll 23-Sep-2002 22:39 5.0.2195.5255 9,488 Httpmib.dll 23-Sep-2002 22:39 5.0.2195.5991 13,584 Infoadmn.dll 23-Sep-2002 22:39 5.0.2195.5991 246,544 Infocomm.dll 23-Sep-2002 22:39 5.0.2195.6036 62,736 Isatq.dll 23-Sep-2002 22:39 5.0.2195.5255 7,440 W3ctrs.dll 23-Sep-2002 22:39 5.0.2195.6067 349,456 W3svc.dll STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Microsoft Windows 2000 Service Pack 4. MORE INFORMATIONFor additional information about how
to obtain a hotfix for Windows 2000 Datacenter Server, click the article number
below to view the article in the Microsoft Knowledge Base: 265173
(http://support.microsoft.com/kb/265173/EN-US/
)
Datacenter Program and Windows 2000 Datacenter Server Product
| Other Resources Other Support Sites
CommunityArticle Translations |






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email

Back to the top