I have a sharepoint 2007 farm (of 5 machines). All uses publishing site templates, and I have IFS (as in an Extended site, with anonymous access) And I configured the Site output caching on one of the server, and checked on the one of the pages of the same server. The caching was working just fine. I went to the same page on the other machine of the same farm and found that there is no caching working. And found this at the end of the page when I did view source. <!-- 3 Output cache not used. Reason: Unable to get publishing page object for current request. --> Any idea?

Hi, According to your description, in my opinion, the output caching is limitations include the following: 1. Output caching uses additional memory to cache the HTML markup for each cached page. Be sure to install enough physical memory to avoid system paging or other memory problems. Here is a use article about hot to extend caching, for more information, please refer to: http://msdn.microsoft.com/en-us/library/ms550239.aspx 2. When used with two or more Web servers, output caching might affect consistency. You can configure a cache profile not to check for updates for each request and, for example, configure the profile to ignore changes to the version of the Web page in the output cache until 60 seconds after the original page is updated. If you have two Web servers in your topology, and depending on the load balancer used to route the user’s request, a reader might see inconsistent content if the page is rendered by one server and then a later request is routed to a second server within that 60-second window. If checking for changes is enabled in the cache profile, it will reduce the effectiveness of the output caching. 3. If output caching is enabled for users who have write permission for a site collection, these users may not see the most up-to-date data on the Web pages in that site collection until the output-cached pages have expired. Typically, this does not directly affect the content on a Web page that the user is currently changing or viewing. However, it can affect roll-up data from a list or a library. For example, this can affect data presented from a document library Web Part. Therefore, if you want to be sure that users who have write permissions can view all current information, enable output caching for only users who have read-only permissions. Please have a try. Best Regards David Hu

Hi, According to your description, in my opinion, the output caching is limitations include the following: 1. Output caching uses additional memory to cache the HTML markup for each cached page. Be sure to install enough physical memory to avoid system paging or other memory problems. Here is a use article about hot to extend caching, for more information, please refer to: http://msdn.microsoft.com/en-us/library/ms550239.aspx 2. When used with two or more Web servers, output caching might affect consistency. You can configure a cache profile not to check for updates for each request and, for example, configure the profile to ignore changes to the version of the Web page in the output cache until 60 seconds after the original page is updated. If you have two Web servers in your topology, and depending on the load balancer used to route the user’s request, a reader might see inconsistent content if the page is rendered by one server and then a later request is routed to a second server within that 60-second window. If checking for changes is enabled in the cache profile, it will reduce the effectiveness of the output caching. 3. If output caching is enabled for users who have write permission for a site collection, these users may not see the most up-to-date data on the Web pages in that site collection until the output-cached pages have expired. Typically, this does not directly affect the content on a Web page that the user is currently changing or viewing. However, it can affect roll-up data from a list or a library. For example, this can affect data presented from a document library Web Part. Therefore, if you want to be sure that users who have write permissions can view all current information, enable output caching for only users who have read-only permissions. Please have a try. Best Regards David Hu