Ken

> There are a number of possible problems here.
> 
> For a non-NLB situation, you are probably seeing an in-memory copy
> being cached. IIS relies on Windows for file-change notification
> notices, which in turn triggers a cache flush. There are a number of
> hotfixes available for Windows 2000/IIS 5.0 that address various
> file-change notification issues.
> 
> For an NLB situation, where a reboot has failed to clear the in-memory
> cache, we're looking at a whole different kettle of fish.

It would appear that I was in error regarding the reboot - I thought we rebooted the boxes, but actually we just restarted IIS. When the problem occurred yesterday a reboot fixed things just fine. By the back end of yesterday I had come to the conclusion that it was the Script File Cache not being flushed properly, but did  not have time to investigate a solution.

> I can try an escalate this issue, if I can get more details from you.
> I will try to get a list of information that I'll need, and then get
> in touch.

I appreciate the offer, but the first thing I'll do is to see which hotfixes have been installed on the boxes, and take things from there. Hopefully it will be an easily-fixable file-change notification issue.

Cheers!

Regards

Chris marsh