Tag Info

Hot answers tagged

2

Simply because the direct link "Site Collection Cache Profiles" under Site Collection administration is all about Defining NEW cache profiles, not setting one. To configure it (chose which one) you use "Site Output Cache" in the Site Collection, where you can chose from predefined profiles. It is the difference between, defining the profile, versus applying ...


2

HttpContext.Cache uses HttpRuntime.Cache as the real underlying implementation, and that is not bound to a web context (despite the name implying otherwise). It can be used in any application (class library, WinForms, etc.) without issue - other than it can look a little jarring to pull in System.Web. Your colleague's utility should be using a cache ...


1

I think I have had this problem before and just doing an IISRESET, [Edit]Recycle of SP User Code Host Service[End edit] and restarting Visual Studio before the redeployment solved the issue for me. I may be completely wrong but it seems Visual Studio maintains some kind of cache which holds the old schema.If I did not restart visual studio, I would get the ...


1

This is how the internal implementation of GetDefaultCache method looks like: public DataCache GetDefaultCache() { string cacheName = "default"; return this.GetCache(cacheName); } It's just trying to call GetCache("defaul"). 'default' cache just does not exist. The real name of the default cache should look more like: ...


1

i would try to repair the DC: 1) Get-SPServiceInstance cmdlet to list all services on all servers in the server farm 2) start the powershell and run below command: $s = Get-SPServiceInstance GUID $s.delete() 3) wait for couple of min and in the powershell window run below command. Add-SPDistributedCacheServiceInstance Now try and if it fix fine. ...


1

Blob cache refreshes on a timed basis only and causes what you are seeing. However you can clear it via powershell and I think central admin, but here is the powershell: $webApp = Get-SPWebApplication "<WebApplicationURL>" [Microsoft.SharePoint.Publishing.PublishingCache]::FlushBlobCache($webApp) The setting for the time is here in the web config. ...


1

Distributed Cache is required for SP2013 farms. By default DC takes 10% of memory installed/allocated to a server. Recommendations: 1. Validate memory used for DC thru powershell on server in question 2. Resolve all DC errors showing log 3. If virtual server, verify Dynamic memory allocation is disabled 4. Distributed Cache is not required for WFE ...


1

If they have the namespaces you need, go for it. You've tagged it with '2013', are you using SharePoint 2013? Make sure that the AppFabric Cache cluster you're using is not the one SharePoint 2013 using, make sure it's on a server that's not one of your SharePoint servers and one that you're maintaining on your own. It's unsupported to use the AbbFabric ...


1

Follow the steps from Plan and use the Distributed Cache service in SharePoint Server 2013 under the section titled "Repairing a Cache Host". -Run Get-SPServiceInstance to find the GUID in the ID section of the Distributed Cache Service that is causing an issue. -Run these commands: $s = get-spserviceinstance GUID $s.delete() -Recreate the Service with ...


1

When you install the SharePoint 2013 it installs the service by default and assigns the Distributed Cache service 10 percent of the total physical memory on the server (see more details) It might be you'r having less memory on your SP Installation. So you might need to update the distributed Cache Service to specify the amount of RAM or increase the RAM for ...


1

Discovered the answer to my own question. If Script (or CSS) files are kept in normal libraries they will get cached internally to SP and only rarely updated. However if these are files are maintained in the "Style Library" (a built in library created by SP) they will NOT be cached and will update normally. It's easy enough, once this known, to create your ...


1

Most probably it's an issue of the file getting stuck in one of the server's caches. Is the BLOB caching enabled on the server? If yes, you can try clearing it. Are Publishing Features enabled on the server? If yes, make sure that you have reset the Page Output Cache and the Object Cache also.



Only top voted, non community-wiki answers of a minimum length are eligible