I came across the following error in the crawl logs of a SharePoint 2013 instance. "The content processing pipeline failed to process the item. ( Object reference not set to an instance of an object. )" In my case this turned out to be because I had deleted the managed metadata service that had been... Continue Reading →
SharePoint 2013: Get User Profile Properties via PowerShell
The following script will iterate through all the user profiles and return the account name. Add-PSSnapin microsoft.sharepoint.powershell; #Load SharePoint User Profile assemblies [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Server.UserProfiles") #Get Context $serviceContext = Get-SPServiceContext -Site "[Site Name]" #Instantiate User Profile Manager $userProfileConfigManager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($serviceContext); #Get All User Profiles $profiles = $userProfileConfigManager.GetEnumerator(); #Loop through all user profiles and display account name... Continue Reading →
SharePoint 2013 :Adding shared properties to a term set using PowerShell
To update or create a shared property for a term in your term store run the following script. #Load SharePoint PowerShell Snap In Add-PSSnapin Microsoft.SharePoint.PowerShell; #Get Taxonomy Session $session = new-object Microsoft.SharePoint.Taxonomy.TaxonomySession(Central Admin URL); #Get Managed Metadata Service $Store = $Session.TermStores["Managed Metadata Service"]; #Get Term Group $Group = $Store.Groups["Group Name"]; #Get Term Set $TermSet =... Continue Reading →
Error: Attempted to make calls on more than one thread in single threaded mode using multiple Content by Search web parts
In SharePoint 2013 when adding more than one Content by Search web part to a page you may receive the following error "Attempted to make calls on more than one thread in single threaded mode. (Exception from HRESULT: 0x80010102 (RPC_E_ATTEMPTED_MULTITHREAD)) Correlation ID: 00000000-0000-0000-0000-000000000000" This is caused by a bug in the original release, this has... Continue Reading →
The Microsoft Cloud Blog 