SharePoint people search error

Error:

People search relevance is not optimized when the Active Directory has errors in the manager reporting structure –

The above error happens when active directory manager field is set to empty.  Company leaders can have it empty. To fix the above error, specify the company leaders explicitly.

Powershell script:

Get-SPServiceApplicationProxy                                                                                    

$upaProxy = Get-SPServiceApplicationProxy <proxy id>

Add-SPProfileLeader $upaProxy -Name "contoso\janedow"

 

Then run the below command to see if it has been added:

'Get-SPProfileLeader $upaproxy'

 

Run a full crawl on the content source containing the start address of the URL profile.

 

To remove the company leaders that were added explicitly, run the below powershell command:

Remove-SPProfileLeader -ProfileServiceApplicationProxy $upaProxy -Name "contoso\janedow"

 

SharePoint large lists and libraries

When a SharePoint document library or list exceeds its threshold (by default 5000 defined under Central admin > Manage web applications > web application settings > Resource throttling), the following are possible issues that users may experience:

 

• cannot delete folders
  
   
    
• cannot index a column
  
   
• cannot view all content
  
   
• 
  
• cannot sort columns
  
   
   
   
   

SharePoint Logging and Reporting

 

Logging

To monitor SP servers and services, you can directly access various logs such as event viewer logs, ULS logs or usage data logs that are stored separately. You can also view various reports.

 

To increase monitoring efficiency, configure usage/logging database to monitor from one place.

 

Usage and Health data: Central Administration > Monitoring > Configure usage and health……

Have separate service application (Central Admin > manage service and application) specified with SQL usage database. You can see all the below logs stored in the SQL dbase in logical partitions by going into SQL mgmt. studio > expand databases > select the logging dbase; right click; select Reports > Standard reports > disk usage by top 10 tables

 

Microsoft SharePoint Foundation Usage Data Import – import usage data logs into dbase

Microsoft SharePoint Foundation Usage Data Processing – deletes expired data from the logging dbase that are older than 30 days.                                                                                                          

 

              Health related timer jobs:

Diagnostic Data Provider: App Usage                                                                                 

Diagnostic Data Provider: Event Log                           – stores event viewer logs                             

Diagnostic Data Provider: IO Intensive SQL Queries                                                     

Diagnostic Data Provider: Per-database IO                                                                      

Diagnostic Data Provider: Performance Counters - Database Servers                  

Diagnostic Data Provider: Performance Counters - Web Front Ends                     

Diagnostic Data Provider: Site Size                                                                                      

Diagnostic Data Provider: SQL Blocking Queries                                                             

Diagnostic Data Provider: SQL Blocking Reports                                                             

Diagnostic Data Provider: SQL Deadlocks                                                                          

Diagnostic Data Provider: SQL DMV                                                                                    

Diagnostic Data Provider: SQL Memory DMV                                                                 

Diagnostic Data Provider: Trace Log                           – stores ULS logs into database                    

 

 

Diagnostic logging: Central Admin > Monitoring > Configure diagnostic logging…

Logs related to SharePoint farm

Event Throttling Logs – logs Windows Event Viewer. Verbose/warning…….

Trace Logs/ULS logs – show detailed line by line saved under D:\logs\ULS

 

Audit Logs: Site Collection > Settings > site collection audit settings….

Saved in associated content dbase tables. Can view by going into  

SQL mgmt. studio > expand databases > select the logging dbase; right click; select Reports > Standard reports > disk usage by top 10 tables

 

Search\Query Logs – saved in associated SSP database but can be viewed at SSP level via the Web Browser and in site collection level by going to settings.

 

Information Management Logs – Stored in associated content dbase and can be viewed at site collection level.

 

Content and Structure Logs –only available after publication feature enabled. Saved in the content dbase associated with site collection by going to the settings page.

 

 

 

Reporting

 

Administrative report: Central Admin > Monitoring > View administrative reports

 

Health report: Central Admin > Monitoring > View health reports (only work if usage data collection is enabled and two timer jobs enabled)

 

Web analytics Report: In SharePoint 2013, (unlike SP2010 with separate service application) it’s part of search service; can be accessed by going into Site settings > popularity trends or site collection settings > popularity and search reports.

Same analytics can be accessed for a particular SP page by going into page ribbon > popularity trends or for a particular library by going into library ribbon > most popular items.

 

Audit Log report: need to be enabled at site collection level. In SP2013, they get deleted / trimmed monthly by default via timer job Audit log trimming.

 

 

Related Powershell commands:

To check retention days for Usage database:

Get-SPUsageDefinition                

 

To bring down all usage retention days to 1:

Get-SPUsageDefinition | ForEach-Object {Set-SPUsageDefinition -Identity $_.name -DaysRetained 1}                  

 

To bring down usage retention days individually:

Set-SPUsageDefinition -Identity "Sandboxed Requests" -DaysRetained 3

 

To recreate usage database:

$def=Get-SPUsageDefinition -Identity "page requests"

$def.MaxTotalSizeInBytes=12400000000

$def.update()

Get-spusageapplication | Set-SPUsageApplication -DatabaseServer <DBServer> -DatabaseName <New_DBName>

 

 When you recreate usage database, it will only contain the default set of stored procedures.

In this case the Search Service Application Usage Provider has not created the necessary Stored Procedures in the database. This is done by a timer job called “Search Health Monitoring – Trace Events”. Once this timer job has executed successfully the required stored procedures should be created.

Related error: “Could not find Stored Procedure ‘Search_GetRepositoryTimePerCrawl’”

 

 

My Sites Task error

The below error comes up when accessing tasks from SP2013 my site:

 

Error: Sorry, we’re having trouble refreshing your tasks. (Refer screen shot)

  

Steps to follow:

• Add the account that was used for work management service application to user profile service application's permission.
  [To find the account, go to Central Admin > Manage service applications > highlight 'work management service' and select properties from the ribbon; Take note of the application pool name; Go back to Central Admin > security > configure service accounts > select the app pool name and take note of the account name]
• Make sure work management service is running via CA. If it is already running, try restarting.
  
  
  If error still persists, try the following:
  Run incremental user profile synchronisation
  Recreate work management service application
  Add the same account to My site web application permission via CA.