Hot answers tagged

8

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 ...


6

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


6

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 ...


4

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 ...


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

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.


4

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 ...


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.


4

Crawled properties are generated automatically by SharePoint when crawling published content that has the correspondent fields filled up. For example, in order to get a CrawledProperty for "MyColumn" you need to have at least one item that has a value in that column. After the next "Full Crawl" a Crawled Property for it will be created with a kind of ...


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

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

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

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

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

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

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: ...


2

The solution was to change sps3 to sps3s such that the url was sps3s://mysites. I thought I recalled another protocol but I couldn't find any hint of anything other than STS from the SharePoint 2007 days. I eventually stumbled upon this article which provided the answer as well as many other search crawl related issues and their solutions. After I found ...


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

You dont to reset the index if you just want new content coming to this component. But if you want to divide the content equally then Reset the Index and perform a Full Crawl. Or if you see any issue after adding new crawl DB i.e crawling on content source not completed etc.then you need a index reset followed by full crawl.


1

SharePoint search architecture unable to crawl email attachments. Either you have to store attachment in different item or different library to available attachments in the search result. Regards, Jay


1

You can set vti_searchversion on a web, library or folder, not per item. Not ideal, but not too bad. There's some code over at https://sebastian.expert/force-web-whole-list-library-re-crawled-search-sharepoint-2013-using-api/ you can use. Or my re-crawl scripts at https://github.com/wobba/SPO-Trigger-Reindex.


1

Answered my own question by reading this a little closer: A continuous crawl does not process or retry items that return errors more than three times. A "clean-up" incremental crawl automatically runs every four hours for content sources that have continuous crawl enabled to re-crawl any items that repeatedly return errors. This incremental crawl will try to ...


1

I would get rid of all the Adobe products and change the UseIFilter property back to false. Then run a full crawl to determine if the native PDF file handler is working correctly.


1

I am sure you index will be fine after installing or uninstalling but you have to have run the full crawl after this activity. I think you should remove the custom ifilter as it is trial version and expired. We had metalogix trail product in our farm which give us tough time after expired trial. I would uninstall the 3rd party ifilter and then configure ...


1

We have found the solution. After a lot of scoping, we narrowed it down to a web application. I then went on, finding out which site within that web application was the culprit. It turned out to be a single site collection in which over 500k MSG items were stored. These folks (one specific department) are using SharePoint as a mail storage system, because ...


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 would create a Scope that has these site collections listed as include rules. Then there is no need to remove the existing content source, the scope is just a subset of that index.


1

A root site collection is a requirement for any Web application and furthermore it is also necessary for crawling content. This root site collection must have the same URL as the Web application. Only the root site collection of the web application appears in the content source. All the other host-named site collections in the web application do not appear ...


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

The first thing to do is click on the link to the document and see if it can be loaded. If the document is not corrupt, start up Excel (or whatever client app is involved) as your search account i.e. runas...sp-crawling-account-whateverthatmaybe and see if that account can still open the file and read it. If these two things are OK then I would expect that ...



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