Hot answers tagged

6

Have you tried the following? $ssa = Get-SPEnterpriseSearchServiceApplication $ssa.SetProperty("ContinuousCrawlInterval", 1)


4

You can do it using Search Results Removal (under Queries and Results section) from the Search Administration page. Enter the old url here and it will be removed immediately.


4

Not possible as there are no push api's in 2013.


4

As far as I'm aware, the crawler won't 'run' the javascript on the generated page, therefore this technique probably won't actually work. Can't you add a noindex class to the container div of the nav control on the masterpage?


4

Well... The list is quite extensive when you look at it flat foundation vs enterprise. And not knowing what your customers needs are I would, personally, tell these things to my customer; Custom site definitions and site provisioning are not available. InfoPath forms service Access Services Workflows Documents Sets Managed Metadata Document IDs And ALL ...


4

I think it should be: http://localhost/_api/search/query?querytext='test+path:"http://localhost/subsite/"' I have tested it at my end and it only shows the data from the subsite. If you need more help on search using REST, I found the link below to be useful http://www.tikalk.com/net/sharepoint-2013-rest-api-%E2%80%93-search-service


4

Nothing is stupid here. When you create a custom column in a list do a full crawl and you will see a crawled property available with the name ows_ColumnName. You can't map a column to a Managed Property. You always map Crawled Properties to Managed Properties. So you will have crawled properties from site columns and the YES you can map as many crawled ...


4

This is a well identified issue which was fixed with the Oct 2013 CU update to SP 2013. This happens because the managed property ‘Title’ is mapped to crawled property ‘MetadataExtractorTitle’ by default as first priority and there was no way to change the order of this crawled property unless October 2013 Cumulative Update was applied. However, this issue ...


4

that is expected behavior, but it does not mean that incremental crawl runs every 4 hours. you have to select between continuous vs incremental. When you click on Continuous Crawl it disable the Incremental crawl. Continuous crawl automatically run every 15 min( by default). Continuous crawls crawl SharePoint sites frequently to help keep search ...


4

Yes it is. Please see this TechNet documentation for when a full crawl is needed. A Search service application administrator or site collection administrator added or changed a managed property. A full crawl of all affected content sources is required for the new or changed managed property to take effect.


3

Stemming is available in SharePoint 2013 and enabled by default. Stemming is only available on nouns and adjectives in 2013, you can't search on verbs. I.e if you search car search will return the results for Cars But if you search for Run it will only return the Run results not for Ran. Read More over here. ...


3

Looks like, Site is still in SharePoint Admin Bin.You should this. Use powershell to create site collection Or Run this command Get-SPDeletedSiteenter link description here and if you get all the sites you are having issue then Run Remove-SPDeletedSite -Identity Manually run the Gradual Site Delete timer job from central admin. after this try to ...


3

You can specify a search center for all My Sites in the User Profiles Service Application > Setup My Sites > Preferred Search Center. Are the OOTB search box not working out? Be sure to add "/pages/" after the URL to your search-center. As the example under the text box states. There is currently a bug in SP2013, that by my understandings won't let you ...


3

There are a couple things you could try. Nothing in SharePoint will let you do this. The only mailbox search that is possible from SharePoint is through eDiscovery and that requires too much overhead. I would start by trying to do a federated search to Exchange 2013 Search as if the user were performing the same search from Outlook Web Apps. I would ...


3

Stop-SPServiceInstance This cmdlet will Stops the service instance for a service on the specified server or for the farm. Use the Start-SPServiceInstance cmdlet to start the service instance for a service on a specific server or on the farm. This will not wipe index


3

You cannot set the crawl in O365. It is set to do a continuous crawl, and should take ~15 minutes for results to show in search results. However, in times of heavy use, that can increase to hours. This link provides more information: http://www.sharepointnutsandbolts.com/2013/10/waiting-for-search-crawl-in-office-365.html


3

Two things, the start address for Profiles should be sps3://mysitehost. The permissions on the User Profile Service for the default crawl account has to be allowed to "Retrieve People Data for Search Crawlers". Go to Central Administration | Application Management | Manage Service Applications. Select the User Profile Service Application (don't click the ...


3

You need to setup the site collection's search settings (Site Actions -> Site Settings -> Search Settings). Enable custom scopes by pointing the site to your search center, and set the dropdown mode to enable those scopes to be used. Additionally, you should also point it to the applicable search results for your search center, so that when users perform a ...


3

We finally figured out the problem with this one. We had given Full Read permissions to NT AUTHORITY\Authenticated Users for All zones in User Policy of the web applications in question. I am not sure of the reason for giving this. We removed it. Then, a full crawl fixed the issue. Thanks!


3

Without development you can try add a static query to the content search result webpart: tags:"Keyword X" or tags:"Keyword Y" or tags:"Keyword Z" - tags should be the managed property for the Enterprise Keyword column. With development you have to use the KeywordQueryClass, see: http://msdn.microsoft.com/en-us/library/ms544561%28office.12%29.aspx ...


3

Here is what you are looking for. I have used this when I had to recreate my search center and it worked like a charm: http://sharepoint.jsturges.com/2012/02/update-search-center-for-all-sites-in-a-web-application/ All you basically do is save your new search center url in a variable and use that variable to set the url to all sites within a web app by ...


2

You need have at least one list item with valid value in this column. Then you need to run full crawl. After the crawl is complete you will be able to see it as *ows_yourcolumnname*


2

Yes, you have two options: Use the already configured search index of Farm A (search federation) Crawl Farm A from farm B You can get more information about configuration here: http://technet.microsoft.com/en-us/library/jj219577.aspx#Section12


2

The scope of the rule: If you define them in the search service, its valid for all webapplications associated with that search service. If you define it on subsite/web level, its valid for the contextual search made on that site. If you define it on site collection its valid for the site and all subsites.


2

This is NOT possible with Managed Property keyword queries. The only wildcard capability that Sharepoint Search Server 2010 supports is "Stemming". Stemming expects the characters to be matched by the characters at the start of a string in the index. e.g. Item contains Title string "TestMe" You're query can be : Title:"Tes" and that would pick up the ...


2

The issue seemed to be down to the size of the Index Partition. We reduced the number of items in the index using crawl rules and were able to get it down to about 8 million items from 12 million. We were able to then make changes to the search topology. What was interesting was the SharePoint Search Service on the rogue Crawl server would take about 90 ...


2

When was the last time you ran a full crawl since this issue? I'll be clear, I don't think that's the issue but managed properties (the refiners) are very unique and a full crawl is needed before you can even search against them. I wouldn't be half-surprised, as unbelievable as it sounds, that you would need to do a full crawl for the refiners to show the ...


2

This is not possible - the searchbox overrides the refinement. The idea behind it is: The end-user starts searching by using a phrase/keyword in the textbox - then he refines the result set with the refiners.


2

Ensure that the users have permission to view the search center site collection


2

With regards to that particular error code it is linked to Performance Monitor. You could try Make sure the Search Service account is added in the Performance Log Users and afterwards check that you find a search related trace with status Running in "Event Trace Sessions" of the Performance Monitor.



Only top voted, non community-wiki answers of a minimum length are eligible