Perhaps this will help:

http://support.microsoft.com/support/kb/articles/Q247/3/89.ASP

-----Original Message----- From: Lyons, Jim [mailto:jimbo@ti.com] Sent: Monday, March 19, 2001 12:13 PM To: 'theffron@wisedata.com'; 'toasters@mathworks.com ' Subject: RE: ASP caching

This is a setting on the IIS server. In IIS 4.0, you set this in the application configuration for apps that are set to run in a separate memory space. This is under the 'Process Options' tab. You can set it to cache ASP or not.

We run some apps that cache and some that don't on the same IIS servers with the virtual directories located on netapps. I'm not sure where this is in 5.0, but look around, I am pretty sure this is not a netapp problem.

Jim

-----Original Message----- From: Jean-Christophe Smith [mailto:jsmith@publichost.com] Sent: Monday, March 19, 2001 1:37 PM To: 'toasters@mathworks.com ' Subject: ASP caching

We have a cluster of Windows 2000 servers running IIS 5.0, content lives on a NetApp F720 running OnTap Release 5.3.7R2. Our customers use FTP to upload their web pages.

IIS is caching ASP(active server pages), customers will make changes to their ASP files and try to view them(view IIS) and they see the older pages. I read about this issue entitled "5.3 Active Server Page Caching" in the NetApp document "Integrating a NetApp Filer with Microsoft IIS". I understand it is an issue with CIFS change/notify events and the way IIS was designed.

Does anybody know a way of fixing this? or maybe way to increase the change/notify events, or...

For now, we have to restart IIS when changes are made.

Maybe I could write a program to manually induce change/notify events?

Thanks, Jean-Christophe Smith jsmith@publichost.com VitalStream.com