11

As far as I know in the Office 365 / SharePoint Online, you don't have any control over the schedule for the crawl. This is managed by Microsoft. SharePoint Online targets between 15 minutes and an hour for the time between upload and availability in search results (also known as index freshness). In cases of heavy environment use, this time can ...


6

This will be exactly because there is no file extension. The search crawler (or gatherer) relies on the file extension to know which piece of software (IFilter) to load to open the file and index it. No way around it, this is just how Search in SharePoint works.


5

You also need to install the iFilter from Adobe in order to allow SharePoint to index the PDFs. The configuration changes you made simply tells SharePoint to index PDF, but the iFilter is actually what does the work. Start here: http://support.microsoft.com/kb/2293357


5

A crawl is never started by anything changing in SharePoint, neither content nor security changes. A crawl is either started manually or according to the specified schedule. If you're using search, then you probably have a crawl schedule set up which does incremental (and sometimes full) crawls. The full crawls with crawl everything and the incremental ...


5

If it's a multi value property then the max limit is 1000 instances. As per http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#Search a managed property can only store 1000 unique values per item. Your message says over 3000. If it's a single value you can increase the MaxCharactersInPropertyStoreIndex property using the following ...


5

I am surprised that an incremental crawl is not updating the permissions, I definitely believe that it should, but I haven't had a similar scenario to yours in some time, so can't be sure. The only similar scenario I've seen recently was unfortunately with SharePoint Online, so it may not be exactly the same for on-prem, but my experiences of that were ...


5

I think, you should run the full crawl to remove the deleted site from index.Crawler try 30 times before make a decison that this file/url no more with sharepoint. When the crawler encounters an access denied or a file not found error, the item is deleted from the index if the error was encountered in more than ErrorDeleteCountAllowed consecutive ...


4

Here's a couple of options for you: In Central Admin, go to your Search Service Application (Content SSA if you use FAST Search for SharePoint) then navigate to Server Name Mappings and create one. Set the "Address in index" field value to your Extended zone url (the one configured to be crawled in the content source) and set the "Address in search results" ...


4

Add class="noindex" to your footer <div> See Control Search Indexing (Crawling) Within a Page with Noindex


3

It seems that you have to add LastModifiedTimeStampField property to your Finder method. Take a look at this blog posts series from Todd Baginski, especially at this one - The LastModifiedTimeStampField property on the finder method instance is set for two reasons. So search results will display the last time the data was updated So the ...


3

The search crawler does not access Content Databases at all. The search crawler uses the SharePoint Object Model to crawl SharePoint content in a similar fashion to how a user would view the content.


3

Some things to try first: Running an incremental crawl again Running a full crawl Adding a crawl rule specifically for that site, then running an incremental crawl In our case, we did not want to do full crawl in production because we didn't want to lose any more of the index (we have problems with the full crawl.. but that is another story). For most ...


3

Have you considered splitting the content Databases into smaller chunks? I see a few benefits for doing this : Crawler performance Page Response Times Reduce App Pool Recycle Times Since you are talking about Mirroring DB's I am going to take the liberty of thinking that you may have the capability of having multiple SQL Servers. Consider moving content ...


3

you should set the NoCrawl Property to true of the column. SPField.NoCrawl


3

Yes, automaticly. (Not "service", but "content source") It will prevent you from creating two content source with intersections. Up2u. Choice the most comfortable way for you. To disable crawl choice "No" in the schedule drop down. Continuous crawl work every 15 minutes by default. If you have just one crawl server it will not have any difference from ...


3

Just went through this issue with Microsoft last week. You'll need to go into Central Admin > Manage Service Applications Then you'll have to delete and re-provision your Search Service Application. More info on reprovisioning using PowerShell can be found here.


3

So while writing the question i answered my own question. "Draft Item Security" setting says "Only Users who can EDIT". So we must change to the permission-level from Full Read to Full Control, not the cleanest way to solve this, but it works. Have any input please let me know :)


3

You cannot index a list that exceeds the threshold. This is explained in this Microsoft article: Manage lists and libraries with many items Because creating an index requires accessing all items in the list, it's possible you may be blocked from creating an index for a column if the entire list exceeds the List View Threshold. If this occurs, do the ...


3

'Multiple Lines of Text' field cannot be indexed as it's an Unsupported Column Type. See here - Enforcing Uniqueness in Column Values. Indexing the field is separate from search 'crawling' which is needed for Searches (& its results). Make sure the column has a managed property - see : Automatically created managed properties in SharePoint Server 2013. ...


3

Your understanding is not correct. So rule, if a crawl is running and schedule for another crawl schedule (Lets say full) on the same content source is approached then running crawl always took the priority & continue. Now Full crawl will be skipped and wait for the next schedule which is next week in your case. If you don't want to overlap them then i ...


3

If deleted site collections still showed in the search result,then make sure below things A full Crawl against the content source(which belongs to deleted site collections) If after couple of crawls items still Showed in the result then reset the search index. Another thought, please make sure the deleted sites also removed from Central admin Run the get-...


3

Does the file need an "Approval Status". If so, I have seen Search skip content that was pending approval if the library was setup that way.


3

Search aggregates all the data across the farm into it's own database. When using the everything vertical from a search page, it is returning the user everything they have access to that matches that term. Search is global. If your site collection is limited in access to a few people, then rest assured that only those people can access the content contained ...


3

You need to know the default content Access account. Login to SharePoint Central admin with farm admin account goto Application management > Manage Service Application...On this click on the Search Service Application. On this page, Under the System Status look for "Default content Access Account", the value infront of this is the account.


3

Go to your content source and click on edit. Scroll below and you will find Schedule for Full Crawl. Below you will have a "Edit Schedule" link. A pop up opens as below Do the same for both the content sources by changing the weeks schedule. I hope this helps.


3

No, there will be no loss of Index, since the Index component is another component and in your case on another server. When the Crawl component fails, no new content can be crawled which leads to that no new content will be processed by the Content Processing Component. Thus no new indexed content will be added to the Index component. The process of ...


3

Crawl Target does not support an https:// scheme. Only http://. In this case, use host file entries instead.


2

I ran into the same problem and solved it by replacing the String[] by a IEnumerable<StringWrapper>, or in your case IEnumerable<Personal_nameElement>. This could look like: public class Personal_nameElement { public String Value { get; set; } } And in the BDC: <TypeDescriptor Name="Personal_name" TypeName="System.Collections.Generic....


2

Turns out the problem here was completely unrelated to the Filter Daemon, we ended up having many User Accounts created under the HOME group. This pushed the limits of the ACL beyond its 64k limit, and since we have trimming going on each time a page was being crawled it was checked against EVERY user in the list. Due to the large number, we have 65,000+ ...


2

As you have mentioned Task #1 is pretty straight forward and you need to just add a new index server to the farm with the indexing service enabled. Task #2 - SharePoint contents - The primary search content source for searching all the site contents in Central admin should remain. This 'X' department which has growing contents can also use the same crawled ...


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