Managed Prop Mapping Type Check
We had a People type mapping in OOB AccountName MP. We added another string crawled property mapping to AccountName.
We discovered that, this caused miss the Update of current list item in next Continious Crawl cycle. When a new item added, crawl finds and ports to index, but in an update event, crawl does not fetch this update.
When we removed the mapping menitoned above, the issue disappeared and crawl worked without problem.
So came to a point that, having a type check for an MP-CP mapping can be a good idea to be assured of the integrity of the Search Schema.
Anthony Casillas commented
I realize this post is pretty old, but I wanted to add something here in the event someone else comes across this issue and is uncertain on how to address this. I work on the SharePoint Support team and my primary area of focus is Search. We have seen a few of these cases. While i realize that these Errors appear to point to bad GUIDs in the User Profile Service Application, this is not always the case. In our cases, our customers were not even using "User Profile Service Applications" and were not doing any People Crawls or crawling of MySites.
What we discovered is: that there is a ManagedProperty, called AccountName, and if it has mappings other than the default, People:AccountName, then this can cause this same error. One of our customers had a SharePoint based column called "AccountName" and it was picked up with a crawled Property of "ows_AccountName" and this crawled property was mapped to the "AccountName" managed property in the Search Schema. Because of this, we move into a different code path and call into this "SocialInfoExtractorProducer".. the best way to addressthis is to look at your Search Schema and see if someone addedadditional crawled properties to the "AccountName" managed property. The default one in there should be: People:AccountNameif any others have been added and are not part of the People\Profile property set, i would say this is probably your Culprit and not a bad User Profile Service Application..
Emre Erkan commented
In this case Exception message in ULS is
SocialInfoExtractor Operator error in CTS flow. ( The value is not a valid Guid.; ; SearchID = 717579E1-B2DF-49C9-943B-77EEA1C2CEB9 )
When you know the cause of error is a wrong MP-CP mapping, exception message may mean something. But when you don't have any clue, this leads to nothing