Tag Info

Hot answers tagged

6

After installing the system you need to configure your indexing job. Navigate to Central Admin -> Manage Service Applications -> Search. You will see a link to your Content Sources. If you edit that it will give you the opportunity to setup a schedule for both Full and Incremental indexing. You can kick off a full crawl, once completed you will have ...


5

Yes, you can. Crawling file shares is very easy to set up, and permissions are accounted for - so there is no risk that users find information they don't have access to. In Central Admin Search Service Application, add a new Content Source. Specify your file server and set up a schedule. Do a full crawl and you're up and running in no time.


4

You can add "Path:http://urlofyourlist" to you KQL query.


3

The Search account will only index published content, so that might be your issue. Try logging in as your default content account (the one that indexes the pages) to see what it looks like from that users perspective. The best way to add reader rights for the default content access account is from inside Central Administration under web applications. ...


3

You can solve your problem in various ways: Change per sitecollection the order of the scopes in the displaygroup that you are using Add 2 site collection type displaygroups, either one with the correct order. Create the displaygroups in a feature, with the correct order of scopes in that group, and use the correct displaygroup for your searchbox. the ...


3

I think you'll need: (ColName:Val1) AND (ColName:Val2) Without the AND, yes, they are implicitly OR'd, as they're the same column. This is mentioned in the documentation, but it doesn't make it clear that you can explicitly AND them. If the column names were different, they would be explicitly AND'd - but in exactly the same way you could explicitly OR ...


3

You need to setup the site collection's search settings (Site Actions -> Site Settings -> Search Settings). Enable custom scopes by pointing the site to your search center, and set the dropdown mode to enable those scopes to be used. Additionally, you should also point it to the applicable search results for your search center, so that when users perform a ...


2

Searching a specific list can be implemented in several ways depending on the type of list you can use CAML to search for specific field info, you can create a search scope just searching the specific list or you can use a custom query that only retrieves info from that list SharePoint Server 2010 Standard allows you to search external content types and ...


2

I know this post is rather old, but I wanted to provide some insite to this as well. If your Web Applications that you created in SP 2010 are "Claims Based" Web Apps, you will see this behavior. Central Admin is not a CLAIMS Based Web App and cannot properly access the Items in the Scope for a CLaims Based Web App. If you browse into the "Search Scopes" ...


2

This blog post provides an answer: http://www.moss2007.be/blogs/vandest/archive/2010/03/18/sharepoint-search-scopes-approximate-item-count-is-incorrect.aspx Apparently the behaviour is that it gets the number of items in a scope via a search query. If for any reason that query fails (permissions, probably) you'll get a result of 0. I had this problem but ...


2

Are you using FAST Search? The UI only really works for the standard SharePoint search. If you're looking at scopes on a FAST Search index they'll always be empty, and the scope rules won't be used (you've got to configure FAST scopes via Powershell, or code).


2

The figure I have seen for SharePoint 2010 is 200 site scopes and 200 shared scopes per search service application. As far as I know the recommended limit on the number of scopes was unchanged from SharePoint 2007 (i.e. 200 scopes for MOSS). These are recommendations - if you exceed them you will probably get poor performance. The best way to find if there ...


2

In Search Administration, within System Status, you can specify that the Scopes Update Schedule be set to "On Demand" rather than the default setting of "Automatically Scheduled Update". Once a scope change is made, you can then kick off the update by selecting "Update Now" next to "Scopes Needing Update". Alternatively, on an ad hoc basis, you could ...


2

Go to "Site Settings" In Site Collection Administration section Click on "Search Settings" Click on "Display Groups" Click on "Search Drop Down" Configure as Required and save settings.


2

Assuming the list stores same type of content, you can create a Search Scope based on Content Type instead of URL


2

If you have search configured, it is possible to search across sites. The All Sites search scope will search against all sites indexed. You can also identify other search scopes as needed that can filter down the index the query searches against. This can be set based on the specific sites, or content properties. If search is configured, you can go to ...


2

You'll need to use and IFilter to crawl the content of PDF-documents. It should work out of the box for Office-documents. Here's a detailed tutorial (I haven't tried it)


2

You can configure every web to avoid that appears in search results. This option is "Site Actions > Site Configuration > Site Administration > Search Availability and offline". Check to not "Index site content" and do an incremental crawl. Sorry if the path has not the exactly options but my SharePoint is in Spanish and I've done a quick translation.


2

Is the search crawler service running as an account that should have access to the sub-site? To rule out permission issues, you could try running the service as one of the admin accounts to see if it crawls the site as expected.


2

Ok, I found the solution: This line from xml should have been deleted: <Property Name="ScopeDisplayGroupName"></Property> When i delete that line and redeploy, I receive the expected results. Hope this will help other people.


2

I found the solution instead of using the SearchServiceApplication which causes the issues with permissions, I use this piece of code: RemoteScopes remoteScopes = new RemoteScopes(SPServiceContext.GetContext(site)); And it works like a charm.


2

You need to include all content as a rule by default, your exclusion then works with this to make the list.


2

This is how we did something similar for our environment. On the master page or page layout you would create a declaration for this code and use a control to wrap anything you want to hide from the crawler. Implementation and explanation from here: http://www.sharepointdesigners.net/profiles/blogs/sharepoint-search-partial-page-exclusion was then ...


2

I have come across this too, and yes, viewscopes.aspx causes the standard display groups to be created. I have written a post about my findings, and the work around I used: http://danielflint.im/2014/01/working-around-getdisplaygroup-throwing-invalid-cast-via-powershell/ Here's the work around: Add-PSSnapIn Microsoft.SharePoint.Powershell ...


2

Just deactivate Document ID Service and reactivate it. Source: Click Here Or try this Open central admin Go to Operations Go to Services on server and located your index server On “Office SharePoint Server Search” click “Stop”. This deconfigures it. Now click “start” Then click “Shared Services Administration”, hover over the failing SSP and select ...


2

To achieve the goal, you can go to configure search navigation. Here are the steps for your reference: Go to the Site settings page, click Search Settings under Search. In the section of Configure Search Navigation, click Add Link to add the the following links: 1). Title = Everything; URL = /search/pages/results.aspx 2). Title = People; URL = ...


1

UserProfiles properties in sharepoint are restricted to a number of data types (and accompanying control: http://stackoverflow.com/questions/1260784/is-it-possible-to-use-custom-data-types-for-moss-user-profile-properties), To get your field to render as a dopdown would probably involve either jquery, a control redirection using the compat.browser file ...


1

I have been encountering the same issue intermittently myself using code like this: $SPWebApp = Get-SPWebApplication $spSiteUrl $displayGroupName = "Search Dropdown" $ssa = Get-SPEnterpriseSearchServiceApplication "Search Service Application" $scopes=New-Object Microsoft.Office.Server.Search.Administration.Scopes($ssa) foreach ($SPSite in $SPWebApp.Sites) ...


1

I had the same problem. We need to use a RemoteScopes object, as in Manesh's example. $serviceContext = Get-SPServiceContext -Site $site $scopes = New-Object Microsoft.Office.Server.Search.Administration.RemoteScopes($serviceContext)


1

I have the same problem, same code, and if I look at the properties of the Scopes object after getting it I can see that there are no DisplayGroups in AllDisplayGroups. For me, I'm sure this is why the script is failing there, but I can't figure out WHY the displayGroup does not show up in the Scopes object. I'm trying to use the default "Search Dropdown". ...



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