IIS Stuff

Hi Everyone,

We have one of our users who no matter what nevers sees the changes that he did in his workarea. And there has been similar problems with other users as well.

We think it is because of the server is caching the files.....so I checked out IIS to see if it was defaulting to caching ISAPI applications. Turns out that it is....but I did notice that on the iw-mount virtual directory, the error icon in IIS is shown.

I was wondering....if this is normal or not.......I have attached an image of what I am talking about.

Find more posts tagged with

Comments

Adam Stoller

The error icon for iw-mount is shown because of a timing issue with respect to IIS and TeamSite. I believe you can right-click on the IIS instance and do a Refresh and the error icon will go away (or else stop/start the IIS instance and do a Refresh).

Caching could be taking place at the web server level *or* at the browser level (or both) - make sure the user's browser is set to not-cache as well as making sure that IIS is set to not-cache.

If that still doesn't resolve the issue, I'd suggest contacting Interwoven Support so that they can work with your more closely to diagnose the problem more thoroughly.

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

IIS tends to cache things too aggressively. There is a KB article about this, I'm sure. There's a way to configure IIS not to cache pages.

This is a separate matter from whether IIS caches ISAPI applications, unless you happen to be developing an ISAPI application inside TS.

NathanW

There is an article about this - 3 actually:

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=48906

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=1254

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=1764

After our intial install we had all sorts of problems with caching - make sure your users workstations are set correctly - refresh every visit to page seems to work OK for us. The other thing that cropped up - all our browser requests were intially being directed through our corporate network to a central proxy before being rerouted internally to the TeamSite server - make sure caching is switched off at the proxy if you have one.

We havent yet gone down the path of implementing some of the changes proposed in the above articles - it seems to be intermittent for us now but in some cases changes can take 30 minutes to appear..... weird huh?

Nathan Wall
Department of Transport and Regional Services (Australia)