SharePointSupport

In this article we learn how to configure a user profile and My Site configuration in SharePoint 2013. In earlier versions of SharePoint, each user had a profile and a personal site (e.g., My Site). The 2013 version of SharePoint splits My Site into three sections: Newsfeed, SkyDrive, and Sites. A global navigation bar provides access to each section. These social features are tightly integrated into SharePoint 2013, so you no longer need to launch a web browser to access them. Use the following procedure to create a My Site Host site collection:     1. Verify that the user account that is performing this procedure has the following credentials:         The user account that performs this procedure is a farm administrator         The user account that performs this procedure is a member of the Administrators group on the computer that is running SharePoint Server.         2. First we have to create a web application for My Site; see: 3. On Central Ad

There are many great articles that talks about how to configure your SharePoint 2013 farm for apps development . At the end of this article I will list a lot of these great references. I’m going to try to summarize the important things you need to know and also cover few FAQs along the way. First of all, you need to know that there are two main types of SharePoint apps you can develop on prim in your local SharePoint 2013 farm: SharePoint hosted apps SharePoint provider hosted apps The third type SharePoint Auto hosted (Azure auto hosted apps) is only available on SharePoint online tenants part of Office 365 . Also it’s important to note that if you plan to publish your SharePoint app into the SharePoint store to make some money the above mentioned types (Hosted & provider hosted) are the only allowed ones as long as they don’t request full control permission. For more details about the submission requirements check this link . In order to make your SharePoint 20

What is the search schema? The search schema is a mechanism in SharePoint search that controls: Which aspects (properties) of items are to be indexed How and with what indexing structures particular pieces of data are indexed Which aliases can be used when querying using property restrictions What does this mean really? It means that the search schema controls  what  can be searched for,  how  it can be searched for and  how  the results can be presented in your search sites. Main schema concepts The most important concepts in search schema are  crawled properties  and  managed properties . The typical data flow is illustrated by this figure: So a crawl component reads items from the content database (or other content sources) and sends documents and metadata to the content processing component in the form of  crawled properties . A lot of magic then happens inside the content processing component: the text of the item is extracted, language detected, spell-checkin

I have built a new SharePoint 2013 environment and after provisioning a new Search Service Application the following was regularly being logged in the Application Event Log: Content Plugin cannot be initialized -  list of CSS addresses is not set After a fair amount of Googling and looking through logs I learned that this was caused by the Search Service Application not being fully provisioned.  After removing and recreating the Search Service Application these errors went away.

Problem: In my redundant Search farm, search falls over.  It was working, nothing appears to of changed but it suddenly stops working.  This problem has caused itself to surface in several places: 1. In  Central Admin going to "Search Administration" displays the following error message:  Search Application Topology - Unable to retrieve topology component health states. This may be because the admin component is not up and running. 2. Query and crawl stopped working. 3. Using PowerShell I can't get the status of the Search Service Application PS> $srchSSA = Get-SPEnterpriseSearchServiceApplication PS> Get-SPEnterpriseSearchStatus -SearchApplication $srchSSA Error: Get-SPEnterpriseSearchStatus : Failed to connect to system manager. SystemManagerLocations: net.tcp://sp2013-srch2/CD8E71/AdminComponent2/Management 4. In the "Search Administration" page within Central Admin, if I click " Content Sources " I get the error mes

All managers from the company were waked with this emails like: Subject: The My Site of X Y is scheduled for deletion The My Site of X Y is scheduled for deletion in 14 days. As their manager you are now the temporary owner of their site. This temporary ownership gives you access to the site to copy any business-related information you might need. To access the site use this URL: https://mysites.portal.domain.local/personal/xy Pretty uncomfortable. The day before this I deleted the AD Sync Connection from SharePoint's User Profile Service Application and this caused it. The sync job ran and with no connections SP thought that all the users have been deleted. Theoretically there should be 14 days until these profiles are deleted but for some reason I can't see past activity for the use users. Long story short, I need to restore MySites from a backup .   The Process The restoring process is simpler than thought. Later I found out that I had to restore the User Profi

After performing a SharePoint 2013 upgrade we were having trouble with our search functions and got a rather generic error message. After doing a migration upgrade of SharePoint 2010 to SharePoint 2013, search failed with: Sorry, something went wrong. A correlation id is provided. We checked our Content Sources from Central Administration->Manage Services on Server->SharePointServer Search->Search Service Application->Content Sources   and found that Full Crawls had completed successfully. You will find a TON of log enties for that correlation id, so finding the root cause is daunting.  Buried in the results you will find a 500 Service Unavailable error connecting to the Metadata Management Service. In the Search Service Application, we saw that in Queries and Results->Search Dictionaries , we had an error: Managed Meta Data Error The Managed Metadata Service or Connection is currently not available.  The Application Pool or Managed Metadata Web Service