IIS Cache and Updates to Files

We are experiencing an issue where we are trying to do a basic update
of all the content on our web site (static html and PDF files). Within
the last week, two times have we encountered an error where a PDF file
was unable to be written over. We speculate that someone has the file
open in their brower. We tried to kill and restart iis but that did
not work. We had to reboot the server which freed it up. Again, the
problem happened this morning. In my research on the discussion
groups, I came up with the following items that we need to investigate.
While I don't have a fix yet, I thought this would be helpful to
others:

IIS: Access Denied When Trying to Update Files on IIS Computer
http://support.microsoft.com/kb/q191742/

API Opportunity to Fix or Get Around
http://groups.google.com/group/microsoft.public.inetserver.iis/browse_thread/thread/efb71a730d49dfb0/a95d97dc6eb65d02?

lnk=st&q=q191742&rnum=1&hl=en#a95d97dc6eb65d02


Discussion of how to clear the Cache
http://groups.google.com/group/microsoft.public.inetserver.iis/browse_thread/thread/9811981fa325dca1/dcfea8578e3c0be9?

lnk=st&q=iis+Cache+time&rnum=5&hl=en#dcfea8578e3c0be9


Registry Values for HTTP.SYS for Caching
http://support.microsoft.com/?id=820129


DisableStaticFileCache Parameter
http://groups.google.com/group/microsoft.public.inetserver.iis/browse_thread/thread/f1f0b92dd6845c4/cfc5edb6cedb5d3e?l

nk=st&q=iis+Cache+Update+time&rnum=8&hl=en#cfc5edb6cedb5
d3e

How to change it:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/8a887ebb-7094-4702-86a4-eb105d09132d.mspx


Disabling Caching for a specific MIME Type
http://support.microsoft.com/default.aspx?scid=KB;EN-US;247389


Discussion of similar problem
http://www.leafe.com/archives/showFullThd?cMsgNum=78538&cList=profox


Article on third party utility trying to work through is that has a
"retry" paramater.
http://www.netline.ch/support/info/aspcomp/safileup/install_tailor_lockretry.htm

Similar issue with IIS6 and Fresh Content not Showing
http://support.microsoft.com/?id=832139

David
Thu May 04 02:31:33 CDT 2006

Hi. It is very nice of you to share links of your issue investigation to try
and help others, and I appreciate your positive intentions to help.

However, I have to say that most of the links you provided are actually
talking about a variety of *different* issues that have no connection to
what you are asking -- meaning they really don't help but rather confuse the
issue. I'm sure that it is not your intent, but that is the likely outcome.


Basically, if you restarted IIS and the file is still locked, then that
looks to eliminate IIS from being a problem. If IIS had an open handle to
lock the file, by recycling the IIS processes, Windows automatically closes
the handle and the file should no longer be locked on restart.

Personally, I would try using something like Process Explorer from
www.sysinternals.com to determine the process with an open handle to that
file and go from there.

In short, when offering help, you want to be relevant and concise. Anyone
should be able to punch in a search and come up with the links.


--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Marty Zigman" <google@interscore.com> wrote in message
news:1146671599.913079.250460@v46g2000cwv.googlegroups.com...
> We are experiencing an issue where we are trying to do a basic update
> of all the content on our web site (static html and PDF files). Within
> the last week, two times have we encountered an error where a PDF file
> was unable to be written over. We speculate that someone has the file
> open in their brower. We tried to kill and restart iis but that did
> not work. We had to reboot the server which freed it up. Again, the
> problem happened this morning. In my research on the discussion
> groups, I came up with the following items that we need to investigate.
> While I don't have a fix yet, I thought this would be helpful to
> others:
>
> IIS: Access Denied When Trying to Update Files on IIS Computer
> http://support.microsoft.com/kb/q191742/
>
> API Opportunity to Fix or Get Around
> http://groups.google.com/group/microsoft.public.inetserver.iis/browse_thread/thread/efb71a730d49dfb0/a95d97dc6eb65d02?
>
> lnk=st&q=q191742&rnum=1&hl=en#a95d97dc6eb65d02
>
>
> Discussion of how to clear the Cache
> http://groups.google.com/group/microsoft.public.inetserver.iis/browse_thread/thread/9811981fa325dca1/dcfea8578e3c0be9?
>
> lnk=st&q=iis+Cache+time&rnum=5&hl=en#dcfea8578e3c0be9
>
>
> Registry Values for HTTP.SYS for Caching
> http://support.microsoft.com/?id=820129
>
>
> DisableStaticFileCache Parameter
> http://groups.google.com/group/microsoft.public.inetserver.iis/browse_thread/thread/f1f0b92dd6845c4/cfc5edb6cedb5d3e?l
>
> nk=st&q=iis+Cache+Update+time&rnum=8&hl=en#cfc5edb6cedb5
> d3e
>
> How to change it:
> http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/8a887ebb-7094-4702-86a4-eb105d09132d.mspx
>
>
> Disabling Caching for a specific MIME Type
> http://support.microsoft.com/default.aspx?scid=KB;EN-US;247389
>
>
> Discussion of similar problem
> http://www.leafe.com/archives/showFullThd?cMsgNum=78538&cList=profox
>
>
> Article on third party utility trying to work through is that has a
> "retry" paramater.
> http://www.netline.ch/support/info/aspcomp/safileup/install_tailor_lockretry.htm
>
> Similar issue with IIS6 and Fresh Content not Showing
> http://support.microsoft.com/?id=832139
>

Marty
Fri May 05 17:32:53 CDT 2006

David,

Indeed, you are correct. Your assessment of the situation is sound.
I tried sysinternals using FileMon and it showed the wierdest thing.
When we tried to rename the files with Explorer, I could see Adobe
Acrobat loading... It led me to believe that there are hooks in Windows
Explorer to the registered application and I thought that I really
don't understand the complexities going on in Windows when you want to
rename a file. But alas, we discovered the problem which we never
found in any postings and I hope may be helpful to others. The
Indexing Service is somehow holding a lock on it. We believe it has
something to do with the filter offered by Adobe. We are figuring out
a workaround now.

David
Sat May 06 05:58:23 CDT 2006

Hmm... if you have a .pdf file being served by IIS, IIS will only treat it
as a static file and send it as-is (i.e. do not invoke Adobe Acrobat on the
server to do anything).

If you are seeing Acrobat running on the server with a lock on the file,
then either:
1. .pdf file is NOT configured as a static download in IIS
2. There is some lower-level driver, possibly filesystem filter, that is
invoking extra user code on the server in response to file access to a .pdf
file.

Indexing Service holding a lock on it is probably because you told it to
index the hard drive's contents, so on update, it is re-indexing. It is most
likely benign because Index server has no interest in the file until AFTER
you update it -- and you're having problem UPDATING the file -- so Index
server is likely a "victim" of whoever is holding the file handle open... so
we want to figure out why the handle is open in the first place by Acrobat.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Marty Zigman" <google@interscore.com> wrote in message
news:1146868373.613401.26570@j73g2000cwa.googlegroups.com...
> David,
>
> Indeed, you are correct. Your assessment of the situation is sound.
> I tried sysinternals using FileMon and it showed the wierdest thing.
> When we tried to rename the files with Explorer, I could see Adobe
> Acrobat loading... It led me to believe that there are hooks in Windows
> Explorer to the registered application and I thought that I really
> don't understand the complexities going on in Windows when you want to
> rename a file. But alas, we discovered the problem which we never
> found in any postings and I hope may be helpful to others. The
> Indexing Service is somehow holding a lock on it. We believe it has
> something to do with the filter offered by Adobe. We are figuring out
> a workaround now.
>