locked
IIS 7 Shared Configuration - Errors if files share is unavailable RRS feed

  • Question

  • User1478706195 posted

    I am testing the Shared configuration setup and have come across something that doesn't make sense to me. If you have Server A and Server B both using shared configuration on Fileserver 1 they don't appear to cache the config because you cannot restart or do anything with the file server or they will both stop serving pages and throw a configuration error. Then to top it off once the resource is available again the web servers will not serve content - they won't even after a IIS restart. It requires a complete machine reboot. Is there some switch to flip that says watch the file for changes but cache it locally?

     

    Thursday, July 31, 2008 6:13 PM

Answers

  • User-1653247517 posted

    Hi MCUSA,

    We recommend people to use client side caching (AKA offline files) to deal with unavailability of shared configuration file server. This article details how to enable offline files.

    Thanks,
    Kj

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Thursday, July 31, 2008 9:40 PM

All replies

  • User-1653247517 posted

    Hi MCUSA,

    We recommend people to use client side caching (AKA offline files) to deal with unavailability of shared configuration file server. This article details how to enable offline files.

    Thanks,
    Kj

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Thursday, July 31, 2008 9:40 PM
  • User1478706195 posted

    Thanks that does work. I just thought it would cache locally on its own.

    Tuesday, August 5, 2008 6:39 PM