People Search Relevance Is Not Optimized When The Active Directory Has Errors In The Manager Reporting Structure

This is a pretty common error, and the solution is generally pretty simple. I saw this over at a vacuum manufacturer this morning.

The error really does make sense, you can’t build a represntation of organizational units without having the top level object of that overall tree defined. What this error is saying is SharePoint 2013 needs to know who the company leader is by first finding the GUID of that user within the User Profile Service Application Proxy and then using that to setting that ID as a company leader. This is generally achieved by using OOB powershell commands Get-SPServiceApplicationProxy and Add-SPProfileLeader. Sometimes when using these commands you will run into the following error:

Get-SPProfileLeader : UserProfileApplicationNotAvailableException_Logging ::
UserProfileApplicationProxy.ApplicationProperties ProfilePropertyCache does
not have 1387E85D-F009-4691-8BDD-003367D1ECA5
At line:1 char:1
+ Get-SPProfileLeader
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidData: (Microsoft.Offic…CmdletGetLeader:
SPCmdletGetLeader) [Get-SPProfileLeader], UserProfileApplicationNotAvailab
+ FullyQualifiedErrorId : Microsoft.Office.Server.UserProfiles.PowerShell.

This error, particular the ProfilePropertyCache does not have segement implies a direct permission error problem. To get around this error so that the command can be successfully executed ensure that the user that you are using with powershell has the appropriate permissions on the UPA.