Episode #125 of the Stack Overflow podcast is here. We talk Tilde Club and mechanical keyboards. Listen now

Hot answers tagged

15

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


10

Crawled properties are generated automatically by SharePoint while crawling published content that has the corresponding fields populated. 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 "MyColumn" will be created with a kind ...


8

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


7

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


7

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


7

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

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


6

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


6

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


5

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


5

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


5

Yes, it requires performing incremental Crawl. it's enough to reflect your new list search settings. Incremental crawl covers the below scenarios, Adding new document/item. Edit document/item Content, Properties / Delete document/item. Changing List / Library settings. Changing Item permissions.


4

First, in Search Administration (this is the page that shows the status of all of the search components and index), record the Default Content Access Account. Next, go to Central Administration -> Manage Web Applications. Highlight the Web Application you want to have search crawl. Click on User Policy in the ribbon. Add a new user (the Default Content ...


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

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

You cant check that. In office 365 Continuous crawls are enabled , with crawl frequencies managed by Microsoft. Search crawls occur continuously to make sure that content changes are available through search results as soon as possible. Recently uploaded documents may not immediately be displayed in search results because of the time that's required ...


4

Stop the crawl for all content sources Get-SPEnterpriseSearchCrawlContentSource -SearchApplication "Search Service Application" | ForEach-Object { If($_.CrawlStatus -ne "Idle") { Write-Host "Stopping crawl on Content source $($_.Name)..." $_.StopCrawl() While ($_.CrawlStatus -ne "Idle") { Write-Host "Waiting to crawl to be stopped......


4

You need to do a crawl, as the item will need to be deleted from the index if it was there previously, and it's the crawler that does this. An incremental crawl should do the trick; if you want to be super-sure and don't have that much searchable content, you could also do a full Index Reset then a full crawl.


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

Check that your search account has 'Retrieve People Data for Search Crawlers' rights in your User Profile administrators


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

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


3

I have encountered issues with this recently myself on at a Yammer question. You can try to clear the SharePoint Config Cache to resolve it. See http://blogs.technet.com/b/sp/archive/2013/05/29/clear-sharepoint-config-cache-with-powershell.aspx for code on this. Code copied from the above post: Add-PSSnapin -Name Microsoft.SharePoint.PowerShell –...


3

It does not expedite it, it just flags the document library or site to have the crawler perform a full crawl on the next pass. If you've set up Continuous Crawl, this should be fairly quick.


3

No, content sources are defined by start addresses and crawl rules. You could try to define a targeted crawl rule, but that would exclude the other content and you cannot reuse the start address. What I would suggest is that you architect your farm so that your search topology can use Continuous Crawl. This brings your index freshness to near 15 minutes (or ...


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


2

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.


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: http://messor.com/small-pdf-files-reporting-item-truncated-index-...


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


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