I am doing an in place search in a document library and results are being returned just fine. However, some users are reporting seeing the following message:
Some files might be hidden. Include these in your search
I also receive this message at random times for different searches. There seems to be reports of this on various boards with no real answer. Anyone know why this message would occur?
This may relate to the Search Service Settings > Content Source in Central Admin. Ensure that the addressers are correct and that the crawl have the same entry as you do. Normally you want to point the url to the default zone.
When done, reset the index and start a new full crawl.
Related
We run a classic JavaScript app on multiple tenants on SharePoint online. The app uses the Microsoft.SharePoint.Client.Search.Query.KeywordQuery to search for documents within the site collection where the app is installed. On one of the systems we get the error:
Microsoft.Office.Server.Search.SubstrateSearch.SubstrateSearchException:
Remote executors failed, local failback not allowed.
Despite the specific words in the error message, I was not able to find any documentation about its meaning. When I copy the search string used in the SP search field the search works. Any clues what could be the cause?
Any developments on this? We just started seeing this same error in one dev environment but not another, despite running the same code.
I have the exact same problem, but if I include "-contentclass:STS_ListItem_DocumentLibrary" in the keyword query it works, but since i need items from document libraries this wont help me.
We have only seen this issue one one environment, I am not sure how to fix it. It looks like it is having issues with document libraries specifically, unless i include a some text it also should search for (besides the keywords). If i didn't know any better i would almost say it was some kind of overflow, but that just seems far fetched, and we do have limits on the query anyway.
Update:
Subsequently if I wrote a keyword for a specific library like ListId:73C91192-89CD-4C06-A322-388CEAE456ED instead, it also works
we just recently started to see this same issue.
In our case we were using a Classic SharePoint Online site, with the search web parts on it. The search results web part had a number of different Hit-highlighted managed properties that it was trying to bring back. One of these properties was "Topic". I checked the search schema and for some reason, this managed property had disappeared. Removing this property from the search results web part fixed the page and search results web part.
No one had touched our search schema in a long time so this property had simply disappeared. Definitely seems like search schema updates are causing issues.
Hit-highlighted properties
Does anybody have some usefull information or pointers on this issue? We just came across this issue on one tenant for one specific user. We have a multi-tenant app that executes a search query looking for document libraries with 3 conditions:
We do use the ContentClass:STS_List_DocumentLibrary condition as we are looking for document libraries
External content specifier: "-isexternalcontent:1"
Generic search term: just a single word
As mentioned we get this error on one tenant when one specific user executes it. I can't reproduce it with other user accounts. Since we are providing a multi-tenant SaaS we are afraid this will start popping up for our customers..
I have searched unsuccessfully for a number of days to try and resolve an issue with the search not returning results in Sharepoint 2010. Basically the search has successfully crawled the content and indexed the results but the search is returning no results on our site.
The codebase is the same as other servers that does return results so we are confident it's not a coding issue, but is a sharepoint issue. We can reach the search queryex webservice also
I was wondering if anyone had any suggestions on possible settings / things to check to try and kickstart this search!
This is my first question on stackoverflow, so please advise if I haven't added enough detail.
I'm fairly new to SO myself, but I'll help if I can! Quick couple of questions:
Is the search returning no results for all user types, including admin?
Is there an error returned when you submit a search or does it just say "no results"?
Are you using any custom web parts for displaying the search results, or is it OOB?
Do you have access to the ULS logs perchance? There may be further information there.
Are you using search scopes at all?
What domain account are you using for the search app pool? There's some info here about making sure you have the right type of identity - SharePoint 2010 search crawling but not displaying results
(Apologies for posting a comment-as-an-answer, but since my rep is below 50 I can't yet post comments on your question - still wanted to help though.)
As part of a SharePoint solution, the functionality for users to create new web sites and publishing pages (programmatically) via a button click has been added. I need to ensure that the Description field for the newly created sites and pages is indexed by SharePoint Search. What is the best way to do this?
Please note, I am NOT interested in starting a new crawl. I just want to ensure that whenever the next scheduled crawl occurs, the contents of these fields will be searchable.
Thanks, MagicAndi
I'm guessing you mean how can you ensure the site is indexed immediately?
Generally, crawls are scheduled which means your new site will only be added to the search index after the next crawl is done. So if your incremental crawl happens every hour you may have to wait up to an hour for it to appear in the search index.
However, given that your new sites are being added programatically you could also programatically start an incremental crawl if it is vital for it to start appearing in search results immediately. There are details how to do this in this article.
Update:
The site title and description should be indexed automatically by the next crawl. If this isn't happening, then you don't have a Content Source that covers that site so you need to create/update one to cover the new sites and make sure it has a crawl schedule. If the new sites are created in separate site collections consider putting them on a Managed Path.
In our SharePoint system we have a terrabyte of data with 100,000 site collections and probably 20 new site collections added every day. We only have one content source that points to the root of the site and everything gets indexed automatically.
It sounds like you're missing a content source or a crawl schedule.
It turns out that the site description is included in the crawl by default. I tested the search default properties by creating a new site and assigning a unique text string to the description. After the next incremental crawl, I was able to search and find the unique string via the default SharePoint search.
I have not yet tested if the page description is included in the search scope by default, but I'm prepared to guess that it is. I will update my answer as soon as I get a chance to test this.
For some reason my search in the sharepoint site does not work.
I have set up the SSP, the scopes, the crawls, everything but it still does not work
Can someone explain to me how to setup the search? Maybe I did something wrong in the process.
It's not the simplest thing in the world to setup, as it's comprised of a number of components.
You need to check each one to determine where your problem is.
Start from the crawl, and work your way forward to the search production on the page.
So check the following:
Check some servers have been setup to index pages. (You can see this under services on servers in the central administration pages.)
Make sure they're all running correctly. (Not in a half started state.)
Check your crawl log in your SSP to see if it is indexing anything.
(Index different types of content, like file shares, web sites, and sharepoint itself. (check each one.)).
(Note you need a special plugin to index PDF's.).
Check your index is copied to the front end server where it is used.
If it's not, it may be because this hasn't been configured, (Check Services running on servers again)
Then check your site collection setup, and ensure you have a search site configured.
Ensure the site collection search details are configured to use the search site.
Finally check the user doing the searching actually has access to the content being indexed.
Doing all of that should give you some idea of where the problem is.
In addition to Bravax's answer its worth checking that you are not getting stung by the local loopback check.
I had similar problem and ended up using search server express which is free (see my answer from this link: sharepoint 2010 foundation search not working)
I have installed search server express 2010 on top of SPF which works great. it has additional features and work well with sharepoint foundation. her is a link for upgrade and configuration: http://www.mssharepointtips.com/tip.asp?id=1086
You need to crawl the the contents source and add the website to it, then run full crawl to index data.
Platform: MOSS 2007 on server 2008
Sharepoint is working etc...
Problem: When you search for something, it doesn't find anything, no errors.
Authentication and permissions look fine. Search service is up and running.
What could be the problem? Any checkpoints I might have missed, any bad configurations I should check, etc...?
You should start with checking the crawl log files. That will probably give some valuable information.
Also double check that the SSP is set up correctly, with a valid content source setup, valid starting addresses, schedule etc.
Make sure that no crawl rules prohibit any searches.
And lastly, no 3rd party/custom security trimmers installed that prohibit results to be shown.
Doesn't work is not a lot of use is it.
My first guess is: Have you configured the search correctly (crawl schedules, content sources etc.)
To setup search (crawl etc.) go to the Central Admin site and then to your Shared Service Provider. in the SSP Select Seearch Adminstration. in the menu on the left you can find the link "Content sources". In the following page you can select the Content Source (something like "SharePoint sites" (out of the box). selct edit in the context menu and define your crawl schedule. Then select the "start a full crawl" checkbox.
You should make sure that you've indexed your site.