When gathering files from a content source, the SharePoint 2013 Crawl Component can be very I/O intensive process – locally writing all of the files it gathers from content repositories to its to temporary file paths and having them read by the Content Processing Component during document parsing. This post can help you understand where the Crawl Components write temporary files, which can help in planning and performance troubleshooting (e.g. Why does disk performance of my C:\ drive get so bad – or worse, fill up – when I start a large crawl?)
To prevent Enterprise keyword fields from offering suggestions from a team set then unckeck this setting Office 2010/2013 can integrate with Managed Metadata site column If you want to use Content type hubs then you need to activate this site collection feature :Content Type Hub Syndication… Read More ›
Access Denied Error after migrating to SharePoint 2013 Scenario: We were working for a client, they had many groups and we had to build a collaboration portal for all the groups. Key thing was few sites of some groups were… Read More ›
Sharepoint 2013 – 404 Not Found while accessing site collection from outside.
People have liked the Organization Browser web part so much that they want the web part to be added to their companies main Portal web application. I too recently came across this interesting situation, wherein we were supposed to show… Read More ›
We all know that SharePoint doesn’t support saving publishing sites as a template. I don’t recommend doing that anyway as the produced template will have errors and isn’t reliable to be used in production to create new sites off of. However, sometimes as a developer you need to save a publishing site as a template to see how SharePoint packages things. This can help you build your own custom web template which is a neat thing and replaces the need to save a publishing site as template.