We have 3 front-end servers each running multiple web applications. Each web application has an in memory cache.
Recreating the cache is very expensive (>1 min). Therefore we repopulate it using a web service call to each web application on each front-end server every 5 minutes.
The main problem with this setup is maintaining the target list for updating and the cost of creating the cache several times every few minutes.
We are considering using AppFabric or something similar but I am unsure how time consuming it is to get up and running.
How do you/would you update an expensive in memory cache across multiple front-end servers?
We have experienced a strange issue in SharePoint. We backed-up and restored a site collection from WebApp1 to WebApp2 and both the site collections have Publishing Features activated (BLOB CACHE was NOT Enabled) After successful restore , none of the sites were working. Following Exception has occured : Site id <> could not be found OR File not found Solution : In the stack trace there method sitecachesettings(guid id).....Reset the IIS, and booom every thing works fine :) My Question : Where is object cache stored ??? how it works?? point me any links where I can dig in deep
I have a SharePoint 2007 Publishing Site. The top level site is purely anonymous and one of the children is using Forms authentication using Custom membership provider. The Admin site is using windows authentication. How can I set the site output caching to allow best performance without risking having authenticated users see each others data (cached)?
Just wanted to see what the consensus on this one is… If you make a call to the OM to return a SP object e.g. SPListItemCollection, and then want to cache the results (to improve subsequent performance and usage of the object/data) would you "unpack" the contents of the collection/object into a custom class and cache that or just cache the native SP object? I’m not sure if there is any reason to introduce the overhead of a custom class etc?
Issue:Web Front End servers in the server farm are not consistent in the services they run. Impact:Users may have intermittent failures while trying to access Web pages in this server farm. Update: Thanks for your reply. I understand about the first warning and I just left it as it is. However, same set of services are running on each WFE not sure what is different let me show you what is running no each server. Under the link "Servers in Farm": mail server Windows SharePoint Services Outgoing E-Mail WFE1 Incoming Mail, Windows SharePoint Services Web Application WFE2
Every where I'm reading about setting up Excel Services for delegation so that it can connect to Analysis Services running on separate server is based around using Claims based authentication to authenticate to the web application. However, right now we are using Classic Mode Authentication, and I can't find ANY information on how to set things up in this scenario. Is it even possible to get this going without using Claims Authentication?
I'm prototyping the best way to dynamically connect web parts at runtime. Essentailly, the application will allow for several disparate application groups to create web parts that will be consumed within the SharePoint front end. All of the web parts will need to automatically detect consumers and providers to create connections at runtime. What we are looking to do is have webparts discover... interface for passing data between the parts, so the only issue is how to manage the connections. To be clear, we do not want user's to worry about having to create connections themselves. For our
I have recently generated a couple of ListDefinitions using both SPSource and VSeWSS SharePoint Solution Generator. In both cases, surpisingly, Visual Studio reports fake schema validation errors in schema.xml like The 'Description' attribute is not declared" for List xmlns="http://schemas.microsoft.com/sharepoint/" BaseType="0" DefaultItemOpen="0" Description=""... >... followed by errors like Could not find schema information for the element 'http://schemas.microsoft.com/sharepoint/:GetVar'. Can anyone help me fix that?
what do you think about deploying the SharePoint IIS web sites to a Shared file location (\\Fileserver\WWWRoot\Application1 for example) in contrast with deploying a copy locally to each Web Front End server (c:\inetpub\wwwroot\application1 for example). Deploying locally to WFEs can usually take time to copy physical files to the different WFEs and we make efforts in making them synched and sometimes we have problems because the two servers are not exactly the same and so on. Are there any problems with the approach of deploying a Sharepoint IIS web site on a shared location path?
be asynchronous using Ajax functionality. Some questions I can't decide whether to go with Visual web parts or Silverlight? I know there are other possibilities as well (like running separate Asp.net MVC... have to build a complex business application that will use its own DB on MS SQL 2008 R2. Authentication will be done using client certificates and will connect to AD FS on the server side... to master/detail views, and I guess each of these should be a separate screen/webpart/whatever. Application will display custom controls that will support business processes. These controls will be custom