Hot answers tagged crawling
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
2
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 ...
2
The 'Contribute' level of permission still does not have permission to see minor versions. You would have to grant the crawl account at least 'Approve' permissions for this.
However, if a document has not been given any version yet then only the document creator can see it. If you want those documents to appear in search then the crawl account will need ...
2
Don't use SSL (https) whenever specifying your content sources in SharePoint search.
Also, the second error just means that users and services are using the http://servername url to access to the site. It's more of a warning than an error. I constantly see that on my farm, but I ignore it.
1
Method 1 from this link did the trick for me.
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
Right-click MSV1_0, point to New, and then click Multi-String Value.
Type BackConnectionHostNames, and ...
1
With the various changes going on, it may be a good idea to just reset the index and run a full crawl. There are a lot of things, including the managed properties that get defined during that first full crawl so it is possible that it just isn't getting everything.
Also, make sure that the system is setup for full support for anonymous access. Search ...
1
Crawler's have schedule to crawl, they don't just randomly start crawling, and it time depends on how you configured crawler's Schedule. You can check when your crawler crawled last time through Central Admin.
In the Search service application, you can schedule a full or
incremental crawl of a content source. There are four types of
Schedules:
...
1
Does this workflow result in an approved document being "published"? If so, you could set the crawl account to only have permissions to view published items instead of all items.
Here is some related information: How does SharePoint Search handle pending (unapproved) items?
1
To answer your specific question, yes, there is. Go into Central Administration - Shared Services - Search Administration (or if you are on 2010, Manage the Search Service Application) and there is a link on the left called "Crawler Impact Rules". You can use those to control how hard the crawler hits the site. Bear in mind that reducing the impact will ...
1
Unless you build a Macro (which by the way are not recomanded particularly for spreadsheets hosted in SharePoint) the Track Changes should allow you access to all data.
Q: Why not considering importing the Excel into a custom list, which would give you more possibilities, such as:
No-code (via SPD Workflow) to use "Wait for a change" in target
fields and ...
1
A few reasons that I'm thinking of
the targeted site is not part of any content source
the crawler account that is used has no access to the target site
A specific robots.txt is available at the root of the web application preventing a proper crawl / indexing
A too generic crawl rule is defined or wrongly positioned (cascading effect)
an unconfigured ...
1
If you have a lot of users in the site (usually over ~1800), your site will no longer be crawled. This count includes unique users in sharepoint groups or site permissions. Users in active directory security groups don't count towards the limit (the security group counts as 1).
If this were the case, you would likely be receiving a message like The ...
1
Since SP1 our current site was no longer alloweding the People Crawl access through the sps3 protocol, for some reason this only works on the extended site. Our extended site is set up with anonymous access, more for the Search Content Crawl to work, this is on port 81 so placing the port number on the content source as sps3://hostname:81 allows the People ...
Only top voted, non community-wiki answers of a minimum length are eligible
