Posts

Showing posts with the label sharepoint search error

Sharepoint Online SPFx Search Rest Api 403

Image
In case you develop an SPFx and you try to use RestApi for Search (or maybe also with the SP Rest) and you get 403, this in because your Webpart is running in his own scope, under an IFRAME. The solution is to dynamically take your Absolute Url      let   filesQuery  =  this . context . pageContext . web . absoluteUrl ; Every SPFx Webpart has his own SPPageContextInfo. P.S. In case you choose to user SPHttpClient, you need 2 things to get over your 500 error: 1. use Default configuration (that should be v3 or v4) 2. change Accept header odata part to verbose      this . context . spHttpClient . get ( filesQuery ,  new   SPHttpClientConfiguration ({}),       {  headers :  {  Accept :   "application/json;odata=verbose;charset=utf-8"  } })         . then (( response :  SPHttpClientResponse )...
1 comment
Read more

Sharepoint Search Crawl error with BotDetect

this is what you may see The SharePoint server was moved to a different location. ( Error from SharePoint site: HttpStatusCode Redirect The request failed with the error message: --< html><head><title>Object moved</title></head><body>< h2>Object moved to <a href="/_vti_bin/sitedata.asmx?AspxAutoDetectCookieSupport=1">here</a>.</h2>< /body></html> --., CorrelationID: 6f92129d-4742-20cf-86da-6e46bae7318e; SearchID = B83C0CF2-2B3E-4047-AC33-ADD06488B452 ) we dont understand why but it only happens when the BotDetect is configured as AJAX. the available solutions, Note that for search we usually want only to adapt the admin site: 1. do not activate the capthca on the admin. 2. change the cookieless attribute in the sessionState for the BotDetect to false, like explained here: http://captcha.com/doc/aspnet/known-issues.html#cookielesscrawlers more on cookieless: https://msdn.microsoft.com/en-us/li...
Post a Comment
Read more

Sharepoint 2013 search error: The crawler could not communicate with the server

wherever you get this error message in sharepoint 2013 search: The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. the 1st thing that means is that the crawler just failed to get the page. but before you're running to the IIS and FW, you should just think about Permission. and that 1st of all means that everything is Published! Steps: 1. publish everything, incuding Master pages, Page Layouts, ect. 2. make sure the user running the search crawler has Read Permissions to that web. 3. if not the above, do check the IT stuff like communications and FW.
Post a Comment
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX ...
3 comments
Read more