{"id":1190,"date":"2021-08-03T09:05:50","date_gmt":"2021-08-03T14:05:50","guid":{"rendered":"https:\/\/zewwy.ca\/?p=1190"},"modified":"2021-08-03T13:35:48","modified_gmt":"2021-08-03T18:35:48","slug":"fixing-sharepoint-search","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2021\/08\/03\/fixing-sharepoint-search\/","title":{"rendered":"Fixing SharePoint Search"},"content":{"rendered":"

<\/span>Broken SharePoint Crawl<\/span><\/h1>\n

<\/span>Issue: SharePoint Search<\/span><\/h2>\n

<\/span>First Issue: Crawl ends in 1 min 20 seconds.<\/span><\/h3>\n

Solution: Check to see if the Page Loads when queried from the front end server. If you get a credential prompt 3 times.\u00a0 Then you have to disable loop back checking.<\/p>\n

How to:<\/p>\n

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa<\/p>\n

Add a new DWORD value named DisableLoopbackCheck and give it a value of 1. After setting the value reboot your server.<\/p>\n

reg add HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa \/v DisableLoopbackCheck \/t REG_DWORD \/d 1<\/pre>\n
<\/span>Second Issue: Crawl appears to complete but Errors in Log<\/span><\/h3>\n
Log Details of “the content processing pipeline failed to process the item ExpandSegments”<\/p>\n
You may find lots of sources stating to watch out for multi valued attributes or property names such as this nicely detailed blog post<\/a> however, watch for the details in the log message and it’s a bit different. However I feel this TechNet was answered incorrectly<\/a>.<\/p>\n
I tried some of the basics, such as clearing the index and adding the search account as site admin<\/a>, did not help. On that note I learnt that separate search content sources within a search application do not have their own indexes. You have to create dedicated search applications for each SharePoint site if you wish them to have their own index (“Database\/Tables”).<\/p>\n
After a bit more scouring I found many instances of the same problem with the solution always being you have to create a new search application, such as this TechNet post<\/a> and this TechNet Post.<\/a><\/p>\n
Solution:<\/p>\n
Remove the content source from the existing Search Service Application.<\/p>\n
Create an entirely new Search Service Application.<\/p>\n
Reboot the Front End.<\/p>\n
Add Crawl Content on new SSA. Crawl should work.<\/p>\n
<\/span>Third Issue: Red X on Search Service Application Services<\/span><\/h3>\n
*NOTE* After creating the new Search Application, a front end reboot is required to remove the red X’s on some of the application services statuses<\/a>.<\/p>\n
<\/span>Fourth Issue: Search results not working<\/span><\/h3>\n
This from my testing appeared to have resolved the crawl issue at hand. However I wasn’t able to get results returned when entering data in to search. I did a bit of searching and testing and I found the solution<\/a>. Turns out you have to associate the web application with the new search service application (In my testing I created a new uniquely defined search application to have a separate index then the other SharePoint Sites).<\/p>\n
Solution:<\/p>\n
Navigate to Central Admin > Application Management > Manage web applications >Highlight the web application > Select Service Connections from top ribbon > Make sure your Search service application is selected.<\/p>\n
This was it for me, however if you still experience issues I have also read updating the front end servers can resolve issues as well, as blogged about by Stefan Go\u00dfner<\/a>.<\/p>\n
<\/span>Fifth Issue: Runaway Crawl<\/span><\/h3>\n
For some unknown reason, when I went to check out the SharePoint front end after the weekend, I noticed it was using near 100% CPU usage, very similar to a Front End that is actively doing a crawl, I knew this wasn’t a normal time for a crawl and it generally never happens during this time.<\/p>\n
To my amazement 3 crawls were on going for over 70+ hours. Attempting to stop them from the front end option “Stop all crawl” resulted in them being stuck in a stopping state.<\/p>\n
Googling this I found stop and starting<\/a> the SharePoint Search Service under services.msc did help to bring them back to “idle”.<\/p>\n
Now I believe this next step is what caused my next issue, but it is uncertain.<\/p>\n
I clicked on Remove Index, for the primary search service application. It was stuck at “This shouldn’t take long” for a really long time, and I believe it was my impatience here that caused the next problem, as I restarted the search service again after this fact.<\/p>\n
<\/span>Sixth Issue: Paused by System<\/span><\/h3>\n
All solutions I found for this<\/a> issue resulted in no success. Even rebooting the server the primary search service content crawl states were “paused by system. Regardless of:<\/p>\n
    \n
  1. \n
      \n
    1. Pausing and Resuming the Search Services<\/li>\n
    2. Restarting the Search Services<\/li>\n
    3. Rebooting the server<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
      I was only able to resolve this issue the same way I fixed the initial issue with the crawl, rebuild the search service application.<\/p>\n
      I hope this blogs helps anyone experiencing issues with SharePoint Search functionality. Cheers!<\/p>\n","protected":false},"excerpt":{"rendered":"
      Broken SharePoint Crawl Issue: SharePoint Search First Issue: Crawl ends in 1 min 20 seconds. Solution: Check to see if the Page Loads when queried from the front end server. If you get a credential prompt 3 times.\u00a0 Then you have to disable loop back checking. How to: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa Add a new DWORD value named … <\/p>\n
      Continue reading “Fixing SharePoint Search”<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","footnotes":""},"categories":[8,9],"tags":[360,361,140],"class_list":["post-1190","post","type-post","status-publish","format-standard","hentry","category-server-administration","category-sharepoint","tag-crawl","tag-search","tag-sharepoint"],"_links":{"self":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1190","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/comments?post=1190"}],"version-history":[{"count":6,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1190\/revisions"}],"predecessor-version":[{"id":1197,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1190\/revisions\/1197"}],"wp:attachment":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/media?parent=1190"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/categories?post=1190"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/tags?post=1190"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}