Tag Info

Hot answers tagged

4

You have several options of excluding content in SharePoint: Crawl Rules tag Search Scopes robots.txt custom code to exclude content "noindex" tag (--> warning will still make SSRS requests, only not index the content) 1. Crawl Rules You say you don't want to use crawl rules as you have many pages you would have to exclude. Fine. 2. tag With the ...


4

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


4

Does your crawl account have access to the 2007 site? If you are still struggling you can watch the requests by using Fiddler as a proxy for the crawl process. Then you can kick off the crawl and watch the requests and the response from the 2007 server.


3

SharePoint internal errors may not always say exactly what is wrong. Instead, they throw a general error at you and you’re on your own with your favorite search engine. This could very well be the cause in your case, which may be difficult to find. There are however, cases where your error is caused by the use of multiple values flag on a site column ...


3

To second Matt's answer, what you're asking to do is simply not possible. The reason why you can't index external content is because Microsoft doesn't provide access to the Crawl configuration. This area of the SharePoint Online implementation is a black box managed by Microsoft and Microsoft alone. It's not hidden, obfuscated or disabled "by default" - it ...


3

You could consider using dedicated servers for search. There are guidance on Technet regarding the relatively new "best practice" physical topology called Streamlined Topologies, where one setup is using a dedicated server for search. Streamlined topologies is an attempt to make the server topology more simple, and configure it based on latency/cpu/ram ...


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

In order to see the crawl log in SharePoint Online, you need to create an eDiscovery Site Collection. When the eDiscovery SC is created, create a case and add a souce. Finally run queries exporting content to your source case. In the eDiscovery Center, open the case that you want to add a source to. Click eDiscovery Sets. Type a name for the ...


3

Continuous crawl is created to try to help keeping your search index more up to date. The problem with incremental crawl is that only one can run at a time (for a content source) and it only updates the index when it's done. Multiple continuous crawls can run at the same time (for the same content source) and they update the index continuously. The main ...


2

As you stated in your last update, checking for useragent is an option.If the user agent contains MS SEARCH, the rendering is stopped. This works (tested) in SharePoint 2007 and 2010. if (!string.IsNullOrEmpty(Request.UserAgent)) { if (Request.UserAgent.ToUpperInvariant().IndexOf("MS SEARCH") > -1) { return; } }


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

Incremental Crawls are search crawlers that gather the changes made since the last crawl. Incremental Crawls and Full Crawls cannot be run in parallel. They take charge and hog the whole crawler resource. This also makes it possible to have very outdated search results. An incremental crawl may not pick up changes that happen while the incremental crawl is ...


2

Solution: You need to disable the LoopBackRequest in registry. To do this, just follow my instructions: Go to command window and type regedit.exe Once opened the registry editor, just navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" Right click on "Lsa" and create a new 32bit DWORD value Rename it as "DisableLoopbackCheck" (Note: you ...


2

You cannot add a content source to SharePoint Online (SPO). There are techniques to "Federate Search" between On Premise and the Cloud, but that configuration is more than I can answer here. If federation is not an option, I would suggest, now that you know this limitation, you readdress the business problem. For example, if you need to search for the ...


1

The reason it fails is due to a code bug in Microsoft.Office.Server.Search.Administration.GetErrorMessages. In the loop it checks if allKnownErrors has the key, and of course it does as it's looping that dictionary. The code should check if dictionary2.ContainsKey instead. public Dictionary<int, string> GetErrorMessages() { ...


1

I had the same problem where small .pdf files (less than 1MB in size) were being truncated. I finally found that it was version 1.3 .pdf files that were generated by SQL Server Reporting Services were the issues. I was able to resolve it by using the Adobe iFilter. Details may be found here: ...


1

Turns out the Page Layout had a reference to 16.0.0.0 that was causing search to blow up. The site started out as an O365 site but was recently migrated to on-prem; this must have slipped through the cracks. Honestly, I'm surprised the page loaded at all.


1

I've finally dived deep enough to solve my problem. This is according to Microsoft by design with the People Result Web Part, you can use the Core Result Web Part instead. "Apparently, the issue is with the People Results web part. If you remove it and add the Core Results web part instead, point it at the People scope and configure it the same way, it ...


1

It consist of the following steps: Add application server to the existing farm. To add application server to the farm follow MSDN Add a Web or application server to the farm Configure Search service application In case of search architecture further options might be considered, like scale out of Search components Configure Search components Search ...


1

Crawling is one of the most resource intense services you can use in SharePoint. That's why we in the first place would like to have an application server in our three tier topology setup. One for Front-End, one for Applications and one for Databases. As content grow over time it will take longer and longer time to crawl with an already resource intense ...


1

I think it should work as you described - the following steps are needed, maybe you can try again: To be picked up, the new items must be crawled. If you’re not using Continuous crawling, this will be limited to when your incremental crawls run. The column must be a site column! To be picked up, crawled properties MUST have a value. To be applied ...


1

Please give your search content account access to the managed metadata service application: http://get-sharepoint.com/2013/04/failed-to-run-flow-microsoft-customdictionarydeployment/ ** EDIT: Above I stated content access account, it should be the service account (windows) that's running search. Apologies for confusion.


1

You would use the Set-SPEnterpriseSearchCrawlContentSource cmdlet. Here is the documentation on how to use it: http://technet.microsoft.com/en-us/library/ff607675.aspx(v=office.15).


1

Tried this one for exclusion? http://site/.*.aspx[?]review=1


1

This issue was fixed in the SharePoint 2010 April 2012 Cumulative Update package: Issues that this hotfix package fixes: Changes on the Home.aspx page are not crawled through an incremental crawl in SharePoint Foundation 2010. Don't get confused by the description only mentioning Home.aspx, which relates to Wiki pages. I have ...


1

It depends on so many factors. Server configuration, amount of data to index specific settings for the content sources/scopes. Be very careful though when setting your content sources. I once had a client set their search to follow links. They had linked to their internet site and then had links from that to other sites. When they finally asked me to take a ...


1

The performance of search will depend on a few things Size of target being crawled, bigger it is the longer it'll take, naturally. Also, the performance of the target, if pages are loading slowly, search will run slower. Your farm infrastructure: services per server and server performance. How is your farm setup? Is search running on its own server or ...


1

Rahul, to answer your question, based on the comments in your question: You should try to crawl and index the items via the JDBC connector instead of the OOTB SharePoint connector. take note that you need to install the java runtime. You will also need a sql database (no express version) when indexing more then 2 million items. see ...



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